<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [ispcp] RIR meetings for ISPCP Outreach
Hi,
Just to report you:
Today I did the presantation.
The recorded video is already available at the program page
http://conference.apnic.net/34/program/reports
and directly here:
http://conference.apnic.net/34/program/reports/video
My part is starting around 29:00 .
My English is not very good, and I have a couple of thing I missed to mention.
Not very many but I had some responses from my friends.
Especially Paul Wilson likes this approach of ISPCP and thinks positive of further cooperation.
Hope you like it.
Akinori
In message <94A656B58A0446D7AF73F083E3724567@harrys>
"Re: [ispcp] RIR meetings for ISPCP Outreach"
""Anthony Harris" <harris@xxxxxxxxxxxxx>" wrote:
|
| That is a good suggestion. I can help in preparing
| this list.
|
| Tony Harris
|
| ----- Original Message -----
| From: <KnobenW@xxxxxxxxxx>
| To: <maem@xxxxxxxxx>; <ispcp@xxxxxxxxx>
| Sent: Friday, August 10, 2012 3:27 AM
| Subject: AW: [ispcp] RIR meetings for ISPCP Outreach
|
|
| >
| > Akinori,
| >
| > Names of member organisations could be included, too, giving the audience
| > examples of where participants come from.
| >
| > Best regards
| > Wolf-Ulrich
| >
| > -----Ursprüngliche Nachricht-----
| > Von: owner-ispcp@xxxxxxxxxxxxxx [mailto:owner-ispcp@xxxxxxxxxxxxxx] Im
| > Auftrag von MAEMURA Akinori
| > Gesendet: Freitag, 10. August 2012 05:34
| > An: ispcp@xxxxxxxxx
| > Betreff: Re: [ispcp] RIR meetings for ISPCP Outreach
| >
| > Here's the *initial* draft of the slides.
| >
| > Eight minutes is not infinite, but I believe we can still add one or two
| > slides.
| >
| >
| > Akinori
| >
| >
| >
| > In message <201208081717.EDF95882.NBNF@xxxxxxxxx>
| > "Re: [ispcp] RIR meetings for ISPCP Outreach"
| > "MAEMURA Akinori <maem@xxxxxxxxx>" wrote:
| >
| > |
| > | Thank you Alain!
| > |
| > | I will develop slides aligning with my thought and will share with you
| > all for further development.
| > |
| > | Akinori
| > |
| > | In message
| > <4992_1344410910_5022151E_4992_86_1_7358953E06B3044F81495D7AE8F6F6B76EB588B1F0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
| > | "RE: [ispcp] RIR meetings for ISPCP Outreach"
| > | "<alain.bidron@xxxxxxxxxx>" wrote:
| > |
| > | | I am volunteering to help you Akinori.
| > | | Regards
| > | |
| > | |
| > | |
| > | |
| > | |
| > | |
| > | | Alain Bidron
| > | | FT/OLNC/NAD/EAS/NAN
| > | |
| > | | Head of Naming Addressing Numbering Unit
| > | |
| > | | tel. + 33 1 57 36 17 24
| > | |
| > | | mob. + 33 6 87 65 90 94
| > | | alain.bidron@xxxxxxxxxx
| > | |
| > | |
| > | | -----Message d'origine-----
| > | | De : owner-ispcp@xxxxxxxxxxxxxx [mailto:owner-ispcp@xxxxxxxxxxxxxx] De
| > la part de MAEMURA Akinori
| > | | Envoy・: mercredi 8 ao皦 2012 03:26
| > | | タ : mike@xxxxxxxxxx; ispcp@xxxxxxxxx
| > | | Objet : Re: [ispcp] RIR meetings for ISPCP Outreach
| > | |
| > |
| > | -------------------------------------------------------------------------------------------------------------------------------------------------------
| > | | ------
| > | |
| > | | Oups, votre interlocuteur continue de vous ecrire a votre ancienne
| > adresse email : @orange-ftgroup.com. Veuillez lui demander de mettre a
| > jour son carnet d'adresses. Vous pouvez le faire en utilisant ce <a
| > href="http://pratique.itn.ftgroup/FR/produitsetservices/messagerie/boitesperso/Documents/nouvelle_adresse.msg";>modele</a>
| > d'email. Merci
| > | |
| > | |
| > | | Oops, your contact is still using your old email address
| > @orange-ftgroup.com. Please could you tell them to update their address
| > book details for you?
| > | | You can use this email <a
| > href="http://pratique.itn.ftgroup/FR/produitsetservices/messagerie/boitesperso/Documents/nouvelle_adresse.msg";>template</a>
| > if you like. Thanks
| > | |
| > |
| > | -------------------------------------------------------------------------------------------------------------------------------------------------------
| > | | ------
| > | |
| > | |
| > | |
| > | | 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.)
| > | | |
| > | | |
| > | | |
| > | |
| > | |
| > _________________________________________________________________________________________________________________________
| > | |
| > | | Ce message et ses pieces jointes peuvent contenir des informations
| > confidentielles ou privilegiees et ne doivent donc
| > | | pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
| > recu ce message par erreur, veuillez le signaler
| > | | a l'expediteur et le detruire ainsi que les pieces jointes. Les
| > messages electroniques etant susceptibles d'alteration,
| > | | France Telecom - Orange decline toute responsabilite si ce message a
| > ete altere, deforme ou falsifie. Merci.
| > | |
| > | | This message and its attachments may contain confidential or
| > privileged information that may be protected by law;
| > | | they should not be distributed, used or copied without authorisation.
| > | | If you have received this email in error, please notify the sender and
| > delete this message and its attachments.
| > | | As emails may be altered, France Telecom - Orange is not liable for
| > messages that have been modified, changed or falsified.
| > | | Thank you.
| > | |
| > |
| >
|
|
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|