June 2015 - lac-discuss-en - lists.icann.org

Re: [lac-discuss-en] Draft Numbering Services SLA, still open for comment Until 14 June
by asoto＠ibero-americano.org June 8, 2015

June 8, 2015

[[--Translated text (es -> en)--]] Subject: Re: Draft Numbering Services SLA, still open for comment Until 14 June From: asoto(a)ibero-americano.org Dear, here the answer of John Curran, CEO of ARIN, David Conrard. Best regards Alberto Soto ----- Original Message ----- From: ianaxfer-bounces(a)nro.net [mailto: ianaxfer-bounces(a)nro.net] On behalf of John Curran Posted on: Monday, June 8, 2015 8:04 a.m. To: David Conrad CC: ianaxfer(a)nro.net Subject: Re: [NRO-IANAXFER] Draft Numbering Services SLA, still open for comment Until 14 June On June 7, 2015, at 11:51 PM, David Conrad <drc(a)virtualized.org> wrote: > > Hi, > > I have been hesitant to provide comments on the draft SLA due to my current role within ICANN: for those that do not know, I am ICANN's CTO and am responsible for the technical implementation of the transition of the stewardship of the IANA Functions to the global multistakeholder community. However, a number of people (not directly associated with ICANN) have asked me to provide my input WITHOUT my ICANN hat on, and instead as someone who helped set up APNIC, was an ARIN Board member for 5 years, had a very small role in helping to set up AfriNIC, who ran IANA from 2005 to 2010, and who has been doing registry stuff in one way or another for way longer than I care to admit. > > Perhaps this can be a lesson in being careful what you ask for... > > While I can assert the following input is, in fact, (a) purely my own, (b) is in no way representing ICANN's view, and (c) has not been coordinated with ICANN staff or board (I did mention I was planning on posting something in my own name), I am aware some will believe my input is subject to conflict of interest. My apologies in advance if you are among these people. Thanks for These comments - I have no doubt That They will lead to an SLA improved as a result. > I will also apologize in advance if some of the comments below appear a bit harsh. This is not intended, however I believe due to time constraints, it is better to be clear and direct. of the comments (as the community is likely To have ample comments), but but will comment on three areas Which relate to the overall assumptions for the IANA Stewardship transition process at a high-level. > ... > In addition, the "SLA" appears to be entirely one-sided, ignoring the reality that management of numbers is a cooperative effort done by the IANA numbering function operator, the RIRs, LIRs, and end users, for the benefit of the Internet community as a whole. > As such, I believe a useful SLA must clearly define the _mutual_ roles and responsibilities of both parties, along with a very clear escalation path should a party not live up to their responsibilities. The current document does not do this. Does not Necessarily Have to be (or even Should be) in a single document. The rather colorful structure and evolution of ICANN has Resulted in it having multiple roles, and These roles are not yet strictly dependent on each other. For example, if the ICANN Were IANA team to experience extremely and chronic performance issues in the administration of the IANA number registries (the opposite of the excellent performance provided to date), Then There Could be a community Circumstances Where the numbers would need (via the RIRs as Their representative) to an alternative contract for IANA registry operator numbers. The SLA Should be suitable for That arrangement (even though ICANN would not longer be performing the IANA registry numbers function.) However, in my personal opinion, shouldnt Such a change in any way change the RIRs collectively operating under ICANN's overall coordination role Internet identifier; Should the community ie still submit comprehensive policies to ICANN for ratification, the ASO MOU Should Remain in effect, the RIR community Should Participate in accountability and transparency reviews (ATRT) as part of the ICANN system, etc. ICANN Serves Important role as an external to the Internet community That Improves overall numbers accountability and transparency, and Helps in broad outreach to the global Internet community. So, I think we're in agreement That role and Responsibilities Should be Clearly defined, but it is not clear That it Should be done in a single document since there are multiple relationships: 1) RIR / NRO serving as the Global Address Supporting Organization Within ICANN Obligations With its incumbent, and 2) serving as ICANN the IANA numbers for numbering service operator community as Represented by the RIRs. > 5.2: "Notwithstanding the foregoing, the maximum amount the RIRs shall reimburse the Operator pursuant to Article 5.1 above shall be One Hundred Dollars ($100.00) unless otherwise agreed to in writing by all Parties." > > Um, what? So the RIRs are only obligated to pay a maximum of $500 total? This makes no sense to me, particularly given 5.1. I guess this is some sort of legal incantation that makes sense to lawyers. That Makes more sense - ie what do you believe the full costs of providing "the extremely limited activity "of the IANA numbering function? I personally believe That it is in the community's interest for this value be an accurate estimate of Such costs, ICANN ASO and the present contribution Should be reduced by the same amount established eleven o'clock. In This manner, if the worst-cast Were to happen and another HAD party to perform services IANA, the RIRs then a budgeted at Least Would Have to meaningful amount for th purpose, and while ICANN would Lose This amount, it would like Correspond with a reduction in the level of effort in Their IANA team. > 12.1.1: "Operator does hereby assign and transfer any and all right, title and interest in and to such intellectual property rights to the RIRs, their successors, assigns and designees." > > I don't think it makes sense to assign (say) intellectual property held by the Operator on behalf of (say) the naming community exclusively to the RIRs. > > 12.1.2: "Operator does hereby assign and transfer any and all right, title, and interest in and to such data rights to the RIRs, their successors, assigns and designees." > > Similar comment as above. > > 12.3: "the Operator may be provided the use of intellectual property or rights over data through a license from the RIRs or the IETF Trust (the “IP Assets”)." > > This is backwards. ICANN currently owns the rights to that intellectual property. These related to intellectual property activities (including any data rights, trademark, domain names, etc.) Should be held by an entity Which was whos Such set-up for a purpose, Had no operational role, would make available to all Appropriate licenses That parties had a role in IANA operations, etc. Last I checked, the IETF Trust met all of These criteria (Whereas neither ICANN nor the RIRs do) One can imagine some rather extreme worse-case scenarios transitions Involving Where it would be Could it very helpful we all rely on the intellectual property Being made available to whomever needed it to perform the functions, and Not Otherwise caught in transition. Thanks again for the comments! / John Disclaimer: The above remarks are my own as CEO of ARIN. While I believe them to be fully Compatible with the organization's positions on These matters to date, neither the Board nor ARIN ARIN community has Discussed David's comments and developed specific positions on These topics at This Time. _______________________________________________ ianaxfer mailing list ianaxfer(a)nro.net https://www.nro.net/mailman/listinfo/ianaxfer --- Avast antivirus software scanned this email for viruses. https://www.avast.com/antivirus _______________________________________________ lac-discuss-en mailing list lac-discuss-es(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es http://www.lacralo.org [[--Original text (es) http://mm.icann.org/transbot_archive/a9de8ff44a.html --]]

1 0

Re: [lac-discuss-en] ? = Utf-8 OPINION q = C3 = B3n_sobre_futuro_CEO_de_ICANN =
by apisanty＠gmail.com June 8, 2015

June 8, 2015

[[--Translated text (es -> en)--]] Subject: Re:? = Utf-8 OPINION q = C3 = B3n_sobre_futuro_CEO_de_ICANN = From: apisanty(a)gmail.com Alberto, thank you very much. I agree that these issues are important. We can analyze them in a broader context: we agree when I say that the Fadi attention paid to LACRALO ALAC and At Large is disproportionate, and you say missing proposals in our region. The second is of the first consideration. Again and again prior to each ICANN meeting have proposed initiate these proposals and rarely have come sufcicientemente away. The meeting Buenos Aires ICANN is too close to achieve something significant. Let us use it to organize with true accountability accounts between us. Alejandro Pisanty 07/06/2015 23:17 GMT-05: 00 Alberto Soto <asoto(a)ibero-americano.org> : > Gracias Alejandro. Trataremos de hacer esto lo más fácil posible pese a la > complejidad, dado que nunca el Board nos ha pedido opinión. . > > Personalmente puedo afirmar la alta predisposición del actual CEO para con > nosotros. > > - Estoy pidiendo opinión sobre los requisitos del próximo CEO. > Es la primera vez que se hace > > - Los RALOS Chairs estamos participando de reuniones mensuales > de nivel estratégico con el CEO de ICANN y su equipo de colaboradores. Es > la primera vez que se hace. > > - El actual CEO de ICANN realiza reuniones particulares con los > RALOS Chairs y parte de su equipo en las reuniones anuales de ICANN. Es la > primera vez que se hace. En estas reuniones henos realizado varias > observaciones, y todas fueron tenidas en cuenta. En Buenos Aires tendremos > dos reuniones presenciales de este tipo. > > - El actual CEO ha concurrido a distintas reuniones de ALAC y no > solamente a la específica prevista en cada reunión anual de ICANN. También > ha llevado a los distintos responsables de área y hemos podido hablar con > ellos, y hasta entablar discusiones para defender nuestros intereses. Es la > primera vez que se hace. > > > > Quizás sea la personalidad de Fadi, pero necesitamos contar con esta > continuidad, la que aún creo no hemos aprovechado totalmente, por falta de > opiniones de nuestra Región. Por ello, no creo logremos esta transparencia > con el nuevo CEO. > > > > Saludos cordiales > > > > Alberto Soto > > > > > > *De:* Alejandro Pisanty [mailto:apisanty@gmail.com] > *Enviado el:* lunes, 08 de junio de 2015 12:56 a.m. > *Para:* Alberto Soto > *CC:* LACRALO Español; Rinalia Abdul Rahim > *Asunto:* Re: [lac-discuss-es] Opinión sobre futuro CEO de ICANN > > > > Alberto, > > > > mil gracias por esta renovada convocatoria. > > > > Creo que tú y Humberto están en la mejor posición para ayudarnos a enfocar > mejor el esfuerzo. Pienso en esto porque son Uds. quienes mejor pueden > tener acceso a archivos para comparar las expresiones de LACRALO y de At > Large en general en nombramientos anteriores, y su impacto. Una vez que nos > informen eso podremos orientarnos mejor para concentrar el esfuerzo sobre > los puntos en los que hayamos tenido mayor influencia. > > > > Adelanto que pronostico que el resultado indicará que la influencia de los > criterios que se hayan llegado a expresar se detectará como nula, ya que la > designación de los dos más recientes CEOs de ICANN han sido ciudadanos y > residentes de EU, con historia dentro del gobierno (en el caso de Rod > Beckstrom) y en el sector privado (ambos), externos a la organización y sin > prolongado contacto con ésta. Sí en cambio han sido políglotas, > multiculturales y con experiencia de educación y residencia en diversos > países. También hay que hacer notar que han sido desproporcionadamente > atentos con ALAC y At Large y generosos en la aplicación de recursos para > estas organizaciones. Tengámoslo en cuenta. > > > > Alejandro Pisanty > > > > 2015-06-07 21:48 GMT-05:00 Alberto Soto <asoto(a)ibero-americano.org>: > > Estimados, continuando con este importante tema, quiero informarles sobre > los requisitos que fueron considerados en la búsqueda anterior. Es > importante nuestra contribución, y creo que si así lo considera el Board, > es nuestra obligación enviar nuestra opinión. > > Espero vuestros comentarios antes del 20 a las 23:00UTC > > Saludos cordiales > > > > Alberto Soto > > > > > > CEO Perfil [CEO de búsqueda en 2011] > > Se espera de los candidatos para demostrar en el mayor grado posible, la > siguiente experiencia y habilidades. Estos se han agrupado en 4 ítems que > encarnan la naturaleza multifacética de la función: > > Profesional > > § sólido historial de servicio público, o empresarial académica, en un > alto nivel internacional > > § Exposición global: experiencia de trabajo en diferentes países o con > diferentes culturas > > §Experiencia en el manejo flujos de trabajo de procesos y capacidad de > anticipar los problemas > > § Familiaridad con las formas en que la sociedad civil, los intereses del > sector empresarial y las autoridades reguladoras interactúan > > § El éxito en la gestión de la evolución de la ICANN como organización, > cuestiones complejas y programas y contratos clave > > § historial de lograr resultados, no sólo "estar allí" > > § asociación previa con las organizaciones altamente respetadas > > § Liderazgo de equipos internacionales dispersos y múltiples partes > interesadas activas que proporcionan entrada de la política Personal > > § Consenso constructor y catalizador, un motivador y persuasivo > > § Intelectualmente atractivo, contribuye al "liderazgo pensado 'en ayudar > a definir la visión y la estrategia, y aprovecha las competencias de la > organización > > § Combina peso de la personalidad con empatía hacia los demás de > diferentes orígenes > > § Practica en ejercer una influencia en las relaciones no jerárquicas > > § gana respeto y genera confianza en él / ella y la organización > > § Multicultural con conocimientos de idiomas, comunicador practico y > orador público > > § Alinea con los valores de la ICANN: la integridad, la confianza, la > humildad, la excelencia técnica y servicio público > > § negociador capaz, sin hacer enemigos, puede representar la ICANN y puede > representar bien > > § afinidad fuerte con Internet (pero no sólo una "cheerleader"), > consciente de su papel y la complejidad, abraza plenamente la misión de > ICANN y su proceso de abajo hacia arriba > > § encarna y practica el enfoque de múltiples partes interesadas y facilita > la participación de voluntarios > > § conocimiento arquitectura de Internet: la comprensión de los sistemas de > la Internet mundial de identificadores únicos, incluidos los nombres de > dominio, los parámetros del protocolo y direcciones > > § conocimiento institucional: la familiaridad con el funcionamiento de los > registros y registradores, los procedimientos de desarrollo de políticas de > ICANN y categorías de usuarios > > § Comprensión de la estructura del mercado de nombres de dominio y la > dinámica, incluidas las cuestiones de competencia > > § El Ecosistema de la Gobernanza de Internet > > § Instituciones: comprender el entorno de lo implicado en la Internet y > sus sistemas de gobierno administrativos, en particular IETF, ISOC, W3C, y > otros organismos de normalización (ETSI, ITU, ISO, Unicode) > > § La conciencia internacional: conocer los grupos de interés del gobierno > en la gobernanza de Internet y la forma de interactuar con ellos > > § Conocimiento del sistema de las Naciones Unidas y otras organizaciones y > procesos internacionales > > § Capacidad para funcionar y generar confianza con todos los actores a > través de la excelencia operativa y el respeto a la entrada de la base de > múltiples partes interesadas > > > > > > > > *De:* Alberto Soto [mailto:asoto@ibero-americano.org] > *Enviado el:* domingo, 07 de junio de 2015 12:58 a.m. > *Para:* 'LACRALO Español (lac-discuss-es(a)atlarge-lists.icann.org)' > *Asunto:* Opinión sobre futuro CEO de ICANN > > > > Estimados, la Junta de ICANN está interesada en la opinión sobre cuáles > son las características que a nuestra comunidad le gustaría ver en el > futuro CEO de ICANN. > > También habrá una sesión pública con el Consejo sobre el tema de CEO , el > jueves 25 de junio justo antes de que el foro público. > > Sería muy conveniente opinar sobre este tema, y fundamentar tal opinión. > > Creo que es una buena oportunidad de participar y que nuestra voz sea > considerada. > > Estas opiniones deben ser enviadas antes del 20 de junio a las 2300 UTC > por la reunión que tendremos los RALOs Chair con la Junta. > > Muchas gracias y saludos cordiales > > > > Alberto Soto > > > > > ------------------------------ > > <https://www.avast.com/antivirus> > > El software de antivirus Avast ha analizado este correo electrónico en > busca de virus. > *www.avast.com* <https://www.avast.com/antivirus> > > <https://www.avast.com/antivirus> > > > _______________________________________________ > lac-discuss-es mailing list > *lac-discuss-es(a)atlarge-lists.icann.org* > *https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es* > > *http://www.lacralo.org* <https://www.avast.com/antivirus> > > > > <https://www.avast.com/antivirus> > > <https://www.avast.com/antivirus> > > -- <https://www.avast.com/antivirus> > > - - - - - - - - - - - - - - - - - - - - - - - - - - - > Dr. Alejandro Pisanty > Facultad de Química UNAM > Av. Universidad 3000, 04510 Mexico DF Mexico > +52-1-5541444475 FROM ABROAD > +525541444475 DESDE MÉXICO SMS +525541444475 > Blog: *http://pisanty.blogspot.com* > LinkedIn: *http://www.linkedin.com/in/pisanty* > Unete al grupo UNAM en LinkedIn, > *http://www.linkedin.com/e/gis/22285/4A106C0C8614* > Twitter: *http://twitter.com/apisanty* > ---->> Unete a ISOC Mexico, *http://www.isoc.org* > . . . . . . . . . . . . . . . . > <https://www.avast.com/antivirus> > > > ------------------------------ > [image: Avast logo] <https://www.avast.com/antivirus> > > El software de antivirus Avast ha analizado este correo electrónico en > busca de virus. > www.avast.com <https://www.avast.com/antivirus> > > - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty UNAM Faculty of Chemistry 3000 University Avenue,. 04510 Mexico DF Mexico + 52-1-5541444475 FROM ABROAD SMS FROM MEXICO +525541444475 +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty UNAM Join the LinkedIn group, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---- >> Join ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . . [[--Original text (es) http://mm.icann.org/transbot_archive/524588dd75.html --]]

1 0

Re: [lac-discuss-en] Draft Numbering Services SLA, still open for comment Until 14 June
by asoto＠ibero-americano.org June 8, 2015

June 8, 2015

[[--Translated text (es -> en)--]] Subject: Re: Draft Numbering Services SLA, still open for comment Until 14 June From: asoto(a)ibero-americano.org Dear, I forward this mail as too interesting for the criticisms of the work done so far on transition IANA, and concerns us. While it's long, reading is important. When you have answer, I will send them. Best regards Alberto Soto ----- Original Message ----- From: ianaxfer-bounces(a)nro.net [mailto: ianaxfer-bounces(a)nro.net] On behalf of David Conrad Posted on: Monday, June 8, 2015 12:52 am To: Axel Pawlik CC: ianaxfer(a)nro.net Subject: Re: [NRO-IANAXFER] Draft Numbering Services SLA, still open for comment Until 14 June Hi, I Have Been hesitant to Provide comments on the draft SLA due to my current role Within ICANN: For Those That do not know, I am ICANN's CTO and am responsible for the technical implementation of the transition of the stewardship of the IANA Functions to the overall multistakeholder community. However, a number of people (not Directly Associated With ICANN) Have Asked to Provide me my input WITHOUT ICANN my hat on, and as someone WHO Instead Helped set-up APNIC, was an ARIN Board member for 5 years, had a very small role in helping to set-up AfriNIC, WHO IANA ran from 2005 to 2010, and WHO has-been doing stuff registry in one way or another for way longer than I care to admit. Perhaps esta can be a lesson in Being careful what you ask for ... While I can assert the following input is, in fact, (a) purely my own, (b) is in no way Representing ICANN's view, and (c) you have not Been Coordinated With ICANN staff or board (I did mention I was planning on posting something in my own name), I am aware some will believe my input is subject to conflict of interest. My apologies in advance if you are Among These people. Also I will apologize in advance if some of the comments below Appear a bit harsh. Intended This is not, however I believe due to time constraints, it is better to be clear and direct. Finally, I apologize for the length of esta message. I partially blame the length on the length of the SLA Which is quite stunning what the IANA Given the whos function does and numbering (as Indicated by the blog by Alain Durand at https://www.icann.org/news/blog/iana-functions-usage-analysis) So, With the above caveats: At a high level, I will admit to very high degree of confusion about the draft document as written SLA. It does not seem like an SLA to me. In my experience, When one is writing up service level agreements, the first step is to Clearly Identify the services to an agreement Which is Being defined. You then figure out acceptable levels of services, preferably by the folks whos Who are Involved in making use of the services in question, and Once You Have An Idea of \u200b\u200bthe services and the services Those levels at Which Should be provided, you then Clearly defined the Roles and Responsibilities of Both parties.Only after all of this is done do you bring in the lawyers (IF NECESSARY) to write stuff down into a binding agreement. Should SLAs minimize the technical and legal jargon, Instead, focus on clarity and simplicity. This does not Appear to Have Been the path taken in drawing up the draft SLA. Instead, it Appears the drafting team, aka "the RIR legal team (a group of staff counsels and advisors from the five RIRs)" Took the IANA Functions contract, and hacked it up. I feel this is VERY odd since I believe the contract is IANA Functions Primarily interested in Ensuring DNS root zone management is Done with minimal hiccups (with contractual language put in place to root zone management Ensure past hiccups did not reoccur) - the IANA Functions Contract management's treatment of numbers (like management protocol parameter) is Largely Mentioned only (IMHO) to Ensure oversight of Those functions are bound by NTIA to ICANN. That is, I believe the drafting team Largely Took an existing but non-applicable _contract_, applied cosmetic Largely Changes, and then a Declared That a "Service Level Agreement". Esta I believe to be a mistake. In Addition, the "SLA" appears to be entirely one-sided, ignoring the reality That management of numbers is a cooperative effort done by the operator numbering IANA function, the RIRs, LIRs, and end users, for the benefit of the Internet community as a whole. As such, I believe to useful SLA must _mutual_ Clearly define the roles and Responsibilities of Both parties, along with a very clear escalation path Should a party not live up to Their Responsibilities. The current document does not Do This. Finally, much of the document, Perhaps as a result of Its origin, feels much more like a contract for services or MoU As opposed to a service agreement _level_. Perhaps the issue here is just my interpretation of what an SLA is and what "the RIR legal team" whos was after was a service contract. If that's so, I'd Suggest not terming it a "service level agreement". Specific comments: Article 1: As I am not a lawyer, I can not usefully comment on the one and a half pages of definitions and interpretations.I also do not feel comfortable trying to figure out all the Implications of Those definitions and interpretations As They apply to SLAs, so I'm just going to ignore them and try to focus on the rest of the document as a definition of acceptable service levels . Article 2: 2.1: "The Operator is required to perform the IANA Numbering Services in a stable and secure manner and in Accordance With the RIR Global Policies." What does "stable and secure" In This context mean? Also, as written, it can be read as this is defined in RIR overall policies, Which of course it is not. 2.1: "The IANA Numbering Services are administrative and technical in nature." So what? Do not see the point of esta sentence in an SLA. 2.1: "The Operator is required to coordinate IANA With operators of other services." Who are these "operators" and what do they do?I assume this is Intended to Deal with the case Where the numbering function is split off from the other IANA functions, but It Might be useful to state Explicitly That, since reading is another potential That there are multiple providers of the numbering function. Article 3: Not being a lawyer, I do not understand the usage of "severally" in 3.1 and 3.2. Also I'm a bit surprised That a liability Assumed by (say) ARIN, presumably Including legal liabilities since it is not constrained, would apply to (say) RIPE, but I suspect due to lack of legal training, I'm simply misunderstanding what is meant. Article 4: 4.1: "The Operator Shall be responsible for Allocated and unallocated IPv4 and IPv6 address space and Autonomous System Number (ASN) space based on established guidelines and RIR Global Policies." IPv4 unallocated address space? What are "established guidelines"? In a service level agreement, I believe it is Very Important to Have concise and concrete terms, not vague handwaves. 4.1. "The Operator Shall distribute IP address blocks to RIRs for routine distribution Typically downstream through Internet providers to end-users Within the regions served by Those registries The Operator Shall Also reserve and direct allocation of space for special purposes, Such as multicast addressing , addresses for private networks as described in RFC-1918 Address Allocation for Private Internets, and specified applications globally. " No mention of distributing AS numbers. Should probably say "... Shall distribute Internet numbering resources ...". 4.2.1: "The RIR will submit an initial request for Internet Number Resources to the Operator by electronic mail (e-mail)." I do not think it is a good idea to permanently embed to using email to handle requests. It precludes the Operator pointlessly from innovation and deploying more user friendly technologies. 4.2.1.b: "The Operator Shall acknowledge receipt of the initial request Within two (2) business days by return e-mail." Again, forcing the use of email Seems a bad idea to In This Day and Age. 4.2.1.c.ii: "send a detailed announcement to the Requesting RIR as well as a simultaneous announcement to the RIRs, informing them of the provisioning of resources" Nit: Should probably send the simultaneous announcement to "the other RIRs" to avoid the redundant announcement to the Requesting RIR. 4.2.1.c.iii: "Appropriate make Modifications to the pages of the Operator's website ..." This should probably say "make Modifications to the Appropriate Registry Number IANA or Registries" 4.2.1.c.iii: "Such announcements Which Shall be limited to Which IP address or AS number ranges Have Been issued, the time of issuance and the Registry to Which They Have Been issued" I do not see the reason for esta limitation. What is this trying to stop? 4.2.1.c.iv "ITS Upon receipt of the allocation, the RIR Requesting That Shall notify administrator of the name servers to be inserted into the name server resource records of That domain." And what happens if the RIR does not? This is an example of why I believe SLAs need to define mutual roles and Responsibilities. Article 5: 5.2: "Notwithstanding the foregoing, the maximum amount the RIRs Shall reimburse the Operator Pursuant to Article 5.1 above Shall Be One Hundred Dollars ($ 100.00) unless otherwise Agreed to in writing by all Parties." Um, what? So the RIRs are only obligated to pay a maximum of $ 500 altogether? This makes no sense to me, Particularly Given 5.1. I guess this is some sort of legal incantation That Makes Sense to lawyers. Article 6: 6.1: "Additionally, Within a month of the adoption ..." Probably Should state 30 days or 4 weeks or something else non-ambiguous. 6.1: "the Operator, as guided by the RIRs, Shall document the procedures ACCORDING TO RIR Global Policy esta Which would be Implemented and publish it on the Operator's website." I do not think the RIRs Should Have the unilateral Ability to define the process by Which the Operator updates STI website. 6.2: "... Shall Be Obliged to issue yearly reports illustrating ITS compliance With the Obligations Described in Articles 4 and 6.1" Probably need a bit of detail in What They expect to Contain este informe, eg, the Operator simply writing a report That says "we did stuff" is probably Insufficient. Article 7: As a preamble, I think the amount of work defined In this section Makes the maximum $ 100 / RIR absolutely ludicrous. It strikes me as incredibly odd That the work performing the actual function is vastly outweighed by the work Necessary to monitor the function. 7.1.1: "The Operator Shall Implement a system for secure authenticated communications Between it and Its customers When carrying out all IANA Numbering Services requirements." This is why I feel it is Inappropriate To have based the Service Level Agreement for the IANA Function Numbering function on the IANA contract. That sentence Makes Sense for the Root Zone Management System and Dealing with Hundreds of TLD That Administrators connect via HTTPS, it does not make sense here. Above, the SLA has required requests to be Submitted By email: There is no "system for secure authenticated communications" for the Currently numbering function. We authenticate above the communications system. 7.1.5: "The Operator Shall notify and consult in advance the RIRs When there are million other Changes in personnel." Notification is fine, however it Should be clear esta That does not imply approval. 7.1.5: "The Director of Security Shall Be one of the key personnel Assigned to this contract." Cut-and-paste error: this is not a contract. 7.2.2: "... starting no later than six (6) months after date of contract award." Cut-and-paste error: this is not a contract and it is not Awarded. 7.2.3: "No later than 30 days after conducting the survey, the CSS Operator Shall submit the Report to the RIRs." Should it be made public, so This should probably say "... CSS submit the Report to the RIRs and publish Appropriately Operator on the website" or some such. 7.2.5: "Prior to publication / posting of reports, the Operator Shall Obtain approval from the RIRs." This violates ICANN's (and the RIRs) requirements to be open and transparent.If This was not a copy / paste from the IANA Functions contract, I'd be extremely worried about this clause. 7.3.3: "Prior to publication / posting of reports, the Operator Shall Obtain approval from the RIRs." Same comment as 7.2.5. Article 8: 8.2: "The RIRs May perform a review Whenever They deem Appropriate." This needs to be constrained. I do not think it reasonable to allow the RIRs to 'perform a review' at (say) 2 a.m. on January 1. There Should be some sort of notice and reasonable accommodation made for schedules, workload, etc. 8.3: "The Operator must Comply with the request by providing the information Requested Within working days." The number of working days Might be helpful. 8.4: "The RIRs May perform reviews in Consultation with third parties." And What happens when the RIRs demand the use of (say) the Russian Business Network, the Yakuza, or worse, the US Congress, as a third party? Who is the third party must be constrained somehow. "Mutual agreement" should suffice. Article 9: I believe would be an escalation process Appropriate here. Article 10: 10.1: "the term of Agreement esta Shall continue for five (5) years after the Commencement Date." I do not see the point in having a term Given the agreement can be terminated at any time by any party. 10.2, 10.3: Separability. I believe These SLAs need to be mutual - if the RIRs choose not to renew or terminate, They first need to document how the replacement Operator can Assure At least the same level of accountability, openness, transparency, security, stability, resilience, etc. , as the Existing Operator. Article 11: 11.1: "The Operator Shall prepare plan for th purpose esta plan and submit to the RIRs (18) months after the date of esta Agreement." What happens if the RIRs choose to terminate six months after the date of the agreement? 11.1: "The Operator Shall Provide sufficient experienced personnel During the phase-in, phase-out period to Ensure That the IANA Numbering Services are maintained at the required level of proficiency." This Seems pointless. In the event of a termination, what if the Operator does not? Are the RIRs going to doubly terminate them? 11.2: "Transition to Successor Operator" Same question as above. 11.2.3: "The Operator Shall disclose Also Necessary personnel records and allow the successor to conduct on-site interviews With These employees." Would not this violate the privacy of Those employees and privacy protection laws? Article 12: 12.1.1: "Operator does hereby assign and transfer any and all right, title and interest in and to Such intellectual property rights to the RIRs, Their successors, ASSIGNS and designees." I do not think it Makes Sense to assign (say) intellectual property held by the Operator on Behalf of (say) the naming community Exclusively to the RIRs. 12.1.2: "Operator does hereby assign and transfer any and all right, title, and interest in and to Such data rights to the RIRs, Their successors, ASSIGNS and designees." Similar comment as above. 12.3: "May be the Operator provided the use of intellectual property rights over data or through a license from the RIRs or the IETF Trust (the" IP Assets ")." This is backwards. Currently ICANN That owns the rights to intellectual property. Articles 13-15: Did not read. Do not have the background to determine if legal incantations Those are reasonable. If you've read this far, I'm impressed at your intestinal fortitude ... Regards, -drc (SPEAKING ONLY FOR MYSELF) --- Avast antivirus software scanned this email for viruses. https://www.avast.com/antivirus [[--Original text (es) http://mm.icann.org/transbot_archive/99e41ce1b2.html --]]

1 0

Re: [lac-discuss-en] ? = Utf-8 OPINION q = C3 = B3n_sobre_futuro_CEO_de_ICANN =
by asoto＠ibero-americano.org June 8, 2015

June 8, 2015

[[--Translated text (es -> en)--]] Subject: Re:? = Utf-8 OPINION q = C3 = B3n_sobre_futuro_CEO_de_ICANN = From: asoto(a)ibero-americano.org Thanks Alexander. We try to make this as easy as possible despite the complexity, ever since the Board has asked opinion. . I can personally say high bias current CEO for us. - I'm asking opinion on the requirements of the next CEO. It is the first time you do - The Chairs are participating RALOS monthly strategic level meetings with ICANN CEO and his team. It is the first time it is done. - The current CEO of ICANN makes private meetings with RALOS Chairs and part of his team in the annual meetings of ICANN. It is the first time it is done. At these meetings hay made several observations, and all were considered. In Buenos Aires we have two face meetings of this type. - The current CEO has attended various meetings of ALAC and not only the specific provided at each annual meeting of ICANN. It has also led to various area managers and we could talk to them, and to engage in discussions to defend our interests. It is the first time it is done. Perhaps Fadi personality, but we need to have this continuity, I still have not fully exploited due to lack of opinions in our region. Therefore, I do not think we achieve this transparency with the new CEO. Best regards Alberto Soto From: Alejandro Pisanty [mailto: apisanty(a)gmail.com] Posted on: Monday, June 8, 2015 12:56 am To: Alberto Soto CC: LACRALO Spanish; Abdul Rahim Rinalia Subject: Re: [lac-discuss-en] Comments about future CEO of ICANN Alberto, thank you for this renewed call. I think you and Humberto are in the best position to help us better focus the effort. I think of this as you are. Who can best access files to compare the expressions of LACRALO and At Large generally above appointments and their impact. Once you inform us that we orient ourselves better to concentrate efforts on the points where we have had more influence. Advancement to predict that the result will indicate that the influence of the criteria that have come to be expressed is detected as invalid, since the appointment of the two most recent CEOs of ICANN are EU citizens and residents with a history within the government ( in the case of Rod Beckstrom) and in the private sector (both), external to the organization without prolonged contact with it. If you have been multilingual, multicultural and experienced education and residence in several countries.Also it should be noted that they have been disproportionately attentive to ALAC and At Large and generous in the allocation of resources to these organizations. Let's keep in mind. Alejandro Pisanty 07/06/2015 21:48 GMT-05: 00 Alberto Soto <asoto(a)ibero-americano.org <mailto:asoto@ibero-americano.org> >: Dear, continuing with this important issue, I want to inform you about the requirements that were considered in the previous search. Our contribution is important, and I think if the Board considers it is our duty to send our opinion. I hope your comments before 20th at 23: 00UTC Best regards Alberto Soto CEO Profile [CEO search in 2011] It is expected the candidates to demonstrate the extent possible, the following experience and skills.These have been grouped into four items that embody the multifaceted nature of the function: Professional § strong record of public service, academic or business at a high international level § Global Exposure: experience working in different countries or cultures §Experiencia in managing work flow processes and ability to anticipate problems § Familiarity with the ways in which civil society, the interests of business and regulators interact § The success in managing the evolution of ICANN as an organization, complex issues and key programs and contracts § record of achieving results, not just "being there" § previous association with highly respected organizations § Leadership scattered multiple active international teams and stakeholders providing input Politics § consensus builder and catalyst, motivator and persuasive § intellectually attractive, contributes to the "thought leadership" in helping to define the vision and strategy, and leverages the powers of the organization § weight combines personality with empathy toward others of different backgrounds § Practice in influence in non-hierarchical relationships § earn respect and builds trust in him / her and organization § Multicultural with language skills, practical communicator and public speaker § aligns with ICANN values: integrity, trust, humility, technical excellence and public service § negotiator capable, without making enemies, may represent ICANN and may represent either § strong affinity with the Internet (but not just a "cheerleader"), aware of its role and complexity, fully embraces the mission of ICANN and its bottom-up process § embodies and practices of multi-stakeholder approach and facilitates the participation of volunteers § knowledge of Internet architecture: the understanding of the global Internet systems of unique identifiers, including domain names, protocol parameters and addresses § institutional knowledge: familiarity with the operation of registries and registrars, procedures ICANN policy development and categories of users § Understanding market structure of domain names and dynamics, including competition issues § The Ecosystem Internet Governance § Institutions: understanding the environment as implied in the Internet and government administrative systems, in particular IETF, ISOC, W3C and other standards bodies (ETSI, ITU, ISO, Unicode) International awareness § meet the stakeholders of government in Internet governance and the way you interact with them § Knowledge of the United Nations system and other international organizations and processes § Ability to work and build trust with all stakeholders through operational excellence and respect for the entrance to the base of multi-stakeholder From: Alberto Soto [mailto: asoto(a)ibero-americano.org <mailto:asoto@ibero-americano.org> ] Posted on: Sunday, June 7, 2015 12:58 am For: 'LACRALO Spanish (lac-discuss-es(a)atlarge-lists.icann.org <mailto:lac-discuss-es@atlarge-lists.icann.org> ) ' Subject: Opinion on the future CEO of ICANN Dear, the ICANN Board is interested in opinion on what are the features that our community would like to see in the future CEO of ICANN. There will be a public meeting with the Council on the issue of CEO on Thursday June 25 just before the public forum. It is highly desirable to review this issue and substantiate this view. I think it's a good opportunity to participate and that our voice is considered. These opinions should be sent before June 20 at 2300 UTC by the meeting we will have the RALOs with the Board Chair. Thank you very much and best regards Alberto Soto _____ < https://www.avast.com/antivirus> < https://www.avast.com/antivirus> www.avast.com < https://www.avast.com/antivirus> < https://www.avast.com/antivirus> _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/df98a79397.html --]]

1 0

Re: [lac-discuss-en] ? = Utf-8 OPINION q = C3 = B3n_sobre_futuro_CEO_de_ICANN =
by apisanty＠gmail.com June 8, 2015

June 8, 2015

[[--Translated text (es -> en)--]] Subject: Re:? = Utf-8 OPINION q = C3 = B3n_sobre_futuro_CEO_de_ICANN = From: apisanty(a)gmail.com Alberto, thank you for this renewed call. I think you and Humberto are in the best position to help us focus best effort. I think of this as you are. Who can best access files to compare and expressions of LACRALO At Large general in previous appointments, and their impact. Once we report that can guide us better to concentrate efforts on the points where we have had more influence. Advancement to predict that the result will indicate that the influence of the criteria have come to be expressed is detected as invalid, since the designation of the two most recent CEOs have been citizens of ICANN and US residents with a history within the government (in the case of Rod Beckstrom) and in the private sector (both), external to the organization without Prolonged contact therewith. If you have been polyglot, multicultural education and experience and residence in various countries. Also it should be noted that they have been disproportionately attentive to ALAC and At Large and generous in applying resources these organizations. Let's keep in mind. Alejandro Pisanty 07/06/2015 21:48 GMT-05: 00 Alberto Soto <asoto(a)ibero-americano.org> : > Estimados, continuando con este importante tema, quiero informarles sobre > los requisitos que fueron considerados en la búsqueda anterior. Es > importante nuestra contribución, y creo que si así lo considera el Board, > es nuestra obligación enviar nuestra opinión. > > Espero vuestros comentarios antes del 20 a las 23:00UTC > > Saludos cordiales > > > > Alberto Soto > > > > > > CEO Perfil [CEO de búsqueda en 2011] > > Se espera de los candidatos para demostrar en el mayor grado posible, la > siguiente experiencia y habilidades. Estos se han agrupado en 4 ítems que > encarnan la naturaleza multifacética de la función: > > Profesional > > § sólido historial de servicio público, o empresarial académica, en un > alto nivel internacional > > § Exposición global: experiencia de trabajo en diferentes países o con > diferentes culturas > > §Experiencia en el manejo flujos de trabajo de procesos y capacidad de > anticipar los problemas > > § Familiaridad con las formas en que la sociedad civil, los intereses del > sector empresarial y las autoridades reguladoras interactúan > > § El éxito en la gestión de la evolución de la ICANN como organización, > cuestiones complejas y programas y contratos clave > > § historial de lograr resultados, no sólo "estar allí" > > § asociación previa con las organizaciones altamente respetadas > > § Liderazgo de equipos internacionales dispersos y múltiples partes > interesadas activas que proporcionan entrada de la política Personal > > § Consenso constructor y catalizador, un motivador y persuasivo > > § Intelectualmente atractivo, contribuye al "liderazgo pensado 'en ayudar > a definir la visión y la estrategia, y aprovecha las competencias de la > organización > > § Combina peso de la personalidad con empatía hacia los demás de > diferentes orígenes > > § Practica en ejercer una influencia en las relaciones no jerárquicas > > § gana respeto y genera confianza en él / ella y la organización > > § Multicultural con conocimientos de idiomas, comunicador practico y > orador público > > § Alinea con los valores de la ICANN: la integridad, la confianza, la > humildad, la excelencia técnica y servicio público > > § negociador capaz, sin hacer enemigos, puede representar la ICANN y puede > representar bien > > § afinidad fuerte con Internet (pero no sólo una "cheerleader"), > consciente de su papel y la complejidad, abraza plenamente la misión de > ICANN y su proceso de abajo hacia arriba > > § encarna y practica el enfoque de múltiples partes interesadas y facilita > la participación de voluntarios > > § conocimiento arquitectura de Internet: la comprensión de los sistemas de > la Internet mundial de identificadores únicos, incluidos los nombres de > dominio, los parámetros del protocolo y direcciones > > § conocimiento institucional: la familiaridad con el funcionamiento de los > registros y registradores, los procedimientos de desarrollo de políticas de > ICANN y categorías de usuarios > > § Comprensión de la estructura del mercado de nombres de dominio y la > dinámica, incluidas las cuestiones de competencia > > § El Ecosistema de la Gobernanza de Internet > > § Instituciones: comprender el entorno de lo implicado en la Internet y > sus sistemas de gobierno administrativos, en particular IETF, ISOC, W3C, y > otros organismos de normalización (ETSI, ITU, ISO, Unicode) > > § La conciencia internacional: conocer los grupos de interés del gobierno > en la gobernanza de Internet y la forma de interactuar con ellos > > § Conocimiento del sistema de las Naciones Unidas y otras organizaciones y > procesos internacionales > > § Capacidad para funcionar y generar confianza con todos los actores a > través de la excelencia operativa y el respeto a la entrada de la base de > múltiples partes interesadas > > > > > > > > *De:* Alberto Soto [mailto:asoto@ibero-americano.org] > *Enviado el:* domingo, 07 de junio de 2015 12:58 a.m. > *Para:* 'LACRALO Español (lac-discuss-es(a)atlarge-lists.icann.org)' > *Asunto:* Opinión sobre futuro CEO de ICANN > > > > Estimados, la Junta de ICANN está interesada en la opinión sobre cuáles > son las características que a nuestra comunidad le gustaría ver en el > futuro CEO de ICANN. > > También habrá una sesión pública con el Consejo sobre el tema de CEO , el > jueves 25 de junio justo antes de que el foro público. > > Sería muy conveniente opinar sobre este tema, y fundamentar tal opinión. > > Creo que es una buena oportunidad de participar y que nuestra voz sea > considerada. > > Estas opiniones deben ser enviadas antes del 20 de junio a las 2300 UTC > por la reunión que tendremos los RALOs Chair con la Junta. > > Muchas gracias y saludos cordiales > > > > Alberto Soto > > > > > ------------------------------ > [image: Avast logo] <https://www.avast.com/antivirus> > > El software de antivirus Avast ha analizado este correo electrónico en > busca de virus. > www.avast.com <https://www.avast.com/antivirus> > > > _______________________________________________ > lac-discuss-es mailing list > lac-discuss-es(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > http://www.lacralo.org > - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty UNAM Faculty of Chemistry Av.University 3000, 04510 Mexico DF Mexico + 52-1-5541444475 FROM ABROAD SMS FROM MEXICO +525541444475 +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty UNAM Join the LinkedIn group, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---- >> Join ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . . [[--Original text (es) http://mm.icann.org/transbot_archive/e075235ebf.html --]]

1 0

Welcome to At-Large!
by staff＠atlarge.icann.org June 8, 2015

June 8, 2015

Dear Mario and Carlos, ICANN's At-Large Advisory Committee (ALAC) is pleased to inform you that (224) IEEE Nicaragua has been certified as an At-Large Structure (ALS). The ALAC greatly appreciates your group's interest in involving individual users in ICANN and looks forward to working with you and your colleagues. The purpose of ALS certification is to recognize that your organization meets the necessary criteria to involve individual Internet users at the local or issue level in ICANN activities, and that your organization will support its individual members' informed participation in ICANN efforts that affect end-users. The ALAC is eager to promote a productive working relationship between your organization, other ALS, and the ALAC (and ICANN in general), and your input on how we can make this a success would be greatly appreciated. We would like to offer some initial tools to help your organization keep its members informed (about significant news from ICANN and information on ICANN policy-development efforts) and engaged in activities of interest: - Point of Contact for your Organisation: Please send an email to mailto:staff@atlarge.icann.org identifying the names and email addresses of one or two individuals who will be the point of contact for information and correspondence regarding ICANN At-Large. If this changes, please let us know. - At Large Mailing Lists. There are many At Large email lists, for each region; you can sign up for them and manage your subscriptions at: http://atlarge-lists.icann.org/mailman/listinfo . The points of contact you identify will automatically be added to your region's list just for accredited ALSes to discuss regional issues and to the mailing list for Staff announcements (only Staff can post messages to that list); you are invited to join others as you wish. - ALS information. Information about your organization will be shared with the At-Large community to enable individuals interested in your group's activities to contact you, and to encourage cooperation with other groups interested in ICANN activities in your geographic region. Please complete and email the form at the bottom of this note to staff(a)atlarge.icann.org. - ALAC website. The ALAC website (http://www.atlarge.icann.org <http://www.atlarge.icann.org/> ) is a good source for ICANN news and information of interest to individual Internet users. We encourage you to provide your members with a link. The ALAC relies on volunteers to translate information into multiple languages. Translations of documents on the website are welcome and should be sent to <mailto:staff@atlarge.icann.org> - At-Large Regional Websites. Regional wiki webpages also have been created to distribute information (including in local languages) on activities, events and issues of particular interest to people in each region. These are maintained by the community. They are: African Region: http://www.afralo.org Asia/Australia/Pacific Region: http://www.apralo.org <http://www.apralo.org/> European Region: http://www.euralo.org <http://www.euralo.org/> Latin America/Caribbean Region: http://www.lacralo.org <http://www.lacralo.org/> North American Region: http://www.naralo.org <http://www.naralo.org/> We have included an Starter Kit that includes key information on ALAC and At-Large communication tools. We have also included the ALS Beginners Guide which explains how best to engage within At-Large. We look forward to working with you and your organization's members to advance individual Internet users' interests within ICANN. If you have any questions, or need additional information, please contact us at staff(a)atlarge.icann.org. Sincerely, The At-Large Advisory Committee http://www.atlarge.icann.org <http://www.atlarge.icann.org/> staff(a)atlarge.icann.org --------------------------- Name: Location (city/country/region; whatever is relevant to your membership): Mission: Member benefits: Contacts (name/s and email address/es -- title/s optional): Website: Other (additional informational you would like included):

4 3

Re: [lac-discuss-en] ??? Q = iso-8859-1 F3n_sobre_futuro_CEO_de_ICA VIEW = = = iso-8859-1 q NN =?????
by asoto＠ibero-americano.org June 8, 2015

June 8, 2015

[[--Translated text (es -> en)--]] Subject: Re:??? Q = iso-8859-1 F3n_sobre_futuro_CEO_de_ICA VIEW = = = iso-8859-1 q NN =????? From: asoto(a)ibero-americano.org Dear, continuing with this important issue, I want to inform requirements that were considered in the previous search. It is important our contribution, and I believe that if the Board considers aslo is our obligation to send our opinion. I hope your comments before 20th at 23: 00UTC Best regards Alberto Soto CEO Profile [CEO search in 2011] It is expected the candidates to demonstrate to the greatest possible extent, following experience and skills. These have been grouped into four items which multifactica embody the nature of the function: Professional Slido history of public service, academic or business on a high worldwide Global exposure: experience working in different countries or different cultures Experience in managing work flow processes and capacity anticipate problems Familiarity with the ways in which civil society interests business sector and regulators interact The success in managing the evolution of ICANN as an organization, complex issues and key programs and contracts record of achieving results, not only "be there" prior association with highly respected organizations Ymltiples leadership of international teams scattered parts Active interested providing policy input Personal Consensus builder and catalyst, a motivator and persuasive Intellectually appealing, it contributes to the "thought leadership" in helping define the vision and strategy, and leverages the powers of the organization Combined weight of personality and empathy for the others of different origins Practice in influence in non jerrquicas relations earn respect and builds trust in l / she and the organization Multicultural with language skills, practical communicator and speaker public Aligns with ICANN values: integrity, trust, humility, technical excellence and public service negotiator capable, without making enemies, may represent ICANN and can represent well strong affinity with the Internet (but not just a "cheerleader"), conscious its role and complexity, fully embraces the mission of ICANN and bottom-up process embodies the approach and practice multiple stakeholders and facilitates the participation of volunteers Internet architecture knowledge: the understanding systems the global Internet mechanics identifiers, including names domain, the protocol parameters and addresses institutional knowledge: familiarity with the operation of the registries and registrars, procedures of development policies ICANN and categories of users Understanding of the market structure of domain names and dynamics, including competition issues The Ecosystem Internet Governance Institutions: understanding the environment as implied in the Internet and government administrative systems, in particular IETF, ISOC, W3C, and other normalization bodies (ETSI, ITU, ISO, Unicode) International awareness meet interest groups in government Internet governance and the way you interact with them Knowledge of the United Nations system and other organizations and international processes Ability to function and build trust with all actors through operational excellence and respect for the entrance of the base multiple stakeholders From: Alberto Soto [mailto: asoto(a)ibero-americano.org] Posted on: Sunday, June 7, 2015 12:58 am For: 'LACRALO Spanish (lac-discuss-es(a)atlarge-lists.icann.org)' Subject: Opinin on future CEO of ICANN Dear, the ICANN Board estinteresada in the opinion on what are the features that our community would like to see in the future CEO ICANN. Habruna sesinpblica also with the Council on the issue of CEO, Thursday, June 25 just before the public forum. It is more appropriate to review this issue and support of that opinion. I think it's a good opportunity to participate and that our voice considered. These opinions should be sent before June 20 at 2300 UTC by the meeting we will have the RALOs with the Board Chair. Thank you very much and best regards Alberto Soto --- Avast antivirus software has analyzed this e-mail for viruses. https://www.avast.com/antivirus [[--Original text (es) http://mm.icann.org/transbot_archive/1318e2489d.html --]]

1 0

RES: Welcome to-At Large!
by sylvia＠internautabrasil.org June 7, 2015

June 7, 2015

[[--Translated text (es -> en)--]] Subject: RES: Welcome to-At Large! From: sylvia(a)internautabrasil.org +1 Regards Sylvia ___________________________________________________ Sylvia Leite Herlein <mailto:sylvia@internautabrasil.org> sylvia(a)internautabrasil.org ALAC-LACRALO Delegate to NomComm 2014-2015 One World, One Internet cid: 26A2D0D9-E7A9-455D-BCDC-26757E8E3078 2009-2015 Secretary FLUI ex - Secretary LACRALO-ICANN / 2012-2014 - ex - ALAC Member 2009-2011 - <http://atlarge.icann.org/> http://atlarge.icann.org Skype: sylvia_leite Assinatura_Sylvia_Internautabrasil From: lac-discuss-es-bounces(a)atlarge-lists.icann.org [mailto: lac-discuss-es-bounces(a)atlarge-lists.icann.org] Em nome Vanda Scartezini Posted in: Sunday, June 7, 2015 13:37 To: Alejandro Pisanty; Fatima Cambronero Cc: LACRALO Spanish Assunto: Re: [lac-discuss-en] Welcome to-At Large! First of all it is necessary to engage in new concepts and structure of ICANN, for only after understanding the key points being discussed as the transition from the supervision of IANA and issues of providing slopes to the community. We also need to understand the current new stage with 635 new TLDs to the end of May. And what this means. In Nicaragua they may even have the opportunity to participate in a presentation of these points. Hugs Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, 1004 cj 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos. From: Alejandro Pisanty <apisanty(a)gmail.com> Date: Thursday, June 4, 2015 at 0:48 To: Fatima Cambronero <fatimacambronero(a)gmail.com> Cc: "lac-discuss-es(a)atlarge-lists.icann.org" <lac-discuss-es(a)atlarge-lists.icann.org> Subject: Re: [lac-discuss-en] Welcome to-At Large! +1 What are the substantive issues and discussions on ICANN policy development with which we show the IEEE colleagues Nicaragua to illustrate how the things he says Diego made? Alejandro Pisanty On Wed, June 3, 2015 at 6:10 PM, Fatima Cambronero <fatimacambronero(a)gmail.com> wrote: Diego, all / os, In my case, I would not dare to ask a newcomer, something I am not sure you are contributing as "Contributions and pro-active management of Internet Users are recommended" in a given country or region. Perhaps with this new ALS is incorporated, we serve those who are already involved, to make an introspection and review what we are providing each of us. Mario and colleagues IEEE Nicaragua, are welcome and am available to colaborarles in this new process. Best regards, Fatima Cambronero 06/03/2015 18:00 GMT-05: 00 <dacostabastidas(a)dtech.ec> : [[Translated text (en -> en) -]] Subject: Re: Welcome to-At Large! From: dacostabastidas(a)dtech.ec Welcome !, HOPE Contributions and pro-active management of Users are recommended Internet in Nicaragua and the region. Atte Diego Acosta Bastidas 06/03/2015 16:30 GMT-05: 00 <hcarrascob(a)gmail.com> : > > [[--Translated text (en -> es)--]] > > Asunto: Re: Bienvenidos a-At Large! > Desde: hcarrascob(a)gmail.com > > Bienvenidos a Lacralo !!! > > > > > Saludos > > > Enviado desde mi iPhone > > > > El 03-06-2015, a las 20:31, "staff(a)atlarge.icann.org" < > staff(a)atlarge.icann.org> escribiÃ³: > > > > Dear Mario and Carlos, > > > > ICANN's At-Large Advisory Committee (ALAC) is pleased to inform you that > > (224) IEEE Nicaragua has been certified as an At-Large Structure (ALS). > The > > ALAC greatly appreciates your group's interest in involving individual > users > > in ICANN and looks forward to working with you and your colleagues. > > > > The purpose of ALS certification is to recognize that your organization > > meets the necessary criteria to involve individual Internet users at the > > local or issue level in ICANN activities, and that your organization will > > support its individual members' informed participation in ICANN efforts > that > > affect end-users. > > > > The ALAC is eager to promote a productive working relationship between > your > > organization, other ALS, and the ALAC (and ICANN in general), and your > input > > on how we can make this a success would be greatly appreciated. > > > > We would like to offer some initial tools to help your organization keep > its > > members informed (about significant news from ICANN and information on > ICANN > > policy-development efforts) and engaged in activities of interest: > > > > > > - Point of Contact for your Organisation: Please send an email to > > mailto:staff@atlarge.icann.org identifying the names and email > addresses of > > one or two individuals who will be the point of contact for information > and > > correspondence regarding ICANN At-Large. If this changes, please let us > > know. > > > > > > - At Large Mailing Lists. There are many At Large email lists, for each > > region; you can sign up for them and manage your subscriptions at: > > http://atlarge-lists.icann.org/mailman/listinfo . The points of contact > you > > identify will automatically be added to your region's list just for > > accredited ALSes to discuss regional issues and to the mailing list for > > Staff announcements (only Staff can post messages to that list); you are > > invited to join others as you wish. > > > > - ALS information. Information about your organization will be shared > with > > the At-Large community to enable individuals interested in your group's > > activities to contact you, and to encourage cooperation with other groups > > interested in ICANN activities in your geographic region. Please complete > > and email the form at the bottom of this note to staff(a)atlarge.icann.org > . > > > > - ALAC website. The ALAC website (http://www.atlarge.icann.org > > <http://www.atlarge.icann.org/> ) is a good source for ICANN news and > > information of interest to individual Internet users. We encourage you > to > > provide your members with a link. The ALAC relies on volunteers to > > translate information into multiple languages. Translations of documents > on > > the website are welcome and should be sent to > > <mailto:staff@atlarge.icann.org> > > > > - At-Large Regional Websites. Regional wiki webpages also have been > created > > to distribute information (including in local languages) on activities, > > events and issues of particular interest to people in each region. These > are > > maintained by the community. They are: > > > > African Region: http://www.afralo.org > > > > Asia/Australia/Pacific Region: http://www.apralo.org > > <http://www.apralo.org/> > > > > European Region: http://www.euralo.org <http://www.euralo.org/> > > > > Latin America/Caribbean Region: http://www.lacralo.org > > <http://www.lacralo.org/> > > > > North American Region: http://www.naralo.org <http://www.naralo.org/> > > > > > > We have included an Starter Kit that includes key information on ALAC and > > At-Large communication tools. We have also included the ALS Beginners > Guide > > which explains how best to engage within At-Large. > > > > We look forward to working with you and your organization's members to > > advance individual Internet users' interests within ICANN. If you have > any > > questions, or need additional information, please contact us at > > staff(a)atlarge.icann.org. > > > > Sincerely, > > > > The At-Large Advisory Committee > > > > http://www.atlarge.icann.org <http://www.atlarge.icann.org/> > > staff(a)atlarge.icann.org > > > > --------------------------- > > > > > > Name: > > > > > > Location (city/country/region; whatever is relevant to your membership): > > > > > > Mission: > > > > > > Member benefits: > > > > > > Contacts (name/s and email address/es -- title/s optional): > > > > > > Website: > > > > > > Other (additional informational you would like included): > > > > > > > > > > > > > > <Starter Kit for ALS Representatives - EN.pdf> > > <Starter Kit for ALS Representatives - ES.pdf> > > <alses-beginners-guide-02jun14-en(1).pdf> > > <alses-beginners-guide-02jun14-es.pdf> > > _______________________________________________ > > ALAC-Internal mailing list > > ALAC-Internal(a)atlarge-lists.icann.org > > https://atlarge-lists.icann.org/mailman/listinfo/alac-internal > > > > ALAC Wiki: > https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > > > > At-Large Website: http://atlarge.icann.org > lac-discuss-en lista de correo > lac-discuss-en(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > > > [[--Original text (es) http://mm.icann.org/transbot_archive/a4792b5e40.html --]]

1 0

Re: [lac-discuss-en] Welcome to-At Large!
by vanda＠uol.com.br June 7, 2015

June 7, 2015

[[--Translated text (es -> en)--]] Subject: Re: Welcome to-At Large! From: vanda(a)uol.com.br First of all it is necessary to engage in new concepts and ICANN structure, only to later understand the key points that discusses how the transition from IANA and supervision issues providing slopes to the community. It is also necessary that new understand the current scenario with 635 new TLDs to the end of May. And what this means. In Nicaragua they may even have the opportunity to participate presentation of some of these points. Hugs Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, 1004 cj 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos. From: Alejandro Pisanty <apisanty(a)gmail.com> Date: Thursday, June 4, 2015 at 0:48 To: Fatima Cambronero <fatimacambronero(a)gmail.com> Cc: "lac-discuss-es(a)atlarge-lists.icann.org" <lac-discuss-es(a)atlarge-lists.icann.org> Subject: Re: [lac-discuss-en] Welcome to-At Large! +1 What are the discussions on substantive issues and development ICANN policies with which we show our colleagues from IEEE Nicaragua to illustrate how the things he says Diego made? Alejandro Pisanty On Wed, June 3, 2015 at 6:10 PM, Fatima Cambronero <fatimacambronero(a)gmail.com> wrote: > Diego, todas/os, > > En mi caso, yo no me atrevería a pedirle a un recién llegado, algo que yo no > estoy segura de estar aportando como es "Aportes y gestión activa en favor de > de los ususarios del Internet" de un determinado país o de la región. > Quizás con esta nueva ALS que se incorpora, nos sirva a quienes ya estamos > involucrados, para hacer una introspección y revisar qué estamos aportando > cada uno de nosotros. > > Mario y colegas de IEEE Nicaragua, sean bienvenidos y me encuentro a su > disposición para colaborarles en este nuevo proceso. > > > Saludos cordiales, > Fatima Cambronero > > > 2015-06-03 18:00 GMT-05:00 <dacostabastidas(a)dtech.ec>: >> >> [[--Translated text (en -> es)--]] >> >> Asunto: Re: Bienvenidos a-At Large! >> Desde: dacostabastidas(a)dtech.ec >> >> Bienvenidos!, ESPERAMOS Aportes y gestión activa en favor de de los >> ususarios >> del Internet de Nicaragua y de la región. >> >> >> Atte >> >> >> Diego Acosta Bastidas >> >> >> 06.03.2015 16:30 GMT-05: 00 <hcarrascob(a)gmail.com> : >>> > >>> > [[--Translated text (en -> es)--]] >>> > >>> > Asunto: Re: Bienvenidos a-At Large! >>> > Desde: hcarrascob(a)gmail.com >>> > >>> > Bienvenidos a Lacralo !!! >>> > >>> > >>> > >>> > >>> > Saludos >>> > >>> > >>> > Enviado desde mi iPhone >>> > >>> > >>>> > > El 03-06-2015, a las 20:31, "staff(a)atlarge.icann.org" < >>> > staff(a)atlarge.icann.org> escribiÃ³: >>>> > > >>>> > > Dear Mario and Carlos, >>>> > > >>>> > > ICANN's At-Large Advisory Committee (ALAC) is pleased to inform you >>>> that >>>> > > (224) IEEE Nicaragua has been certified as an At-Large Structure (ALS). >>> > The >>>> > > ALAC greatly appreciates your group's interest in involving individual >>> > users >>>> > > in ICANN and looks forward to working with you and your colleagues. >>>> > > >>>> > > The purpose of ALS certification is to recognize that your organization >>>> > > meets the necessary criteria to involve individual Internet users at >>>>>> The local or issue level in ICANN activities, and That your organization >>>> Will >>>>>> Support STI Individual members' informed participation in ICANN Efforts >>>> That >>>>>> Affect end-users. >>>>>> >>>>>> The ALAC is eager to Promote a productive working relationship Between >>>> Your >>>>>> Organization, other ALS, and the ALAC (and ICANN in general), and your >>>> Input >>>>>> On how we can make this a success would be Greatly appreciated. >>>>>> >>>>>> We would like to offer some initial tools to help your organization >>>> Keep >>>> STI >>>>>> Informed members (about significant news from ICANN and information on >>>> ICANN >>>>>> Policy-development Efforts) and engaged in activities of interest: >>>>>> >>>>>> >>>>>> - Point of Contact for your Organisation: Please send an email to >>>>>> Mailto: staff(a)atlarge.icann.org Identifying the names and email >>>> Addresses of >>>>>> One or two Individuals Who Will be the point of contact for information >>>> And >>>>>> Correspondence Regarding ICANN At-Large. If This Changes, please let us >>>>>> Know. >>>>>> >>>>>> >>>>>> - At Large Mailing Lists. There are many At Large email lists, for each >>>>>> Region; you can sign up for them and manage your subscriptions at: >>>>>> Http://atlarge-lists.icann.org/mailman/listinfo. The points of contact >>>> You >>>>>> Identify Automatically will be added to your region's list just for >>>>>> Accredited ALSes to discuss regional issues and to the mailing list for >>>>>> Announcements Staff (Staff only can post messages To That list); you are >>>>>> Invited to join others as you wish. >>>>>> >>>>>> - ALS information. Information About Your organization will be shared >>>> With >>>>>> The At-Large community to enable Individuals interested in your group's >>>>>> Activities to contact you, and to Encourage cooperation with other >>>> Groups >>>>>> Interested in ICANN activities in your geographic region.Please >>>> Complete >>>>>> And email the form at the bottom of esta note to >>>> Staff(a)atlarge.icann.org >>>>. >>>>>> >>>>>> - ALAC website. The ALAC website (http://www.atlarge.icann.org >>>>>> <http://www.atlarge.icann.org/> ) Is a good source for news and ICANN >>>>>> Information of interest to Internet users individually. We Encourage you >>>> To >>>>>> Provide your members with a link. The ALAC Relies on volunteers to >>>>>> Translate information into multiple languages. Translations of >>>> Documents >>>> On >>>>>> The website are welcome and Should be sent to >>>>>> <mailto:staff@atlarge.icann.org> >>>>>> >>>>>> - At-Large Regional Websites. Regional wiki webpages Also Have Been >>>> Created >>>>>> To distribute information (including in the local languages) on activities, >>>>>> Events and issues of particular interest to people in each region. >>>> These >>>> Are >>>>>> Maintained by the community.They are: >>>>>> >>>>>> African Region: http://www.afralo.org >>>>>> >>>>>> Asia / Australia / Pacific Region: http://www.apralo.org >>>>>> <http://www.apralo.org/> >>>>>> >>>>>> European Region: http://www.euralo.org <http://www.euralo.org/> >>>>>> >>>>>> Latin America / Caribbean Region: http://www.lacralo.org >>>>>> <http://www.lacralo.org/> >>>>>> >>>>>> North American Region: http://www.naralo.org <http://www.naralo.org/> >>>>>> >>>>>> >>>>>> We have included an Starter Kit That includes key information on ALAC and >>>>>> At-Large communication tools. We have also included the ALS Beginners >>>> Guide >>>>>> Which Explains how best to engage Within At-Large. >>>>>> >>>>>> We look forward to working with you and your organization's members to >>>>>> Individual advance Internet users' interests Within ICANN.If You have >>>> Any >>>>>> Questions, or need additional information, Please contact us at >>>>>> Staff(a)atlarge.icann.org [ERROR: Sentence too long to translate (2532> 1800 bytes)]. >>>>>> >>>>>> ALAC Wiki: >>>> >>> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA>>> C) >>>>>> >>>>>> At-Large Website: http://atlarge.icann.org >>>> Lac-discuss-en mailing list >>>> Lac-discuss-en(a)atlarge-lists.icann.org >>>> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en >>>> >>>> >>>> >> >> >> [[--Original text (es) http://mm.icann.org/transbot_archive/c1f1b89465.html --]]

1 0

Re: [lac-discuss-en] ? = Utf-8 OPINION q = C3 = B3n_sobre_futuro_CEO_de_ICANN =
by asoto＠ibero-americano.org June 7, 2015

June 7, 2015

[[--Translated text (es -> en)--]] Subject: Re:? = Utf-8 OPINION q = C3 = B3n_sobre_futuro_CEO_de_ICANN = From: asoto(a)ibero-americano.org Yes please. That way we will all know. Finally I leave this reflected in our wiki for the record. Best regards. Alberto Soto On June 7, 2015 1:10:30 GMT-03: 00, "Mendez Eduado" <eduardo(a)mendez.net.ve> He wrote: > Greetings comrades! > >> On 06/06/2015, at 10:57 pm, Alberto Soto > <asoto(a)ibero-americano.org> He wrote: >> >> Dear, the ICANN Board is interested in the review > What are the features that our community would like to see > Future CEO of ICANN. >> There will be a public meeting with the Council on the issue of CEO >, On Thursday, June 25 just before the public forum. >> It would be desirable to review this issue and substantiate that > Opinion. >> I think it's a good opportunity to participate and make our voice > Considered. >> These opinions should be sent before 20 June 2300 > UTC for the meeting we will have the RALOs with the Board Chair. >> Many thanks and best regards >> > > These views would be sent as a reply to this email? > > A hug > > Eduardo Mendez > Internauta Venezuela > > >> Alberto Soto >> >> >> >> < https://www.avast.com/antivirus> >> Avast antivirus software has analyzed this email > For viruses. >> Www.avast.com < https://www.avast.com/antivirus> >> _______________________________________________ >> Lac-discuss-en mailing list >> Lac-discuss-es(a)atlarge-lists.icann.org > <mailto:lac-discuss-es@atlarge-lists.icann.org> >> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > < https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es> >> >> Http://www.lacralo.org <http://www.lacralo.org/> - Sent from my Android device with K-9 Mail. Please excuse my brevity. [[--Original text (es) http://mm.icann.org/transbot_archive/1454cd26b7.html --]]

1 0