February 2013 - ispcp - lists.icann.org

FW: [council] Current draft of Fadi's requested communication from council
by Wolf-Ulrich.Knoben＠t-online.de Feb. 14, 2013

Feb. 14, 2013

I'd like to put a short discussion about the letter annexed to the agenda today. Clearly BC and IPC are against sending this letter. There shall be a last try to find a conclusion about. Fadi's deadline is end of Feb. We should settle our position. Regards Wolf-Ulrich -----Original Message----- Date: Wed, 13 Feb 2013 00:00:47 +0100 Subject: [council] Current draft of Fadi's requested communication from council From: Mason Cole <mcole(a)5x5com.com> To: "council(a)gnso.icann.org List" <council(a)gnso.icann.org> Council colleagues -- As you know, Fadi requested of the council its input regarding the strawman proposal resulting from the BC's and IPC's request for additional RPMs in new gTLDs. On December 27, I circulated an early draft of a council reply. The communication is due very shortly, and has been taken up by a small group within the council to ensure that all points of view are represented. Because this is an agenda item for our meeting this week, at Maria Farrell's helpful suggestion, I'm sending the current draft to council so we can be prepared to discuss it then. This draft does not reflect additional input of the BC and IPC -- if this is provided prior to the meeting, I'll be happy to forward it to the council. Thanks -- Mason

4 5

Draft agenda for todays call
by tony holmes Feb. 14, 2013

Feb. 14, 2013

DRAFT AGENDA 1. Follow-up on Intercessional meeting in LA 2. Preparations for Beijing 3. ISPCP agenda for Beijing 4. Update on ISP CEO Roundtable meeting 5. Update on WGs 6. AoB Please feel free to add. Tony

2 1

FW: [council] FW: GNSO Council Vice Chair from NCPH
by Wolf-Ulrich.Knoben＠t-online.de Feb. 14, 2013

Feb. 14, 2013

All, Please note below. Jonathan FROM: Metalitz, Steven [mailto:met@msk.com] SENT: 12 February 2013 22:46 TO: Jonathan Robinson (jonathan.robinson(a)ipracon.com) 'Glen de Saint Géry'; Wolf-Ulrich Knoben (wolf-ulrich.knoben(a)t-online.de) CC: Marilyn S. Cade (marilynscade(a)hotmail.com) Robin Gross (robin(a)ipjustice.org) Tony Holmes; Kristina Rosette; Chris LaHatte (chris.lahatte(a)icann.org) SUBJECT: GNSO Council Vice Chair from NCPH Jonathan and colleagues, This is to inform you that CSG and NCSG leadership met on the sidelines of the recent NCPH intersessional meeting and agreed that Wolf Ulrich Knoben will continue to serve as the Vice Chair of the Council from our House for the remainder of this term. The two stakeholder groups also agreed on a protocol for selection of Vice Chair for the term beginning at the ICANN annual meeting in Buenos Aires, and further agreed to meet no later than the second ICANN meeting of 2014 to set procedures for selection of vice chair for the following term and perhaps beyond. The two SGs thank ICANN Ombudsman Chris LaHatte for his assistance in helping us reach this agreement. Steve Metalitz, for CSG

1 0

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