ICANN/GNSO GNSO Email List Archives

[ispcp]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [ispcp] RIR meetings for ISPCP Outreach


this is great!  i can help build  the graphics for a presentation, brochure, handout, etc…


On Aug 7, 2012, at 8:25 PM, MAEMURA Akinori <maem@xxxxxxxxx> wrote:

> 
> Thank you very much everyone for your support on this idea.
> 
> I have the reach to the CEO and/or Comms Director of every RIR, then I think can do the "air cover", or even all coordination to have a timeslot in every RIR.
> 
> Let me start with APNIC and then apply it to the other RIRs.
> 
> Then we need to develop a slide.  I have my own idea for the content which the RIR community people should want, but definitely need someone else with a firm ISPCP position to complete it.
> 
> 
> Best,
> Akinori
> 
> 
> 
> 
> 
> 
> 
> 
> In message <AAF87A91-238E-4F74-A25B-0FDD8DC755E7@xxxxxxxxxx>
>   "Re: [ispcp] RIR meetings for ISPCP Outreach"
>   ""Mike O'Connor" <mike@xxxxxxxxxx>" wrote:
> 
> | 
> | i agree.
> | 
> | any ideas on how to get on their agenda?  i know people at ARIN, but it would be helpful to have some official air cover before i approached them. 
> | 
> | mikey
> | 
> | 
> | On Aug 7, 2012, at 10:39 AM, "Anthony Harris" <harris@xxxxxxxxxxxxx> wrote:
> | 
> | > 
> | > This is a truly excellent idea!
> | > 
> | > I can do the LACNIC meeting.
> | > 
> | > We could ask South Africa ISPA to
> | > help with Khartoum, perhaps.
> | > 
> | > Best
> | > 
> | > Tony Harris
> | > 
> | > ----- Original Message ----- From: "MAEMURA Akinori" <maem@xxxxxxxxx>
> | > To: <ispcp@xxxxxxxxx>
> | > Sent: Tuesday, August 07, 2012 1:42 AM
> | > Subject: [ispcp] RIR meetings for ISPCP Outreach
> | > 
> | > 
> | >> 
> | >> Dear Colleagues,
> | >> 
> | >> I will write the idea I mentioned yesterday's call for the clarity.
> | >> 
> | >> I suggested to use RIR meetings for ISPCP Outreach.
> | >> 
> | >> In terms of targeting, they have the perfect match.
> | >> RIRs' members are ISPs or carriers who obtain IP numbers from RIRs.
> | >> 
> | >> In terms of logistics, a timeslot for the presentation is easy to obtain.
> | >> RIR meetings usually have a session containing the reports from other RIRs, NRO and IANA.  I don't find any big difficulty to have a 10 minutes slot for us to introducing ISPCP, while it is subject to the RIR's desicion.
> | >> 
> | >> I had a brief chat with APNIC people and had a positive response.  If we agree, I will try APNIC to let us have it in the forthcoming meeting APNIC34 at Phnom Penh, in the last week of August.
> | >> 
> | >> fyi, the forthcoming RIR meetings are:
> | >> 
> | >> Aug 27-31: APNIC34 @ Phnom Penh
> | >> Sept 24-28: RIPE65 @ Amsterdam
> | >> Oct 24-26: ARIN30 @ Dallas
> | >> Oct 29 - Nov 2: LACNIC18 @ Montevideo
> | >> Nov 26-30: AfriNIC17 @ Khartoum, North Sudan
> | >> 
> | >> 
> | >> I have been long involved in the RIR arena for more than a decade and I suppose there are not many people who will get interested in gTLD policies and will have problems to understand GNSO process and what happens in ICANN arena.
> | >> However RIR community apparently meet the criteria to participate in ISPCP, thus the very place for ISPCP to do some outreach activities.
> | >> 
> | >> If ICANN needs to have more people with the ISPs' stake, it will be good way to go.
> | >> 
> | >> 
> | >> With those said, I might have missed some points which might have already been dicussed here before.  Let me know if you find any.
> | >> 
> | >> 
> | >> Thank you,
> | >> Akinori
> | >> 
> | >> -----
> | >> MAEMURA Akinori   General Manager, Internet Development Dept.
> | >> maem@xxxxxxxxx      JPNIC - Japan Network Information Center 
> | > 
> | 
> | - - - - - - - - -
> | phone 	651-647-6109  
> | fax  		866-280-2356  
> | web 	http://www.haven2.com
> | handle	OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)
> | 
> | 
> | 

- - - - - - - - -
phone 	651-647-6109  
fax  		866-280-2356  
web 	http://www.haven2.com
handle	OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)





<<< Chronological Index >>>    <<< Thread Index >>>