September 2013 - ispcp - lists.icann.org

RV: IGO INGO Report
by Novoa, Osvaldo Sept. 30, 2013

Sept. 30, 2013

Dear All, Mikey asked about a list of all the names and acronyms considered for protection. There is no one list with all the names and acronyms but from the report we can extract: The identifiers loaded into Spec 5 of the new Registry Agreement are the most authoritative: http://www.icann.org/sites/default/files/packages/reserved-names/ReservedNa…; it contains: * RCRC - Scope 1 * IOC - Scope 1 * IGO (GAC list from 22 March 2013<http://www.icann.org/en/news/correspondence/dryden-to-crocker-chalaby-annex…>) - Scope 1 & Scope 2 Lists also being considered by the WG, but not placed on Spec 5 (never a part of GAC advice): * RCRC - Scope 2 (189 Societies + 6 Acronyms; a definitive list of the 189 names has yet to be provided by the RCRC as far as I know) * INGO - Scope 1 (ECOSOC General Consultative Status<http://csonet.org/content/documents/E2011INF4.pdf>) & Scope 2 (ECOSOC Special Consultative Status<http://csonet.org/content/documents/E2011INF4.pdf>) This is the best we have. Best regards, [cid:089413718@27092013-0F94]Osvaldo Novoa Subgerente General Antel Guatemala 1075, Nivel 22 Montevideo, 11800 Uruguay Tel. +598 2928 6400 Fax. +598 2928 6401 ________________________________ 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.

2 3

Fwd: [Ispcp-private] SO-AC Inputs Needed - Recommendations of the Security, Stability & Resiliency Review Team
by Mike O'Connor Sept. 28, 2013

Sept. 28, 2013

hi David and Patrick, i'm the ISPCP rapporteur on this one. i think it's safe to say that our initial response is - we're interested - what's available? - we don't do much of that right now, but we should do better and would appreciate any assistance/resources that can be provided - we'd like to post ISP-focused material on our website (www.ispcp.info) - where do we go from here? thanks, mikey > From: David Olive <david.olive(a)icann.org> > Date: Monday, September 9, 2013 11:24 AM > > Subject: SO-AC Inputs Needed - Recommendations of the Security, Stability & Resiliency Review Team > > Dear SO/AC leaders: > > The ICANN Security team is continuing with its efforts to implement the recommendations of the Security, Stability & Resiliency Review Team. We are seeking guidance from this group on ways to implement Recommendation #13 – ICANN should encourage all Supporting Organizations (and stakeholder groups) to develop and publish SSR-related best practices for their members. > > We are interested in suggestions related to: > Does your SO/AC currently publish best practices or guidance on security-related topics for participants? > If not, what types of best practices or guidance would be useful to your participants? > Where should this be published – on SO/AC pages? on the ICANN website? > As an example, the ccNSO has several pages of resources on security-related topics, see http://ccnso.icann.org/resources/cybercrime-resources.htm and http://ccnso.icann.org/resources/technical-resources.htm. > > Any suggestions you have would be welcomed. Please send them to my attention at patrick.jones at icann.org. > > Best regards, > > Patrick > > > > > > > > > > > > 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

Policy staff Workshop 30th Sep - 4th October
by Nathalie Peregrine Sept. 26, 2013

Sept. 26, 2013

Dear all, Our Policy Staff team is having its annual workshop in Los Angeles next week from Monday 30th September to Friday 4th October included. Whilst scheduled conference calls will not be impacted, our response time to emails might be slightly delayed. We apologise for the inconvenience, Kind regards, The GNSO Secretariat

1 0

RV: Proposed GNSO Improvements Tabulated
by Novoa, Osvaldo Sept. 23, 2013

Sept. 23, 2013

Dear All, I am enclosing a list of the proposed GNSO PDP improvements discussed in the GNSO meeting. I would appreciate it if you could review the proposal and submit comments on it. Best regards, Osvaldo [cid:864154413@23092013-3280]Osvaldo Novoa Subgerente General Antel Guatemala 1075, Nivel 22 Montevideo, 11800 Uruguay Tel. +598 2928 6400 Fax. +598 2928 6401 ________________________________ De: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] En nombre de Marika Konings Enviado el: Lunes, 23 de Septiembre de 2013 10:22 Para: council(a)gnso.icann.org Asunto: [council] Proposed GNSO Improvements Tabulated Dear All, In relation to the action item below, please find attached a tabulated version of the proposed GNSO PDP Improvements discussed during the last meeting. You'll note that some of the comments and possible changes discussed during the last meeting have been included. If I've missed anything, or if there are any other comments / proposed changes you would like to see included, please feel free to share those with the list. As also noted below, Council members are requested to encourage their groups to review the proposed improvements and consider which suggestions can be supported and implemented. With best regards, Marika From: Glen de Saint Géry <Glen(a)icann.org<mailto:Glen@icann.org>> Date: Friday 6 September 2013 19:37 To: "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Action Items arising from the GNSO Council meeting 5 September 2013 Item 5: INPUT & DISCUSSION - Prospective improvements to the Policy Development Process Action Item: * Staff to tabulate the proposed improvements taking into account feedback received during Council meeting for further review and discussion. * Council members requested to encourage their groups to review the proposed improvements and consider which suggestions can be supported and implemented. ________________________________ 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

Description of our "get ready" project proposal -- aimed at getting network administrators prepared for new gTLDs
by Mike O'Connor Sept. 16, 2013

Sept. 16, 2013

hi all, i've built a little page on our web site and have posted our early thinking about the "get ready" project we discussed on our last Outreach call. with your permission, i'll include a link to this page in the reply comments i'm planning to submit tomorrow. for those of you on the call, the only new thing is a more-detailed task list that takes that high level Gantt chart down one level. developing the *next* level down will be up to the project manager (who, as a happily-retired project manager, i'm emphatically stating for the record will **NOT** be me). :-) here's the link to the page http://www.ispcp.info/policy-resources/proposal-a-get-ready-project-for-new… let me know if you have any objections to including this link in our reply comments (due tomorrow). mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

updated policy-statements
by Mike O'Connor Sept. 11, 2013

Sept. 11, 2013

hi all, i've updated the policy-statement page on our website to reflect our support for the recent ICANN Board decision to prohibit "dotless domains" here's the link to the page http://www.ispcp.info/policy-statements/ mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

2 1

Fw: Comments made by the ISPCP constituency
by WUKnoben Sept. 11, 2013

Sept. 11, 2013

FYI Best regards Wolf-Ulrich From: WUKnoben Sent: Wednesday, September 11, 2013 6:18 PM To: input-to-ewg(a)icann.org Cc: Alice Jansen ; Neylon Michele Subject: Comments made by the ISPCP constituency

1 0

REMINDER WITHA AC ROOM Call Information: ISPCP Call / 11 September 2013 at 1300 UTC
by Nathalie Peregrine Sept. 11, 2013

Sept. 11, 2013

Dear All, The next ISPCP call is scheduled on Wednesday 11 September 2013 at 1300 UTC. To check your local time: http://tinyurl.com/nfha6mr Please find the dial-in details below: Participant Passcode: Participant: 3429 # Dial-in numbers: http://www.adigo.com/icann/ ADOBE CONNECT ROOM : https://icann.adobeconnect.com/_a819976787/ispcp/?launcher=false Thank you. Kind regards, Nathalie GNSO Secretariat

1 0

Call Information: ISPCP Call / 11 September 2013 at 1300 UTC
by Nathalie Peregrine Sept. 10, 2013

Sept. 10, 2013

Dear All, The next ISPCP call is scheduled on Wednesday 11 September 2013 at 1300 UTC. To check your local time: http://tinyurl.com/nfha6mr Please find the dial-in details below: Participant Passcode: Participant: 3429 # Dial-in numbers: http://www.adigo.com/icann/ Thank you. Kind regards, Nathalie GNSO Secretariat

1 0

RV: [gnso-igo-ingo] v1.2 Consensus Recommendations
by Novoa, Osvaldo Sept. 10, 2013

Sept. 10, 2013

Dear All, After some long holidays I am back on line. During my absence the Working Group on the protection of International Organizations' names has reach rough consensus on some points that differ from our position submitted some months ago. In general our position was: International Governmental Organizations; IGOs, including the Red Cross (RC) and the Olympic Committee (IOC). * Full protection at the top level, names and acronyms. There are no cases of conflict in the new gTLDs. * Protection of the Full name at the second level, the acronyms are added to the Trademark Clearing House and allowed to participate in the Sunrise period of the new gTLD program. International Non Governmental Organizations: INGOs, excluding RC and the IOC. * No protection at any level. * Allow them to use the Trademark Clearing House. Now the new proposal is to grant protection to the INGOs that figure in the Ecosoc List with General Consultative Status or Special Consultative Status. According to the last list there are 148 organizations with General Consultative Status and 2608 in Special Consultative Status. For organizations with General Consultative Status the proposal is to grant them the same protection as to the IGOs. For organizations with Special Consultative Status the proposal is to grant them protection at the second level for their exact name and acronyms by including them in a list in the Trademark Clearing House. The Working Group proposes to modify the UDRP and URS so that they can be used by the protected organizations. I was a bit surprised that these changes were supported by ALACL and the registries. My position is to support the protections for IGOs, RC and IOC, they have some legal protections and I think ICANN should grant them protection also. Although in principle I am against any kind of differential treatment to any entity. This was also the ISPC position. With regards to the INGOs, I don't see any reason to grant them special protections when the governments of any country haven't done so. But in order to reach a consensus in the group and since an important number of the WG participants support some type of protectio for them, I would go as far as granting protections to those INGOs that have General Consultative Status in the Ecosoc list, it's only 148 as of april of this year. As the ALALC stated in some proposals "We can live with it". I don't support granting protection to the NGOs, not all of them are International, that have Special Consultative Status with Ecosoc, they are too many. If you agree with me I would submit our position. Best regards, Osvaldo [cid:649333913@10092013-288A]Osvaldo Novoa Subgerente General Antel Guatemala 1075, Nivel 22 Montevideo, 11800 Uruguay Tel. +598 2928 6400 Fax. +598 2928 6401 ________________________________ De: owner-gnso-igo-ingo(a)icann.org [mailto:owner-gnso-igo-ingo@icann.org] En nombre de Berry Cobb Enviado el: Jueves, 05 de Septiembre de 2013 01:21 Para: gnso-igo-ingo(a)icann.org Asunto: [gnso-igo-ingo] v1.2 Consensus Recommendations WG Members, Please find attached two copies of the document we are using for the consensus call. One is marked as a clean version and the other is the one containing the track-changes. This version now includes the missing IGO comments and Poncelet's individual responses. It also includes updates to the principles for implementation based on our discussion today. That section does not yet have GCO input. Stay tuned for the levels of consensus document from Thomas. Thank you all again for your participation today, B Berry Cobb Internet Corporation for Assigned Names & Numbers (ICANN) 720.839.5735 mail(a)berrycobb.com<mailto:mail@berrycobb.com> @berrycobb ________________________________ 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