- ispcp - lists.icann.org

testing -- everybody on ISPCP list can ignore -- except Wolf-Ulrich
by Mike O'Connor Feb. 13, 2013

Feb. 13, 2013

OK, all you other ISPCP list members can ignore this message. we're testing Wolf-Ulrich's email here Wolf-Ulrich, you're getting 3 copies of this message - one to your t-online.de address directly - one to your Gmail address (to make sure you see it) - one to via ISPCP list why don't you check and make sure you got all three. if you did, we've done it! thanks Glen and Gisella! mikey On Feb 13, 2013, at 10:32 AM, Glen de Saint Géry <Glen(a)icann.org> wrote: > > Hi Mikey, > > please try sending him an email via his "Wolf-Ulrich Knoben" <Wolf-Ulrich.Knoben(a)t-online.de> address now please > > I think I may have fixed the list problem, let's see if the ISP allows it through! > > Thanks > > Glen > -----Message d'origine----- > De : Mike O'Connor [mailto:mike@haven2.com] > Envoyé : mercredi 13 février 2013 17:28 > À : Glen de Saint Géry > Cc : Gisella Gruber; Mike O'Connor; Wolf-Ulrich.Knoben(a)t-online.de > Objet : Re: URGENT - ISPCP list > > hi Glen, > > i would bet that his new ISP is the problem. T-Online is crazy aggressive at filtering for spam. they blocked a wider IP address range than my whole ISP, just because of one spammer. if you go back through the ISP list, you may see the bounce messages. here's the conversation i had with T-Online after i saw that they had an abuse email contact buried in the bounce messages that i was getting from them. i wrote them a note and they got things fixed. you may have to do the same -- or just subscribe Wolf-Ulrich with his Gmail address instead. > > if that's the problem, it will probably be a problem across all the lists that Wolf-Ulrich is subscribed to. again, subscribing him under that Gmail address may be the easiest solution rather than trying to rassle through all the T-Online stuff. > > m > > >>> Dear Mr. O'Connor, >>> >>> on Mon, 28 Jan 2013 18:44:28 -0600, you wrote: >>> >>>>> to talk to me: 554 IP=216.250.183.109 - A problem occurred. (Ask your >>>>> postmaster for help or to contact tosa(a)rx.t-online.de to clarify.) (BL) >>> >>> Regrettably parts of a bigger IP range including the mentioned IP had >>> been blocked by our protection system due to impairments and complaints. >>> We will unblock your IP. Please notice that it may take up to 24 hours >>> until the change shows acute effect. >>> >>> Please excuse any inconveniences, but we do not see other possibilities >>> to react to the millions of junkmails we receive at present. Thank you >>> for your appreciation. >>> >>> Kind regards >>> Herbert Gründner >>> >>> Deutsche Telekom AG >>> GLS, Group Information Security >>> SDA-GIS / Abuse >>> T-Online-Allee 1 >>> D-64295 Darmstadt >>> >>> E-Mail: abuse(a)rx.t-online.de >>> http://postmaster.t-online.de >>> http://www.t-online.de/abuse >>> http://www.telekom.de > On Feb 13, 2013, at 10:17 AM, Glen de Saint Géry <Glen(a)icann.org> wrote: > >> Dear Gisella, >> >> Wolf-Ulrich is subscribed to the list as "Wolf-Ulrich Knoben" <Wolf-Ulrich.Knoben(a)t-online.de> >> I cannot make out why he is not receiving emails, I will pull up the list and look. >> >> Thanks, >> >> Glen >> >> -----Message d'origine----- >> De : Gisella Gruber >> Envoyé : mercredi 13 février 2013 16:49 >> À : Glen de Saint Géry >> Objet : URGENT - ISPCP list >> >> Hi >> >> Can you please add Wolf-Ulrich to the ISPCP with this email Wolf-Ulrich >> Knoben <Wolf-Ulrich.Knoben(a)t-online.de> >> >> He is not receiving the notifications. >> >> I will then test and THEN add his gmail if need be >> >> Thanks >> >> >> On 13/02/2013 15:37, "Mike O'Connor" <mike(a)haven2.com> wrote: >> >>> hi Wolf-Ulrich, >>> >>> i'd say it's pretty definite that you're not getting the notices from the >>> ISPCP list. so i'm adding Gisela on to this thread. >>> >>> Gisella, could you add both of those addresses for Wolf-Ulrich to the >>> ISPCP listserv? i'm suggesting both because his T-Online ISP may be >>> rejecting mail from ICANN -- they rejected mail from my server until i >>> intervened. the wuknoben(a)gmail.com address will get through to him for >>> sure. >>> >>> thanks, >>> >>> mikey >>> >>> >>> >>> On Feb 13, 2013, at 9:24 AM, tony holmes <tonyarholmes(a)btinternet.com> >>> wrote: >>> >>>> Yes the call is 16.30 tomorrow >>>> Tony >>>> >>>> Sent from my iPhone >>>> >>>> >>>> On 13 Feb 2013, at 14:56, "Wolf-Ulrich.Knoben(a)t-online.de" >>>> <Wolf-Ulrich.Knoben(a)t-online.de> wrote: >>>> >>>>> Do we stay with the call tomorrow at 16:30 UTC? I didn't yet see the >>>>> details. I'd have to reschedule other potential appointments in case. >>>>> Please advise. >>>>> >>>>> Wolf-Ulrich >>>>> >>>>> >>>>> -----Original Message----- >>>>> Date: Mon, 11 Feb 2013 16:19:54 +0100 >>>>> Subject: Re: [ispcp] [ispcp] ISPCP call >>>>> From: "Novoa, Osvaldo" <onovoa(a)Antel.com.uy> >>>>> To: tony holmes <tonyarholmes(a)btinternet.com> >>>>> >>>>> Thurday is fine for me >>>>> >>>>> El 11/02/2013, a las 12:29, "tony holmes" >>>>> <tonyarholmes(a)btinternet.com<mailto:tonyarholmes@btinternet.com>> >>>>> escribi??: >>>>> >>>>> >>>>> >>>>> Sure, will do. >>>>> Tony >>>>> >>>>> -----Original Message----- >>>>> From: Mike O'Connor [mailto:mike@haven2.com] >>>>> Sent: 11 February 2013 13:54 >>>>> To: tony holmes >>>>> Cc: Mike O'Connor; >>>>> Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de>; >>>>> wuknoben(a)gmail.com<mailto:wuknoben@gmail.com>; >>>>> ispcp(a)icann.org<mailto:ispcp@icann.org> >>>>> Subject: Re: [ispcp] [ispcp] ISPCP call >>>>> >>>>> the Thursday time is fine with me. can you ping Gisella so she has the >>>>> call >>>>> on her announcement schedule? >>>>> >>>>> Wolf-Urich, are you getting these posts via the list? i copied your >>>>> Gmail >>>>> account on this message to make sure you got it. >>>>> >>>>> m >>>>> >>>>> On Feb 11, 2013, at 7:49 AM, "tony holmes" >>>>> <tonyarholmes(a)btinternet.com<mailto:tonyarholmes@btinternet.com>> >>>>> wrote: >>>>> >>>>>> I was sure the details had been circulated but with everything else >>>>> going >>>>> on >>>>>> I may be wrong. Apologies, particularly as this was the date we agreed >>>>> in >>>>>> LA. Its best think we postpone and reschedule. >>>>>> >>>>>> How does Thursday 14th Feb at 16.30 UTC work? >>>>>> >>>>>> This also means we need to fix the provisional agenda for our ISPCP >>>>> meeting >>>>>> in Beijing via email. I'll circulate a proposal later. >>>>>> >>>>>> Regards >>>>>> tony >>>>>> >>>>>> -----Original Message----- >>>>>> From: owner-ispcp(a)gnso.icann.org<mailto:owner-ispcp@gnso.icann.org> >>>>> [mailto:owner-ispcp@gnso.icann.org] On >>>>>> Behalf Of Mike O'Connor >>>>>> Sent: 11 February 2013 13:32 >>>>>> To: >>>>> Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de> >>>>>> Cc: tony holmes; ispcp(a)icann.org<mailto:ispcp@icann.org> >>>>>> Subject: Re: [ispcp] [ispcp] ISPCP call >>>>>> >>>>>> hi Wolf-Urich, >>>>>> >>>>>> looking back, i don't see a meeting invitation on the ispcp list. you >>>>> must >>>>>> be subscribed, because i got your messages through the list. i just >>>>> don't >>>>>> think the meeting announcement ever got sent. >>>>>> >>>>>> Tony, if you decide to proceed with the call, can you circulate the >>>>> details? >>>>>> i'd push them out to the list myself, but i don't have them. >>>>>> >>>>>> thanks, >>>>>> >>>>>> mikey >>>>>> >>>>>> >>>>>> On Feb 11, 2013, at 7:08 AM, >>>>> Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de> >>>>> wrote: >>>>>> >>>>>>> >>>>>>> It matches exactly with the prep call of the GNSO council chairs for >>>>> the >>>>>>> next council meeting. So I have a real problem. >>>>>>> Unfortunately I didn't receive any ISPCP call details (bridge) etc. >>>>> in >>>>>>> advance. Maybe my email-address is still not on the list. >>>>>>> >>>>>>> Wolf-Ulrich >>>>>>> >>>>>>> -----Original Message----- >>>>>>> Date: Mon, 11 Feb 2013 13:45:57 +0100 >>>>>>> Subject: RE: [ispcp] ISPCP call >>>>>>> From: "tony holmes" >>>>> <tonyarholmes(a)btinternet.com<mailto:tonyarholmes@btinternet.com>> >>>>>>> To: >>>>> >>>>> <Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de>>, >>>>> <ispcp(a)icann.org<mailto:ispcp@icann.org>> >>>>>>> >>>>>>> >>>>>>> The call is today at 15.00 UTC >>>>>>> Details have been circulated. >>>>>>> Tony >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: owner-ispcp(a)gnso.icann.org<mailto:owner-ispcp@gnso.icann.org> >>>>> [mailto:owner-ispcp@gnso.icann.org] On >>>>>>> Behalf Of >>>>> Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de> >>>>>>> Sent: 11 February 2013 11:12 >>>>>>> To: ispcp(a)icann.org<mailto:ispcp@icann.org> >>>>>>> Subject: [ispcp] ISPCP call >>>>>>> >>>>>>> >>>>>>> Guys, >>>>>>> >>>>>>> do we have an ISP call today, or when is the next call scheduled? >>>>>>> >>>>>>> Wolf-Ulrich >>>>>> >>>>>> >>>>>> PHONE: 651-647-6109, FAX: 866-280-2356, WEB: >>>>> www.haven2.com<http://www.haven2.com>, HANDLE: >>>>>> OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) >>>>> >>>>> >>>>> PHONE: 651-647-6109, FAX: 866-280-2356, WEB: >>>>> www.haven2.com<http://www.haven2.com>, HANDLE: >>>>> OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) >>>>> >>>>> >>>>> >>>>> ________________________________ >>>>> El presente correo y cualquier posible archivo adjunto está dirigido >>>>> únicamente al destinatario del mensaje y contiene información que puede >>>>> ser confidencial. Si Ud. no es el destinatario correcto por favor >>>>> notifique al remitente respondiendo anexando este mensaje y elimine >>>>> inmediatamente el e-mail y los posibles archivos adjuntos al mismo de >>>>> su >>>>> sistema. Está prohibida cualquier utilización, difusión o copia de este >>>>> e-mail por cualquier persona o entidad que no sean las específicas >>>>> destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con >>>>> respecto a cualquier comunicación que haya sido emitida incumpliendo >>>>> nuestra Política de Seguridad de la Información >>>>> >>>>> >>>>> This e-mail and any attachment is confidential and is intended solely >>>>> for the addressee(s). If you are not intended recipient please inform >>>>> the sender immediately, answering this e-mail and delete it as well as >>>>> the attached files. Any use, circulation or copy of this e-mail by any >>>>> person or entity that is not the specific addressee(s) is prohibited. >>>>> ANTEL is not responsible for any communication emitted without >>>>> respecting our Information Security Policy. >>>>> >>>>> >>>>> >>> >>> >>> PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: >>> OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) >>> > > > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

Re: [ispcp] [ispcp] ISPCP call
by tony holmes Feb. 13, 2013

Feb. 13, 2013

Yes the call is 16.30 tomorrow Tony Sent from my iPhone On 13 Feb 2013, at 14:56, "Wolf-Ulrich.Knoben(a)t-online.de" <Wolf-Ulrich.Knoben(a)t-online.de> wrote: > Do we stay with the call tomorrow at 16:30 UTC? I didn't yet see the > details. I'd have to reschedule other potential appointments in case. > Please advise. > > Wolf-Ulrich > > > -----Original Message----- > Date: Mon, 11 Feb 2013 16:19:54 +0100 > Subject: Re: [ispcp] [ispcp] ISPCP call > From: "Novoa, Osvaldo" <onovoa(a)Antel.com.uy> > To: tony holmes <tonyarholmes(a)btinternet.com> > > Thurday is fine for me > > El 11/02/2013, a las 12:29, "tony holmes" > <tonyarholmes(a)btinternet.com<mailto:tonyarholmes@btinternet.com>> > escribi??: > > > > Sure, will do. > Tony > > -----Original Message----- > From: Mike O'Connor [mailto:mike@haven2.com] > Sent: 11 February 2013 13:54 > To: tony holmes > Cc: Mike O'Connor; > Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de>; > wuknoben(a)gmail.com<mailto:wuknoben@gmail.com>; > ispcp(a)icann.org<mailto:ispcp@icann.org> > Subject: Re: [ispcp] [ispcp] ISPCP call > > the Thursday time is fine with me. can you ping Gisella so she has the > call > on her announcement schedule? > > Wolf-Urich, are you getting these posts via the list? i copied your > Gmail > account on this message to make sure you got it. > > m > > On Feb 11, 2013, at 7:49 AM, "tony holmes" > <tonyarholmes(a)btinternet.com<mailto:tonyarholmes@btinternet.com>> > wrote: > >> I was sure the details had been circulated but with everything else > going > on >> I may be wrong. Apologies, particularly as this was the date we agreed > in >> LA. Its best think we postpone and reschedule. >> >> How does Thursday 14th Feb at 16.30 UTC work? >> >> This also means we need to fix the provisional agenda for our ISPCP > meeting >> in Beijing via email. I'll circulate a proposal later. >> >> Regards >> tony >> >> -----Original Message----- >> From: owner-ispcp(a)gnso.icann.org<mailto:owner-ispcp@gnso.icann.org> > [mailto:owner-ispcp@gnso.icann.org] On >> Behalf Of Mike O'Connor >> Sent: 11 February 2013 13:32 >> To: > Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de> >> Cc: tony holmes; ispcp(a)icann.org<mailto:ispcp@icann.org> >> Subject: Re: [ispcp] [ispcp] ISPCP call >> >> hi Wolf-Urich, >> >> looking back, i don't see a meeting invitation on the ispcp list. you > must >> be subscribed, because i got your messages through the list. i just > don't >> think the meeting announcement ever got sent. >> >> Tony, if you decide to proceed with the call, can you circulate the > details? >> i'd push them out to the list myself, but i don't have them. >> >> thanks, >> >> mikey >> >> >> On Feb 11, 2013, at 7:08 AM, > Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de> > wrote: >> >>> >>> It matches exactly with the prep call of the GNSO council chairs for > the >>> next council meeting. So I have a real problem. >>> Unfortunately I didn't receive any ISPCP call details (bridge) etc. > in >>> advance. Maybe my email-address is still not on the list. >>> >>> Wolf-Ulrich >>> >>> -----Original Message----- >>> Date: Mon, 11 Feb 2013 13:45:57 +0100 >>> Subject: RE: [ispcp] ISPCP call >>> From: "tony holmes" > <tonyarholmes(a)btinternet.com<mailto:tonyarholmes@btinternet.com>> >>> To: > <Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de>>, > <ispcp(a)icann.org<mailto:ispcp@icann.org>> >>> >>> >>> The call is today at 15.00 UTC >>> Details have been circulated. >>> Tony >>> >>> -----Original Message----- >>> From: owner-ispcp(a)gnso.icann.org<mailto:owner-ispcp@gnso.icann.org> > [mailto:owner-ispcp@gnso.icann.org] On >>> Behalf Of > Wolf-Ulrich.Knoben(a)t-online.de<mailto:Wolf-Ulrich.Knoben@t-online.de> >>> Sent: 11 February 2013 11:12 >>> To: ispcp(a)icann.org<mailto:ispcp@icann.org> >>> Subject: [ispcp] ISPCP call >>> >>> >>> Guys, >>> >>> do we have an ISP call today, or when is the next call scheduled? >>> >>> Wolf-Ulrich >> >> >> PHONE: 651-647-6109, FAX: 866-280-2356, WEB: > www.haven2.com<http://www.haven2.com>, HANDLE: >> OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) > > > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: > www.haven2.com<http://www.haven2.com>, HANDLE: > OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) > > > > ________________________________ > El presente correo y cualquier posible archivo adjunto está dirigido > únicamente al destinatario del mensaje y contiene información que puede > ser confidencial. Si Ud. no es el destinatario correcto por favor > notifique al remitente respondiendo anexando este mensaje y elimine > inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su > sistema. Está prohibida cualquier utilización, difusión o copia de este > e-mail por cualquier persona o entidad que no sean las específicas > destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con > respecto a cualquier comunicación que haya sido emitida incumpliendo > nuestra Política de Seguridad de la Información > > > This e-mail and any attachment is confidential and is intended solely > for the addressee(s). If you are not intended recipient please inform > the sender immediately, answering this e-mail and delete it as well as > the attached files. Any use, circulation or copy of this e-mail by any > person or entity that is not the specific addressee(s) is prohibited. > ANTEL is not responsible for any communication emitted without > respecting our Information Security Policy. > > >

1 0

RV: GNSO Independent Review Criteria Follow-Up
by Novoa, Osvaldo Feb. 13, 2013

Feb. 13, 2013

All, FYI. I think we must keep an eye on this. Regards, Osvaldo ________________________________ De: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] En nombre de Robert Hoggarth Enviado el: Martes, 12 de Febrero de 2013 21:39 Para: council(a)gnso.icann.org List CC: Glen de Saint Géry Asunto: [council] GNSO Independent Review Criteria Follow-Up Dear Jonathan and Council Members; As one of the last action items from the January 17 GNSO Council Meeting (see - https://community.icann.org/display/gnsocouncilmeetings/Action+Items ), I agreed to send a update and to circulate the document links I reviewed with you regarding my briefing on the the future GNSO independent Review effort. I am pleased to report that at least 24 people have reviewed and downloaded the slides I shared at the last meeting (see - http://gnso.icann.org/en/node/35555 ). Also, as a result of the interest in the presentation during the Council meeting, I had the opportunity to provide more detailed follow-up briefings to leaders of the Intellectual Property and Business Constituencies. So far, review of the community wiki project page detailing the prospective "macro" and "micro" review criteria I spoke about has seen less traffic. If you are interested in learning more about the effort and offering any opinions about how the review criteria can be adjusted or improved, please visit the GNSO Independent Review Planning wiki space at this link - https://community.icann.org/display/GNSO/GNSO+Review+Plan+Framework . You can share any thoughts, comments or opinions regarding the effort in the comments section of any of the associated wiki pages or directly with me via email. At the very least you may wish to keep the links above for future reference. Best regards, Rob Hoggarth ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

ISPCP call
by Wolf-Ulrich.Knoben＠t-online.de Feb. 11, 2013

Feb. 11, 2013

Guys, do we have an ISP call today, or when is the next call scheduled? Wolf-Ulrich

4 7

FW: ISPCP call
by tony holmes Feb. 11, 2013

Feb. 11, 2013

Sorry Guys My fault, I sent the email below to Gisella but failed to follow up. My fault, not Gisella's particularly as she'd already arranged an ISPCP outreach team call last week. I think that's where I got confused and was sure I'd seen the call details. Let me know about the 14th, unfortunately I can't make it earlier than 16.30 that day. Tony From: tony holmes [mailto:tonyarholmes@btinternet.com] Sent: 30 January 2013 00:04 To: Gisella Gruber (Gisella.Gruber(a)icann.org) Subject: ISPCP call Dear Gisella I hope this finds you well. It's been proposed that next ISPCP call should be held on Monday 11th February commencing at 15.00 UTC. Could I seek your assistance in arranging the call. Best Regards tony

1 0

Fwd: ICANN News Alert -- Webinar: Internationalized Domain Name (IDN) Variant: Examining the User Experience Implication of the Active Variant TLDs
by Mike O'Connor Feb. 2, 2013

Feb. 2, 2013

here's the official announcement of the User Experience report. again -- a great report and worthy of our comment, in my view mikey Begin forwarded message: > From: "ICANN News Alert" <communications(a)icann.org> > Subject: ICANN News Alert -- Webinar: Internationalized Domain Name (IDN) Variant: Examining the User Experience Implication of the Active Variant TLDs > Date: February 1, 2013 7:18:39 PM CST > To: <mike(a)haven2.com> > > > News Alert > > http://www.icann.org/en/news/announcements/announcement-01feb13-en.htm > > Webinar: Internationalized Domain Name (IDN) Variant: Examining the User Experience Implication of the Active Variant TLDs > 1 February 2013 > Date: 13 February 2013 > Time: 13:00 – 14:50 UTC (5:00am – 6:30am PST) > Adobe Connect: http://icann.adobeconnect.com/idnvarianttld/ > Dial In: 1-800-550-6865 or 1-213-233-3193 > International numbers available here > Meeting ID: 46389 > > Internationalized Domain Names (IDNs) serve as powerful tools for broadening the Internet's capacity and accessibility; however, they also raise novel issues. One important issue concerns "variants" which occur when a single character can be identified with two or more different Unicode Code Points with graphic representations that may or may not be visually similar. IDN variants contain one or more such characters and therefore, if not handled correctly, might result in user confusion or a poor user experience. > > In an effort to develop potential solutions for the delegation of IDN variant Top-Level Domains (TLDs), IDN Variant Project Teams, consisting of volunteers, subject matter expert consultants and ICANN staff, have conducted case studies in six scripts, produced an integrated report, and are currently underway to completing three projects investigating potential solutions for IDN Variant TLDs delegation. > > One of these projects is called the Examining the User Experience Implications of Active Variant TLDs Project (P6). The purpose of the project is to gain an understanding of issues that could arise from activating IDN Variant TLDs and offer recommendations to users to avoid such issues. Examples of user roles that have been identified include registrants, registrars, registry operators, system administrators, network operators, application developers, and end users. > > Project team has published for public comment the Draft Final Report for Examining the User Experience Implications of Active Variant TLDs and is seeking to establish a dialog with the community to refine proposed principles, impacts and recommendations of the study. > > This webinar is offered to complement that process both by presenting the key concepts and gathering user input. > > The IDN Variant TLDs Program team is looking forward to your participation. > > > > This message was sent to mike(a)haven2.com from: > ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 > Email Marketing by > > Manage Your Subscription > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

IDN Variants -- User (ie ISP) experience -- worthy of conversation and comment
by Mike O'Connor Feb. 1, 2013

Feb. 1, 2013

hi all, i ran inter Peter Jennings at breakfast yesterday and he strongly encouraged me to take a look at the recently published report on the user experience implications of active variant TLDs. now that i've read it, i strongly encourage *you* to read it as there are profound implications for our members (who will very likely be the front-line point of support when many of these issues arise for our customers). mikey here's a link to the public-comment page https://www.icann.org/en/news/public-comment/variant-ux-18jan13-en.htm here's a chunk out of the table of contents just to give you a taste of what i'm talking about; 5. Challenges Related to Active Variant TLDs........................................................................ 26 ] 5.1. Challenges with the Use of Variants............................................................................. 27 • 5.1.1. Different Users cannot find the complete set of variants for a primary label....... 27 • 5.1.2. Variants not intuitive............................................................................................. 27 • 5.1.3. Variants are delegated independently ................................................................... 28 • 5.1.4. Variants defined inconsistently............................................................................. 28 • 5.1.5. Variants displayed inconsistently ......................................................................... 28 • 5.1.6. Variants cannot be input by the user..................................................................... 29 • 5.1.7. Unable to distinguish specific variants ................................................................. 29 • 5.1.8. Identifier not bound to all variants........................................................................ 29 • 5.1.9. Accessibility and privacy impacted ...................................................................... 29 • 5.1.10. Variants not searchable ......................................................................................... 30 • 5.1.11. Search rankings unpredictable .............................................................................. 30 • 5.1.12. Search optimization affected by variants .............................................................. 30 • 5.1.13. Variants not part of URL/URI/IRI ........................................................................ 31 • 5.1.14. Variants cause session re-establishment ............................................................... 31 5.2. Challenges in the Registration and Management of Variants....................................... 31 • 5.2.1. Management across IDN TLDs inconsistent ........................................................ 32 • 5.2.2. Registration for SLDs across TLDs inconsistent.................................................. 32 • 5.2.3. Inconsistent association of ASCII and IDN TLDs ............................................... 32 • 5.2.4. Software support inadequate................................................................................. 33 • 5.2.5. Registration system not straightforward to localize.............................................. 33 • 5.2.6. Registration information inconsistent ................................................................... 34 • 5.2.7. Trademark protection tracking complex ............................................................... 34 • 5.2.8. Trademark protection dispute process complex ................................................... 34 5.3. Challenges in the Configuration and Diagnostics of Variants...................................... 35 • 5.3.1. Software configuration not supported................................................................... 35 • 5.3.2. Cannot associate variants for configuration.......................................................... 35 • 5.3.3. Compounded certificate management................................................................... 36 • 5.3.4. DNSSEC validation inconsistent .......................................................................... 36 • 5.3.5. Log and history searching does not match............................................................ 36 • 5.3.6. Network traffic statistics incomplete .................................................................... 37 • 5.3.7. Caching infrastructure inefficient ......................................................................... 37 • 5.3.8. Diagnostic and troubleshooting tools incompatible.............................................. 37 • 5.3.9. Forensics significantly more complicated ............................................................ 38 5.4. Traceability between User Principles and Variant Challenges..................................... 39 PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

FW: Non Contracted Parties House Inter-sessional Information
by tony holmes Jan. 30, 2013

Jan. 30, 2013

FYI From: Glen de Saint Géry [mailto:Glen@icann.org] Sent: 30 January 2013 00:33 To: Marilyn Cade ; Benedetta Rossi <bc-secretariat(a)icann.org> (bc-secretariat(a)icann.org) Rosette, Kristina; Metalitz, Steven; Claudio DiGangi (cdigangi(a)inta.org) tony holmes (tonyarholmes(a)btinternet.com) Novoa, Osvaldo; Wolf-Ulrich.Knoben(a)t-online.de; Robin Gross; William Drake; Alain Berranger Cc: gnso-secs(a)icann.org; Robert Hoggarth; David Olive; Susie Johnson Subject: Non Contracted Parties House Inter-sessional Information Dear All, All the information relating to the Non Contracted Parties House Inter-sessional meeting on Tuesday 28 and Wednesday 29 January 2013 can be found on the Wiki pages https://community.icann.org/display/ncph/InterSessional+-+January+2013 Whether you are attending the meeting in person or by remote means, within the pages of this wiki space, you will find general information about the venue, agenda, and related topics. If you find that something important is missing, please alert one of our GNSO Staff personnel and we will work to locate and publish the information as quickly as possible. For meeting transcripts, documents, presentations, etc., please consult: * 2013 GNSO-NCPH Intersessional Meeting Agenda <https://community.icann.org/display/ncph/2013+GNSO-NCPH+Intersessional+Meet ing+Agenda> * Documents <https://community.icann.org/display/ncph/Documents> * Presentations <https://community.icann.org/display/ncph/Presentations> * Transcripts <https://community.icann.org/display/ncph/Transcripts> Please be so kind as to share this information with your groups so that they can follow via the transcripts that will be posted as soon as they are received. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat <mailto:gnso.secretariat@gnso.icann.org> gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

FW: Dial in details for remote participation for ISP members, LA Intersessional 28, 29, 30th January
by Wolf-Ulrich.Knoben＠t-online.de Jan. 28, 2013

Jan. 28, 2013

FYI -----Original Message----- Date: Mon, 28 Jan 2013 17:15:18 +0100 Subject: Dial in details for remote participation for ISP members, LA Intersessional 28, 29, 30th January From: Nathalie Peregrine <nathalie.peregrine(a)icann.org> To: "tony holmes (tonyarholmes(a)btinternet.com)" <tonyarholmes(a)btinternet.com>, "Wolf-Ulrich Knoben (Wolf-Ulrich.Knoben(a)t-online.de)" <Wolf-Ulrich.Knoben(a)t-online.de>, "Novoa, Osvaldo (onovoa(a)Antel.com.uy)" <onovoa(a)Antel.com.uy> Dear all, PLEASE NOTE THERE HAVE BEEN AGENDA CHANGES AFFECTING THE REMOTE PARTICIPATION DETAILS SENT EARLIER DURING THE WEEK. PLEASE THEREFORE REFER TO THE INFORMATION BELOW IN ORDER TO TAKE PART REMOTELY IN THE LA INTERSESSIONAL MEETING ON THE 28TH, 29TH, 30TH JANUARY 2013. Please note that there will be audio streaming in the adobe connect rooms. If you wish to take part orally however, you will need to dial in to the audio bridge. Dial in numbers are to be found at the bottom of this email. Please share these details with your members. TUESDAY JANUARY 29 2013 Ø TUESDAY MORNING: · CSG MEETING POSTEL A INCLUDING SG ROUNDTABLES WITH CEO, 09:00 - 10:30 LOCAL TIME. For other times: http://tinyurl.com/bkc97z6 [1] PASSWORD CSG Adobe Connect room: https://icann.adobeconnect.com/postela [2] · CSG MEETING IN POSTEL A, 10:45 - 12:15 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/A5G7RD5 [3] PASSWORD POSTEL A ADOBE CONNECT ROOM: HTTPS://ICANN.ADOBECONNECT.COM/POSTELA [4] · _ISP OPTIONAL BREAKOUT MEETING ROOM FROM 09:00 - 14:00 LOCAL TIME: KLEINROCK ROOM. __AUDIO PASSCODE: KLEINROCK. NO AUDIO RECORDING NOR ADOBE CONNECT ROOM AVAILABLE. _ _ _ Ø TUESDAY AFTERNOON: · STAKEHOLDER ENGAGEMENT DIALOGUE IN POSTEL A &AMP;B, 14:00 - 16:00 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/9WJPFSJ [5] PASSWORD STAKEHOLDER Adobe Connect room : https://icann.adobeconnect.com/postelaandb [6] · NEW GTLD BRIEFING IN POSTEL A &AMP;B, 16:00 - 17:00 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/AQX33DK [7] PASSWORD GTLD Adobe Connect room : https://icann.adobeconnect.com/postelaandb [8] · RAA NEGOTIATION BRIEFING IN POSTEL A &AMP;B, 17:00 - 18:00 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/ABG89SP [9] PASSWORD RAA Adobe Connect room : https://icann.adobeconnect.com/postelaandb [10] · WHOIS BRIEFING IN POSTEL A &AMP;B, 18:00 - 19:00 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/BFTXQ4M [11] PASSWORD WHOIS Adobe Connect room : https://icann.adobeconnect.com/postelaandb [12] WEDNESDAY JANUARY 30 2013 Ø WEDNESDAY MORNING: · GNSO TOOLKIT PHASE 2 DIALOGUE IN POSTEL A &AMP;B, 09:00 - 09:30 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/BZG33F9 [13] PASSWORD TOOLKIT Adobe Connect room : https://icann.adobeconnect.com/postelaandb [14] · ICANN &AMP; INTERNET GOVERNANCE IN POSTEL A &AMP;B, 09:30 - 11:30 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/BKSD6GD [15] PASSWORD INTERNET GOVERNANCE Adobe Connect room : https://icann.adobeconnect.com/postelaandb [16] · COMMUNITY NEEDS DIALOGUE IN POSTEL A &AMP;B, 11:30 - 12:00 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/AK99LGM [17] PASSWORD COMMUNITY Adobe Connect room : https://icann.adobeconnect.com/postelaandb [18] · LUNCH WITH CEO IN POSTEL A &AMP;B, 12:00 - 13:30 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/AEG6H48 [19] PASSWORD CEO Adobe Connect room : https://icann.adobeconnect.com/postelaandb [20] · _ISP OPTIONAL BREAKOUT MEETING ROOM FROM 09:00 - 14:00 LOCAL TIME: KLEINROCK ROOM. __AUDIO PASSCODE: KLEINROCK. NO AUDIO RECORDING NOR ADOBE CONNECT ROOM AVAILABLE. _ _ _ Ø WEDNESDAY AFTERNOON: · FY14 BUDGET PROCESS AND SO AC REQUESTS IN POSTEL A &AMP;B, 15:00 - 16:30 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/APBGW49 [21] PASSWORD BUDGET Adobe Connect room : https://icann.adobeconnect.com/postelaandb [22] · WRAP UP DIALOGUE IN POSTEL A &AMP;B, 16:30 - 17:00 LOCAL TIME. FOR OTHER TIMES: HTTP://TINYURL.COM/B3AJEC6 [23] PASSWORD WRAP UP Adobe Connect room : https://icann.adobeconnect.com/postelaandb [24] · MEETING WITH THE BOARD IN POSTEL A &AMP; B, 17:00 - 18:00 LOCAL TIME. FOR OTHER TIMES: http://tinyurl.com/b6pu2na [25] PASSWORD BOARD Adobe Connect room : https://icann.adobeconnect.com/postelaandb [26] _ _ DIAL IN NUMBERS: COUNTRY TOLL NUMBERS Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND Land Line: 106-33-203 0-800-9-14610 FINLAND Mobile: 09-106-33-203 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 06-800-12755 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY 39-02-3600-6007 800-986-383 JAPAN OSAKA: 81-6-7739-4799 0066-33-132439 JAPAN TOKYO: 81-3-5539-5191 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 MALAYSIA 1-800-81-3065 MEXICO 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 POLAND 00-800-1212572 PORTUGAL 8008-14052 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 Kind regards Nathalie GNSO Secretariat Links: ------ [1] http://tinyurl.com/bkc97z6 [2] https://icann.adobeconnect.com/postela [3] HTTP://TINYURL.COM/A5G7RD5 [4] HTTPS://ICANN.ADOBECONNECT.COM/POSTELA [5] HTTP://TINYURL.COM/9WJPFSJ [6] https://icann.adobeconnect.com/postelaandb [7] HTTP://TINYURL.COM/AQX33DK [8] https://icann.adobeconnect.com/postelaandb [9] HTTP://TINYURL.COM/ABG89SP [10] https://icann.adobeconnect.com/postelaandb [11] HTTP://TINYURL.COM/BFTXQ4M [12] https://icann.adobeconnect.com/postelaandb [13] HTTP://TINYURL.COM/BZG33F9 [14] https://icann.adobeconnect.com/postelaandb [15] HTTP://TINYURL.COM/BKSD6GD [16] https://icann.adobeconnect.com/postelaandb [17] HTTP://TINYURL.COM/AK99LGM [18] https://icann.adobeconnect.com/postelaandb [19] HTTP://TINYURL.COM/AEG6H48 [20] https://icann.adobeconnect.com/postelaandb [21] HTTP://TINYURL.COM/APBGW49 [22] https://icann.adobeconnect.com/postelaandb [23] HTTP://TINYURL.COM/B3AJEC6 [24] https://icann.adobeconnect.com/postelaandb [25] http://tinyurl.com/b6pu2na [26] https://icann.adobeconnect.com/postelaandb

1 0

FW: RE: [council] GNSO ATRT2 Applicants (minor change to improve clarity)
by Wolf-Ulrich.Knoben＠t-online.de Jan. 27, 2013

Jan. 27, 2013

FYI Wolf-Ulrich -----Original Message----- Date: Sun, 27 Jan 2013 11:11:57 +0100 Subject: RE: [council] GNSO ATRT2 Applicants (minor change to improve clarity) From: Glen de Saint Géry <Glen(a)icann.org> To: "council(a)gnso.icann.org List" <council(a)gnso.icann.org> Dear All, Voting closed on Saturday 26 January 2013 at 23h59 UTC. CONTRACTED PARTIES HOUSE (TOTAL 7 VOTES) (6 people voted - I person did not vote) Result: 5 people abstained 1 person supported each of the candidates NON CONTRACTED PARTIES HOUSE (TOTAL 13 VOTES) (11 people voted - 2 people did not vote) Result: 9 votes in support of Olivier Muron 8 votes in support of Marie-Laure Lemineur Sixty percent support of both houses represented in the Council is required for endorsement. The candidates have not obtained that level of support. The list of endorsements obtained via the bottom-up process of stakeholder group nominations will be deemed final and forwarded to ICANN. Thomas Barrett M North America RrSG Endorsed Brian Cute M North America RySG Endorsed Avri Doria F North America NCSG Endorsed Michael Roberts M North America CSG Endorsed Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org DE : owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] DE LA PART DE Volker Greimann ENVOYé : samedi 26 janvier 2013 10:20 À : Jonathan Robinson CC : council(a)gnso.icann.org OBJET : Re: [council] GNSO ATRT2 Applicants (minor change to improve clarity) Dear Jonathan, thank you for making sure the process remains on track despite the difficult deadlines and our inablility to resolve this early on our last call. During the Amsterdam meeting the RrSG councilors have met and discussed the ballot, and we have elected to abstain on a vote on the two additional candidates. We believe the GNSO has endorsed four candidates for the ATRT that are highly capable for the role. The questions of geographic and gender diversity are fully available to the Chairs of the Board and GAC through the full slate of candidates from all parts of the community. Best regards, Volker Greimann All, The GNSO Council has now received endorsements from all four SGs. As a reminder, the GNSO process is as follows: The Council will consider the resulting list of up to four nominees at its next teleconference. If the list does not meet the above mentioned diversity objectives, the Council as a whole may choose to endorse up to two additional candidates from the applicant pool who would help to give the list of GNSO nominees the desired balance. In this case, the Council would hold a vote during its teleconference, with sixty percent support of both houses represented in the Council being required for endorsement. If no candidate obtains that level of support, the list of endorsements obtained via the bottom-up process of stakeholder group nominations will be deemed final and forwarded to ICANN. Please note: · The candidate list meets the GNSO agreed gender diversity requirements in that not all endorsed candidates are of the same gender. · However it does not meet the GNSO agreed geographic diversity requirements in that all endorsed candidates are from a single (North America) ICANN region. Therefore the slate needs to be added to with (up to two) additional SG supported candidates in order to get closer to meeting geographic diversity requirements. The two SG supported candidates that assist us in meeting this requirement are: Marie-Laure Lemineur F Latin America NCSG Olivier Muron M Europe CSG Therefore we will ballot the Council on list (since a teleconference is now not practical ahead of the deadline) in order to see if either or both (of Marie-Laure Lemineur and Olivier Mouron) have the support of 60% of both houses of the Council. PLEASE CAN YOU KEEP AN ALERT VIEW ON THE COUNCIL LIST FOR THE BALLOT WHICH WILL BE AVAILABLE NO LATER THAN 23H59 UTC TODAY (24TH JANUARY 2013). THE BALLOT WILL CLOSE 23H59 UTC ON 26TH JANUARY. Thank-you. Jonathan

1 0