June 2007 - At-Large - lists.icann.org

Re: [At-Large] [NA-Discuss] MOU - ICANN Obligations: Redelegation
by Jacqueline A. Morris June 14, 2007

June 14, 2007

Danny My email was to inform you that it is not ONLY a NA concern, and that the rest of the regions are working on cc issues as well. This was informational and there is no reason to threaten the existence of the NARALO. The NA region is part of the global AtLarge, and should be interested in working together with the rest of the world, and not only in isolation. -----Original Message----- From: Danny Younger [mailto:dannyyounger@yahoo.com] Sent: Thursday, June 14, 2007 9:42 AM To: jam(a)jacquelinemorris.com; 'NA Discuss' Subject: RE: [NA-Discuss] MOU - ICANN Obligations: Redelegation Hi Jacqueline, Sorry to disagree, but the NeuStar contract with the USG is scheduled to expire by the end of October (posing a potential redelegation issue), and frankly we don't have the luxury of waiting for the ALAC and the CCNSO to come to grips with the global aspects of the problem. This is a timely regional issue for us that we should be at liberty to handle by way of positing an ICANN obligation in the MOU (which is within our rights to request). The RALOs exist to deal with regional concerns. Let us handle this matter in our own fashion or let's just scrap the RALO concept. regards, Danny --- "Jacqueline A. Morris" <jam(a)jacquelinemorris.com> wrote: > Hi Danny > This is a concern in other places, and ALAC has set > up several meetings with > ccNSO in San Juan to discuss how we can work > together on issues such as > this. I don't think that it belongs in the NARALO > MoU, but rather is a > global issue that ALL regions should work on > together. > Jacqueline > > -----Original Message----- > From: Danny Younger [mailto:dannyyounger@yahoo.com] > Sent: Thursday, June 14, 2007 9:11 AM > To: NA Discuss > Subject: [NA-Discuss] MOU - ICANN Obligations: > Redelegation > > I remain troubled by the total lack of transparency > in > the ccTLD redelegation process. Has anyone ever > seen > a detailed redelegation request posted for > consideration prior to action being taken by the > Board? > > The .us situation is particularly bad. On the last > go-around ICANN bypassed the normal IANA processes > to > declare an "emergency redelegation" -- see > http://www.icann.org/announcements/announcement-19nov01.htm > > I certainly don't want the relevant Internet > community > being kept in the dark should the delegation of the > .us namespace become an issue. > > I would ask that the NARALO MOU stipulate that ICANN > has the obligation to inform the NARALO upon the > receipt of any relevant ccTLD redelegation request > (.us or .ca) so that community input may be provided > (as per RFC 1591: "it is also appropriate for > interested parties to have some voice in selecting > the > designated manager.") > > > > > > ____________________________________________________________________________ > ________ > Be a better Globetrotter. Get better travel answers > from someone who knows. > Yahoo! Answers - Check it out. > http://answers.yahoo.com/dir/?link=list&sid=396545469 > > _______________________________________________ > NA-Discuss mailing list > NA-Discuss(a)atlarge-lists.icann.org > http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atlarge-lists.ica > nn.org > --- > Draft MoU with ICANN: > http://www.icannwiki.org/NA_RALO_MOU > > Draft Operating Principles: > http://www.icannwiki.org/NA_RALO_OP > > Draft Code of Conduct: > http://www.icannwiki.org/NARALO_Code_of_Conduct > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.8.15/848 - > Release Date: 6/13/2007 > 12:50 PM > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.8.15/848 - > Release Date: 6/13/2007 > 12:50 PM > > > ____________________________________________________________________________ ________ Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.15/848 - Release Date: 6/13/2007 12:50 PM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.15/848 - Release Date: 6/13/2007 12:50 PM

1 0

Cómo funciona la administración de nombres de dominio
by Robert Guerra June 14, 2007

June 14, 2007

(texto en español a continuación) I just came across the following spanish language blog entry on and about "The administration of domain names". I have only quickly gone through the document and thought it could be of interest to at-large. I have not given it a thorough read through, so i won't yet comment on its accuracy. Keen to get comments from those other spanish speakers involved and engaged in At-large. ## En español ## Acabo de encontrar el siguiente articulo sobre la administración de nombres de dominio. Creo que sería interesante saber lo que opinias sobre el articulo, sobre todo si hay algun error en el texto. A la espera de comentarios de los hispano parlantes en el espacio at- large. saludos/regards Robert -- http://www.arkhaios.com/?p=49 - ARKHAIOS - http://www.arkhaios.com - Cómo funciona la administración de nombres de dominio Posted By PedroNel On June 12, 2007 @ 6:11 pm In Nombres de dominio, Estados Unidos, Organismos de Nombres de dominio, internet, Sociedad de la información | No Comments Muchas personas creen que internet es el reino del “no gobierno”, cuando es exactamente lo contrario, es decir, si hay algo regulado es la internet, lo que sucede -y en eso sí es diferente a cualquiera otro caso global- es que se trata de reglas generalmente aceptadas, mas no de reglas impuestas al estilo de las legislaciones nacionales. En internet lo que uno encuentra son montones de organismos que trabajan coordinadamente en escenarios consensuados, y cuyas recomendaciones son atendidas por todos. Quien desee conocer cómo funciona internet, debe visitar el site de la [1] Internet Society, la cual se autodefine de la siguiente manera: “The Internet Society is a non-profit, non-governmental, international, professional membership organization. Its more than 100 organization members and over 20,000 individual members in over 180 nations worldwide represent a veritable who’s who of the Internet community. You should be a member, too. ” (citado de la portada) Uno de los aspectos más interesantes del funcionamiento de internet es el sistema de nombres de dominio: “El sistema de nombres de dominio (DNS) ayuda a los usuarios a navegar en Internet. Las computadoras en Internet tienen una dirección única llamada “dirección IP” (dirección de protocolo de Internet). Como las direcciones IP (compuestas por una cadena de números) son difíciles de recordar, el DNS permite usar una cadena de letras (el “nombre del dominio”) para que usted pueda escribir [2] www.icann.org en vez de “192.0.34.163”. El DNS traduce el nombre del dominio a la dirección IP que le corresponde y lo conecta con el sitio web que desea. El DNS también permite el funcionamiento del correo electrónico, de manera tal que los mensajes que envía lleguen al destinatario que corresponda, y muchos otros servicios de Internet.” ([3] http://www.icann.org/tr/ spanish.html) El sistema de nombres de dominio está coordinado por la Internet Corporation for Assigned Names and Numbers ([4] ICANN). ICANN “…es una organización sin fines de lucro que opera a nivel internacional, responsable de asignar espacio de direcciones numéricas de protocolo de Internet (IP), identificadores de protocolo y de las funciones de gestión [o administración] del sistema de nombres de dominio de primer nivel genéricos (gTLD) y de códigos de países (ccTLD), así como de la administración del sistema de servidores raíz. ” ([5] http://www.icann.org/tr/spanish.html) Básicamente “ICANN es responsable de la coordinación de la administración de los elementos técnicos del DNS para garantizar una resolución unívoca de los nombres, de manera que los usuarios de Internet puedan encontrar todas las direcciones válidas. Para ello, se encarga de supervisar la distribución de los identificadores técnicos únicos usados en las operaciones de Internet, y delegar los nombres de dominios de primer nivel (como .com, .info, etc.).” ([6] http:// www.icann.org/tr/spanish.html) En ICANN participan gobiernos, organismos internacionales (”organismos de tratados internacionales” en la terminología de ICANN) y negocios privados. Sin embargo, el origen de la capacidad de ICANN respecto del sistema, es un memorando de entendimiento con el Gobierno de Estados Unidos [7] (”Memorandum of Understanding Between the Department of Commerce and the Internet Corporation for Assigned Names and Numbers” ), comoquiera que internet tiene origen en ese país. En concreto, el espacio de direcciones y los nombres de dominio se manejan a trávés de la National [8] Telecommunications and Information Administration (NTIA) del [9] Departamento de Comercio de Estados Unidos (al respecto la página [10] “Domain Names: Management of Internet Names and Addresses” de la NTIA). Respecto de la propia ICANN, se tiene que “ICANN está gobernada por una Junta Directiva, de gran diversidad internacional, encargada de supervisar el proceso de desarrollo de normas y políticas. El Director General de ICANN está a la cabeza del personal de diversas nacionalidades que trabaja en tres continentes, y que asegura que ICANN cumpla con su compromiso operacional con la comunidad de Internet.” ([11] http://www.icann.org/ tr/spanish.html) ICANN tiene diferentes organizaciones de apoyo: Organización de apoyo para direcciones (ASO) - <[12] www.aso.icann.org> Organización de apoyo para nombres de dominio y código de países (CCNSO) - <[13] www.ccnso.icann.org> Organización de apoyo para nombres genéricos (GNSO) - <[14] www.gnso.icann.org> Comité asesora para la participación individual global (ALAC) - < [15] www.alac.icann.org> Comité asesora gubernamental - <[16] www.gac.icann.org> En materia de nombres de dominio hay varias clases, pero la que interesa en principio son los nombres de dominio de nivel superior (top level domains), de los cuales hay tres tipos: 1. Dominios de código de país (Country Code Domains), para el uso particular de los países (como .co para colombia, .us para Estados Unidos, etc., según el [17] ISO-3166). 2. Genéricos (Generic Domains), para el público en general (.aero, .asia, .biz, .cat, .com, .coop, .edu, .gov, .info, .jobs, .mobi, .int, .mil, .museum, .name, .net, .org, .pro, .tel y .travel) [18] salvo algunas excepciones. 3. Dominios de infraestructura de internet (Domain for Internet infrastructure, en realida es .arpa) Dado que el tercero es en realidad un dominio especial, cualquier reflexión sobre nombres de dominio puede concentrarse en los dos primeros (ver [19] “Domain Name Services” en el site de la [20] IANA). En el caso de ccTLD existen dos documentos base, aceptados por consenso de la comunidad internet: - El [21] RFC (Request for Comments) 1591 . Los documentos RFC son documentos técnicos relacionados con la operación de internet coordinados por un [22] editor, actualmente la Networking Division del USC [23] Information Sciences Institute (ISI) (al principio fue una persona: [24] Jon Postel). - El [25] ICP-1 de IANA. ICANN opera gracias a un [26] “Memorando de Entendimiento” de 1998 suscrito con el Departamento de Comercio de Estados Unidos, y en 2001 recibió una [27] licencia para el uso de [28] InterNIC (Internet Network Information Center ) como marca del servicio de información central sobre nombres de dominio. Inicialmente, InterNIC era el nombre del organismo que administraba los nombres de dominio y las direcciones en internet, hasta el paso de las mismas a ICANN en 1998 (inicialmente, el mismo trabajo lo hizo la NIC -Network Information Centre- del Stanford Research Institute o SRI, luego transferido a la Internet Assigned Numbers Authority, o [29] IANA). No es lo mismo “nombre de dominio” que dirección de internet (la “IP”, como se llama coloquialmente, aunque IP es “internet protocol”). Para más información sobre direcciones IP puede visitar la página de la IANA [30] “Abuse Issues and IP Addresses”. Article printed from ARKHAIOS: http://www.arkhaios.com URL to article: http://www.arkhaios.com/?p=49 URLs in this post: [1] Internet Society: http://www.isoc.org/ [2] www.icann.org: http://www.icann.org/ [3] http://www.icann.org/tr/spanish.html: http://www.icann.org/tr/ spanish.html [4] ICANN: http://www.icann.org [5] http://www.icann.org/tr/spanish.html: http://www.icann.org/tr/ spanish.html [6] http://www.icann.org/tr/spanish.html: http://www.icann.org/tr/ spanish.html [7] (”Memorandum of Understanding Between the Department of Commerce and the Internet Corporation for Assigned Names and Numbers”: http:// www.ntia.doc.gov/ntiahome/domainname/icann.htm [8] Telecommunications and Information Administration (NTIA): http:// www.ntia.doc.gov/ [9] Departamento de Comercio : http://www.commerce.gov/ [10] “Domain Names: Management of Internet Names and Addresses”: http://www.ntia.doc.gov/ntiahome/domainname/ [11] http://www.icann.org/tr/spanish.html: http://www.icann.org/tr/ spanish.html [12] www.aso.icann.org: http://www.aso.icann.org/ [13] www.ccnso.icann.org: http://www.ccnso.icann.org/ [14] www.gnso.icann.org: http://www.gnso.icann.org/ [15] www.alac.icann.org: http://www.alac.icann.org/ [16] www.gac.icann.org: http://www.gac.icann.org/ [17] ISO-3166: http://www.iso.org/iso/en/prods-services/iso3166ma/ 02iso-3166-code-lists/list-en1.html [18] salvo algunas excepciones: http://www.iana.org/gtld/gtld.htm [19] “Domain Name Services”: http://www.iana.org/domain-names.htm [20] IANA: http://www.iana.org [21] RFC (Request for Comments) 1591: http://www.isi.edu/in-notes/ rfc1591.txt [22] editor: http://www.rfc-editor.org/ [23] Information Sciences Institute (ISI): http://www.isi.edu/index.php [24] Jon Postel: http://www.isoc.org/postel/ [25] ICP-1: http://www.icann.org/icp/icp-1.htm [26] “Memorando de Entendimiento” de 1998: http://www.icann.org/ general/icann-mou-25nov98.htm [27] licencia: http://www.icann.org/general/internic-license-08jan01.htm [28] InterNIC: http://www.internic.org [29] IANA: http://www.arkhaios.comwww.iana.org [30] “Abuse Issues and IP Addresses”: http://www.iana.org/faqs/abuse- faq.htm

1 0

Re: [At-Large] Teleconference facility (was: Add to agenda for teleconf...)
by Alan Greenberg June 12, 2007

June 12, 2007

As I said in reply to Alice, no fixed line phone = absolutely necessary. Regarding Skype, I am dubious that these problems can be reliably fixed in the short term. But I would be delighted to be proven wrong. Regarding cost, I think that it is completely reasonable that ICANN arrange to reimburse you for real out-of-pocket costs i participating in conference calls. Alan At 12/06/2007 02:55 PM, Hong Xue wrote: >On 6/12/07, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >The GNSO uses the same teleconference facility. I would guess that >the GNSO e-mails include specific times because the GNSO staff put >them there, not because of the service provider. The GNSO conferences >work relatively well most of the time, and with FAR more people >participating. I suspect that part of the issue is that we have more >people from "unusual" locations which require call-outs (and >seemingly no mechanism to know that they have dropped and need to be >re-called). > >I think that we should outlaw the use of Skype and equivalent, and >strongly discourage mobile phones unless absolutely necessary. > > >I don't believe that Skype should be excluded, but it should be >better commodated by the service operator to resolve the problem of >echoing. As for mobile, I don't like using it at all for the cast is >very high. However, what if a participant (such as me) is so poor >that she has no fix-line phone? > >Hong > > > > > > >At 12/06/2007 01:16 PM, Izumi AIZU wrote: > > >I really ask ICANN/Nick to reconsider the Conf Call operator and > >suggest the feasibility of using the one GNSO is using > >(Alan, am I correct that they are better in service and quality?) > >Also to prevent some mistake Vittorio had, I also like to suggest > >the specific time to each member of ALAC be displayed in the > >call notice, just like the GNSO call annoucement does. > > >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org > >At-Large Official Site: <http://www.alac.icann.org>http://www.alac.icann.org >ALAC Independent: <http://www.icannalac.org>http://www.icannalac.org >

1 0

ICANN Budget
by Izumi AIZU June 12, 2007

June 12, 2007

I am concerned about the new proposed budget ICANN released, in the way it is presented. You cannot really find how much exactly ALAC's budget is allocated from the documents. >From the slide, "ICANN Fiscal Year 2008 Proposed Budget Overview" at page 4, it is under "Outreach" and combined with Fellowship and totals to $1,068K Then at page 21 of "Proposd Budget Fiscal Year 2007-2008," more detailed version dated 17 May says "Outreach" includes Ombudsman ($449K), Media Transparency ($1,040K), Fellowship ($308K), Board & SOAC Travel ($1,464K) etc... We need more accurate and transparent figures for the AtLarge Budget. Something like: ALAC Travel Cost RALO/ALS Travel Cost RALO Regional Meeting Cost AtLarge Staff Cost/Regional Staff Cost ALAC related Communications cost (ie Web, wiki, Conf call) ALAC Review Cost etc. AND, we also need the record of previous expenditures so that we can compare them. thanks, izumi -- >> Izumi Aizu << Institute for HyperNetwork Society Kumon Center, Tama University * * * * * << Writing the Future of the History >> www.anr.org

1 0

Board liaison report
by Vittorio Bertola June 12, 2007

June 12, 2007

All, here is my report on what happened in the Board since the last ALAC call. The Board held a retreat in Mountain View, California on May 11-12. Board retreats are devoted to strategic issues, rather than to dealing with current agenda items. In particular, this one featured a presentation on rights and duties of ICANN Directors under the applicable US laws; some reports and advance discussions on the next IGF; and a discussion on ICANN's responsibilities towards its constituents, in which I tried to raise the post-Registerfly issues and, in general, the importance of strengthening ICANN's responsiveness to registrants. A Board call was held on May 15, but due to a change of time I ended up being on the flight back from the US at that very time. Anyway, the main agenda item was the release of the draft budget for next year, which has now been published for comment. The rest of the report refers to discussions happening on the Board list, and decisions taken in the meanwhile. The third ICANN meeting of this year, which was supposed to be in Asia/Pacific, will be held in Los Angeles instead. There was really no alternative due to a number of practical problems, but I (and others) stressed the importance of keeping the rotation running; staff plans to replace the next North American meeting with an Asia Pacific one, as per a new schedule that is already published. There has been a lot of discussion on the increasing speed of exhaustion of IPv4 addresses, and whether ICANN should have a role in the transition, and which one, given that most of the policy-making responsibility lies with the RIRs, that are currently discussing policy proposals for a fair distribution of the last chunks of the IPv4 space (regions that traditionally used less of them are asking to get a reservation so that they can continue getting IPv4 addresses for longer than the others). This issue is likely to come up more and more in the upcoming months. IDNs also came up as an issue - there are some Board members that share the feeling that quicker progress is necessary on this matter. In San Juan this issue should be raised again in the various involved SOs and ACs, also as some advices by some of them (for example, on the matter of IDN ccTLDs) are expected to arrive. "IDN ccTLDs" is a very sensible matter involving a lot of complex issues (ranging from roles & responsibilities of different actors, to the extent & applicability of national sovereignty) and will possibly become hot in the future. Domain tasting/kiting issues, and registrant protection ones, came up on the Board list regularly. The Board recognized our request for an issue report on domain tasting, and is waiting to see what comes out of it in the GNSO. Exactly as in the At Large, there are different preliminary views on the matter, but no immediate action is in sight as of this moment. On post-Registerfly, a RFP on data escrow was posted, and we are waiting for the CEO to release a plan in San Juan. Finally, on June 8 Alejandro Pisanty's term on the Board finished, and his seat was taken by Bruce Tonkin, newly elected to the Board by the GNSO. The next Board call is scheduled for June 18, and will likely feature a discussion of the Ombudsman's reports on the ALAC's alleged failures to treat ALS applications fairly and in a timely manner. Wendy and Patrick's blog posts on the EURALO elections also spawned some discussion on how well the ALAC is doing. In the end, while it is likely that any structural change will be deferred to the upcoming ALAC review, there may be some time devoted by the Board, in San Juan and/or on the next call, to the discussion of ALAC performance issues. Regards, -- vb. Vittorio Bertola - vb [a] bertola.eu <-------- --------> finally with a new website at http://bertola.eu/ <--------

1 0

At-Large Travel Policy
by Nick Ashton-Hart June 11, 2007

June 11, 2007

Dear Community: I'd like to advise you of an update to the At-Large Travel Policy, attached in four language editions below. The change is to advise you that ICANN are adopting a per-diem based system for expenses over and above those paid directly by ICANN. For those attending the San Juan meeting from LAC, NA, and the ALAC committee, a separate email will advise you on the per diem details for the meeting. Current versions of the travel policy, and all forms, will always be available at: https://st.icann.org/alac/index.cgi? policies_and_procedures. -- Regards, Nick Ashton-Hart Director, At-Large ICANN PO Box 32160 London N4 2XY United Kingdom Main Tel: +44 (20) 8800-1011] USA Tel: +1 (202) 657-5460 Fax: +44 (20) 7681-3135 mobile: +44 (7774) 932798 email: nick.ashton-hart(a)icann.org Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart

1 0

Report of the ICANN Staff, May 2007 (with attachment this time)
by Nick Ashton-Hart June 11, 2007

June 11, 2007

Dear ALAC Members: Herewith please find the written report of the Staff for the month of May 2007. The attachment didn't go through the first time due to a file naming issue; hopefully this one will work. Apologies :) -- Regards, Nick Ashton-Hart Director, At-Large ICANN PO Box 32160 London N4 2XY United Kingdom Main Tel: +44 (20) 8800-1011] USA Tel: +1 (202) 657-5460 Fax: +44 (20) 7681-3135 mobile: +44 (7774) 932798 email: nick.ashton-hart(a)icann.org Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart

1 0

contentious with whitlock
by Amber June 10, 2007

June 10, 2007

Want to be the top all night long? Be sexual giant all night long. Buy Licensed and Quality Viagra or Cialis. Unbelievable Viagra and Cialis offer! http://issrgh.voomsuper.hk/?76539125 Instant worldwide shipping and friendly support

1 0

{Filename?} Report of the ICANN Staff, May 2007
by Nick Ashton-Hart June 9, 2007

June 9, 2007

Warning: This message has had one or more attachments removed Warning: (ALAC 2007 SD 5 Report of the Staff for May 2007 - EN.doc.pdf). Warning: Please read the "EMWD-Attachment-Warning.txt" attachment(s) for more information. Dear ALAC Members: As promised in the May 2007 Teleconference, herewith please find the written report of the staff for the month of May 2007. -- Regards, Nick Ashton-Hart Director, At-Large ICANN PO Box 32160 London N4 2XY United Kingdom Main Tel: +44 (20) 8800-1011] USA Tel: +1 (202) 657-5460 Fax: +44 (20) 7681-3135 mobile: +44 (7774) 932798 email: nick.ashton-hart(a)icann.org Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart

1 0

ConfirmSystem: registrar@icann.org [[246c9d80e4f8bb2e]]
by confirmsystem＠icann.org June 8, 2007

June 8, 2007

Hello You have sent a message to registrar(a)icann.org, an ICANN public comment forum. In order for your message to be accepted and published, we need for you to acknowledge your understanding of the fact that any messages sent to any ICANN comment forum will be published on the web. While the archiving process does obscure some email addresses, any personal identifying data will likely also become public. You can confirm your desire to publish your message two ways: 1) Reply to this message, without altering the subject line (The "Re: " added by many mail clients is OK, but please note that this method is *not* foolproof -- there is too much variety in how email clients handle messages to be sure we can parse every reply.) or 2) Visit the URL <http://confirm.icann.org/?s=246c9d80e4f8bb2e&l=registrar@icann.org> If you want to be very sure that your message gets through, do both steps above -- it does no harm to confirm more than once. For your reference, the subject of the message you sent was: "Repl1ca for you" and it arrived at approximately Fri Jun 8 11:20:25 2007. Thank you for your message. --------------------------------------------------------------- ConfirmSystem: registrar(a)icann.org [[246c9d80e4f8bb2e]] 4

1 0