March 2008 - AFRI-Discuss - lists.icann.org

ALS application from MACSIS
by At-Large Staff March 18, 2008

March 18, 2008

Dear all, Unfortunately the ALS application we sent out yesterday was stripped from the email. Please find it attached to this mail. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

AT-LARGE ANNOUNCEMENT: Resignation of ALAC Vice-Chair
by At-Large Staff March 18, 2008

March 18, 2008

Dear Community: The Chair of the ALAC has requested that the At-Large Staff notify you that Robert Guerra has resigned his office as Vice-Chair of the At-Large Advisory Committee for personal reasons. The ALAC wishes to convey its thanks for his work in this position until his resignation. Robert remains an elected Member of the ALAC from North America and the representative of At-Large to the Security and Stability Advisory Committee. This situation is provided for in Rule 9.1 of the Rules of Procedure of the ALAC as adopted in October 2007: ³If for any reason whatsoever (including lack of quorum, lack or loss of eligibility requirements, resignation, or recall) an officer position becomes vacant before the end of the term, the Chair will promptly start an election to fill it, by sending an ³election call² message and starting the procedure from rule 9.1² In conformity with Rule 9.1 an election call message from the Chair will be forthcoming, which will provide the relevant details of the process to elect a replacement co-Vice-Chair. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 1

ALS application from MACSIS
by At-Large Staff March 17, 2008

March 17, 2008

Dear all, Please find attached the ALS application we received from the Moroccan Association of Civil Society for Information Society. The application has been filled in in French. We will send you the translated English version shortly. We will send you further information on the application in due course. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

Translation of Afri-discuss and Lac-discuss disabled
by Nick Ashton-Hart March 14, 2008

March 14, 2008

Dear All: As mentioned earlier today, we have now disabled the list translation interface. We will let you know once we have confidence that the interface will work properly again. -- Regards, Nick Ashton-Hart Director for At-Large Internet Corporation for Assigned Names and Numbers (ICANN) Main Tel: +33 (450) 40 46 88 USA Tel: +1 (202) 657-5460 Fax: +41 (22) 594-85-44 Mobile: +41 (79) 595 54-68 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

Machine Translation Interface problems
by At-Large Staff March 14, 2008

March 14, 2008

-------> [ENGLISH] AUTOMATIC TRANSLATION NOT REVISED FROM THE ORIGINAL MILTILINGUAL Dear All: As you know, the machine translation interface to the mailing lists in the LACRALO and the AFRALO are becoming less reliable. After requests from several of you, we have asked Funredes to disable the machine translation interface. We have set up a new test email list which we will connect to the translation interface. Once the problems are resolved, then we will let you know and enable machine translation again. Please accept our apologies. We will continue to work with Funredes on a solution. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org -------> [PORTUGUESE] TRADUCAO AUTOMATICA NAO REVISADA DO ORIGINAL Caro Tudo: Como você sabe, a relação da tradução de máquina às listas enviando no LACRALO e os AFRALO estão tornando-se mais menos de confiança. Após pedidos de diversos de você, nós pedimos Funredes para incapacitar a relação da tradução de máquina. Nós ajustamos acima uma lista nova do email do teste que nós conectássemos à relação da tradução. Uma vez que os problemas são resolvidos, então nós deixá-lo-emos saber outra vez e permitir a tradução de máquina. Aceite por favor nossos apologies. Nós continuaremos a trabalhar com Funredes em uma solução. -- consideração, Equipe de funcionários Em-Grande de ICANN email: staff(a)atlarge.icann.org -------> [FRANCAIS] TRADUCTION AUTOMATIQUE NON REVISEE DE L'ORIGINAL Cher Tous : Comme vous le savez, l'interface de traduction automatique aux listes d'expédition dans le LACRALO et les AFRALO deviennent moins fiables. Après des demandes de plusieurs de vous, nous avons demandé Funredes pour neutraliser l'interface de traduction automatique. Nous avons installé une nouvelle liste d'email d'essai que nous relierons à l'interface de traduction. Une fois que les problèmes sont résolus, alors nous vous laisserons savoir et permettre la traduction automatique encore. Veuillez agréer nos excuses. Nous continuerons à travailler avec Funredes sur une solution. -- respect, À-Grand Personnel d'ICANN courrier électronique : staff(a)atlarge.icann.org Service d'aide à l'intercompréhension Vérifiez les règles pour un meilleur usage: http://funredes.org/tradauto/index.htm/regles Intercomprehension aid service Check the rules for better use: http://funredes.org/tradauto/index.htm/rules Serviço do dae de compreensão Verificar as réguas para o uso melhor: http://funredes.org/tradauto/index.htm/reguas Servicio de ayuda a la intercomprensión Leer las reglas para un mejor uso: http://funredes.org/tradauto/index.htm/reglas

2 1

Re: [AFRI-Discuss] Machine Translation Interface problems
by Alan Levin March 14, 2008

March 14, 2008

-------> [ENGLISH] Original message in english > After requests from several of you, we have asked Funredes to > disable the > machine translation interface. > Well done, and many thanks! Tres bien! Merci beaucoup, aLain -- Alan Levin Tel: +27 21 409-7997 -------> [PORTUGUESE] TRADUCAO AUTOMATICA NAO REVISADA DO ORIGINAL EM inglês > Após pedidos de diversos de você, nós pedimos Funredes para > incapacitar a relação da tradução de máquina. > Poço feito, e muitos agradecimentos! Tres bien! Beaucoup de Merci, aLain -- Telefone De Alan Levin: +27 21 409-7997 -------> [FRANCAIS] TRADUCTION AUTOMATIQUE NON REVISEE DE L'ORIGINAL EN anglais > Après des demandes de plusieurs de vous, nous avons demandé Funredes > pour neutraliser l'interface de traduction automatique. > Puits fait, et beaucoup de mercis ! Tres bien ! Beaucoup de Merci, aLain -- Téléphone d'Alan Levin : +27 21 409-7997 Service d'aide à l'intercompréhension Vérifiez les règles pour un meilleur usage: http://funredes.org/tradauto/index.htm/regles Intercomprehension aid service Check the rules for better use: http://funredes.org/tradauto/index.htm/rules Serviço do dae de compreensão Verificar as réguas para o uso melhor: http://funredes.org/tradauto/index.htm/reguas Servicio de ayuda a la intercomprensión Leer las reglas para un mejor uso: http://funredes.org/tradauto/index.htm/reglas

1 0

Machine Translation Interface problems
by At-Large Staff March 14, 2008

March 14, 2008

Dear All: As you know, the machine translation interface to the mailing lists in the LACRALO and the AFRALO are becoming less reliable. After requests from several of you, we have asked Funredes to disable the machine translation interface. We have set up a new test email list which we will connect to the translation interface. Once the problems are resolved, then we will let you know and enable machine translation again. Please accept our apologies. We will continue to work with Funredes on a solution. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

URGENT: Statement on Domain Name Front Running
by At-Large Staff March 13, 2008

March 13, 2008

-------> [ENGLISH] AUTOMATIC TRANSLATION NOT REVISED FROM THE ORIGINAL MILTILINGUAL > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. --B_3288271616_1181695 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Dear Members: The statement reproduced below on the practice known as ³Domain Name Front Running² was approved by the NARALO on 10 March 2008. The ALAC reviewed this statement on 11th March 2008, and by decision of the ALAC you are kindly asked to register any objections to this statement not later than Monday 17 March at 1200 UTC after it will be considered approved by the ALAC and transmitted to the Board by the Chair at her convenience. The statement may be found at the following URL in addition to being reproduced below: https://st.icann.org/naralo/index.cgi?statement_to_the_icann_board_on_domain _front_running Statement on Domain Name Front Running Presented to NARALO by electronic Mail, 1 March 2008 Dear ICANN board directors: While we are aware that you have been monitoring the public outrage in response to registrar activities that have been variously described as "front-running" and/or "domain reservation" or "cart-hold" or "cart-reserve" activities, we are of the view that the obligation to safeguard the operational stability of Registrar Services now requires the immediate temporary establishment of a consensus policy curtailing such practices to be taken in accordance with the board's authority under the provisions set out in section 4.3.4 of the Registrar Accreditation Agreement, that states: "A specification or policy established by the ICANN Board of Directors on a temporary basis, without a prior recommendation by the council of an ICANN Supporting Organization, shall also be considered to be a Consensus Policy if adopted by the ICANN Board of Directors by a vote of at least two-thirds of its members, so long as the Board reasonably determines that immediate temporary establishment of a specification or policy on the subject is necessary to maintain the operational stability of Registrar Services, Registry Services, the DNS, or the Internet, and that the proposed specification or policy is as narrowly tailored as feasible to achieve those objectives." Please be advised that we have reached this conclusion based in part upon the following considerations: 1. The use of "cart-hold" or "cart-reserve" systems has been actively under discussion within the registrars constituency since early October 2007 when three different registrars first advanced the concept within the context of a straw poll on the impact to registrants were the AGP to be eliminated in its entirety (see footnote 1 at the bottom of the page) 2. The use of this domain name reservation practice next came to be adopted by a large-volume registrar (Network Solutions) on or about 8 January 2008, and the practice was immediately condemned by the community at large (with extensive coverage in the Tech media, the general press, in blogs world wide, on domain name forums, and on community discussion lists). 3. The actions of Network Solutions has now spawned a similar project on the part of another large-volume registrar (register.com) and we have no reason to believe that other large-volume registrars will refrain from rapidly setting up comparable efforts. (see Footnote 2). While we recognize that we are unable to point to an ICANN-approved definition of "operational stability of Registrar Services" (as no such definition exists within either current ICANN contracts or supporting materials), we take guidance from the ICANN Policy Document ICP-3 which posits that activities that do not interfere with the operation of the DNS are, generally speaking, those that operate within community-established norms. Such norms tend to respect a set of long-established principles such as the principle of least astonishment. When registrants currently search for a domain name at these registrars using normative search practices, they are clearly astonished by that which results from their efforts: the inability to readily register the domain name of their choice with a more competitive registrar and/or the domain name that they have selected appearing in the WHOIS with the name of the registrar as the registrant of record. (Footnote 3 The community's trust in ICANN's ability to manage the Domain Name System is at stake. It is inappropriate for such registrar activities to proceed unabated in a policy vaccuum. Accordingly we call upon the ICANN board to establish a temporary narrowly-tailored policy as a stopgap until such time as the relevant policy-recommending ICANN Supporting Organizations can provide comprehensive consensus policy solution. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org --B_3288271616_1181695 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable URGENT: Statement one Domain Name Running Face Dear Members: The statement reproduced below on the practice known as “Domain Name Front Running” was approved by the NARALO on 10 March 2008. The ALAC reviewed this statement on 11th March 2008, and by decision of the ALAC you are kindly asked to register any objections to this statement not later than Monday 17 March at 1200 UTC – after  it will be considered approved by the ALAC and transmitted to the Board by the Chair at her convenience. The statement may be found at the following URL in addition to being reproduced below: https://st.icann.org/naralo/index.cgi?statement_to_the_icann_board_on_domai… Statement one Domain Name Running Face Presented to NARALO by electronic Mail, 1 March 2008 Dear ICANN board directors: While we are aware that you have been monitoring the public outrage in response to registrar activities that have been variously described as "front-running" and/or "domain reservation" or "cart-hold" or "cart-reserve" activities, we are of the view that the obligation to safeguard the operational stability of Registrar Services now requires the immediate temporary establishment of a consensus policy curtailing such practices to be taken in accordance with the board's authority under the provisions set out in section 4.3.4 of the Registrar Accreditation Agreement, that states: "A specification or policy established by the ICANN Board of Directors on a temporary basis, without a prior recommendation by the council of an ICANN Supporting Organization, shall also be considered to be a Consensus Policy if adopted by the ICANN Board of Directors by a vote of at least two-thirds of its members, so long as the Board reasonably determines that immediate temporary establishment of a specification or policy on the subject is necessary to maintain the operational stability of Registrar Services, Registry Services, the DNS, or the Internet, and that the proposed specification or policy is as narrowly tailored as feasible to achieve those objectives." Please be advised that we have reached this conclusion based in part upon the following considerations: 1. The use of "cart-hold" or "cart-reserve" systems has been actively under discussion within the registrars constituency since early October 2007 when three different registrars first advanced the concept within the context of a straw poll on the impact to registrants were the AGP to be eliminated in its entirety (see footnote 1 at the bottom of the page) 2. The use of this domain name reservation practice next came to be adopted by a large-volume registrar (Network Solutions) on or about 8 January 2008, and the practice was immediately condemned by the community at large (with extensive coverage in the Tech media, the general press, in blogs world wide, on domain name forums, and on community discussion lists). 3. The actions of Network Solutions has now spawned a similar project on the part of another large-volume registrar (register.com) and we have no reason to believe that other large-volume registrars will refrain from rapidly setting up comparable efforts. (see Footnote 2). While we recognize that we are unable to point to an ICANN-approved definition of "operational stability of Registrar Services" (as no such definition exists within either current ICANN contracts or supporting materials), we take guidance from the ICANN Policy Document ICP-3 which posits that activities that do not interfere with the operation of the DNS are, generally speaking, those that operate within community-established norms. Such norms tend to respect a set of long-established principles such as the principle of least astonishment. When registrants currently search for a domain name at these registrars using normative search practices, they are clearly astonished by that which results from their efforts: the inability to readily register the domain name of their choice with a more competitive registrar and/or the domain name that they have selected appearing in the WHOIS with the name of the registrar as the registrant of record. (Footnote 3 The community's trust in ICANN's ability to manage the Domain Name System is at stake. It is inappropriate for such registrar activities to proceed unabated in a policy vaccuum. Accordingly we call upon the ICANN board to establish a temporary narrowly-tailored policy as a stopgap until such time as the relevant policy-recommending ICANN Supporting Organizations can provide a comprehensive consensus policy solution. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org -- B_3288271616_1181695 -- -------> [PORTUGUESE] TRADUCAO AUTOMATICA NAO REVISADA DO ORIGINAL > Esta mensagem está no formato do MIME. Desde que seu leitor do > correio não compreende > este formato, alguma ou tudo esta mensagem não podem ser legible. -- Índice-tipo B_3288271616_1181695: text/plain; charset="ISO-8859-1" quecodifica: cit-quoted-printable Caros Membros: A indicação reproduziu abaixo na prática sabida como a parte dianteira Running² do nome do ³Domain foi aprovada pelo NARALO em 10 março 2008. O ALAC reviu esta indicação em 11o março 2008, e pela decisão do ALAC você é pedido amavelmente para registar não mais tarde todas as objeções a esta indicação do que segunda-feira 17 março no 1200 do UTC depois que será considerado aprovado pelo ALAC e transmitido à placa pela cadeira em sua conveniência. A indicação pode ser encontrada no seguinte URL além a ser reproduzido abaixo: https://st.icann.org/naralo/index.cgi?statement_to_the_icann_board_on_domain _ que front_running Indicação no corredor dianteiro do Domain Name apresentado a NARALO pelo correio eletrônico, 1 março 2008 Caros diretores da placa de ICANN: Quando nós estivermos cientes que você tem monitorado o ultraje público em resposta às atividades do registrar que foram descritas vària como "dianteiro-funcionando" e/ou do "reservation domínio" ou atividades "carro-prenda" ou do "carro-reserva", nós somos da vista que a obrigação proteger a estabilidade operacional de serviços do registrar requer agora o estabelecimento provisório imediato de uma política do consenso que curtailing tais práticas ser feito exame de acordo com a autoridade da placa sob as provisões ajustadas para fora na seção 4.3.4 do acordo do accreditation do registrar, que indica: "uma especificação ou uma política estabelecida pela placa de ICANN de diretores em uma base provisória, sem uma recomendação prévia pelo conselho de uma organização suportando de ICANN, serão consideradas também ser uma política do consenso se adotado pela placa de ICANN de diretores por um voto ao menos de dois terços de seus membros, assim que long como a placa determina razoavelmente que o estabelecimento provisório imediato de uma especificação ou de uma política no assunto é necessário para manter a estabilidade operacional de serviços do registrar, de serviços do registro, do DNS, ou do Internet, e que a especificação ou a política proposta estão costuradas tão estreita quanto praticável para conseguir aqueles objetivos." Seja recomendado por favor que nós alcançamos esta conclusão baseada na parte nas seguintes considerações: 1. O uso "carro-prende" ou de sistemas da "carro-reserva" estêve ativamente sob a discussão dentro do círculo eleitoral dos registrars desde de outubro adiantado 2007 em que três registrars diferentes avançaram primeiramente o conceito dentro do contexto de uma votação da palha no impacto aos registrants eram os AGP a ser eliminados em sua totalidade (veja a nota de rodapé 1 no fundo da página) 2. O uso desta prática do reservation do Domain Name em seguida veio ser adotado por um registrar large-volume (soluções da rede) em ou aproximadamente por 8 janeiro 2008, e a prática condemned imediatamente pela comunidade em grande (com cobertura extensiva nos meios do tech, na imprensa geral, em largo de mundo dos blogs, em forums do Domain Name, e em listas da discussão da comunidade). 3. As ações de soluções da rede spawned agora um projeto similar na parte de um outro registrar large-volume (register.com) e nós não temos nenhuma razão acreditar que outros registrars large-volume refrain ràpidamente de ajustar acima esforços comparáveis (veja a nota de rodapé 2). Quando nós reconhecermos que nós somos incapazes de apontar a um ICANN-approveda definição "da estabilidade operacional do registrar presta serviços de manutenção" (porque nenhuma tal definição existe dentro dos contratos atuais de ICANN ou dos materiais suportando), nós faz exame da orientação do original ICP-3 da política de ICANN que posits que as atividades que não interferem com a operação do DNS seja, geralmente falando, aqueles que se operam dentro das normas comunidade-estabelecidas. Tais normas tendem a respeitar um jogo de princípios long-established tais como o princípio de menos astonishment. Quando os registrants procuraram atualmente por um Domain Name nestes registrars usando práticas normativas da busca, astonished claramente por aquele que resultados de seus esforços: a inabilidade registar prontamente o Domain Name de sua escolha com um registrar mais do competidor e/ou o Domain Name que selecionaram aparecer no WHOIS com o nome do registrar como o registrant do registro. (nota de rodapé 3 A confiança da comunidade na abilidade de ICANN's de controlar o Domain Name System está na estaca. É impróprio para tais atividades do registrar proseguir unabated em um vaccuum da política. Conformemente nós convidamos a placa de ICANN para estabelecer uma política estreito-costurada provisória como um stopgap até que hora como as organizações suportando política-recomendando relevantes de ICANN possa provide a comprehensive consensus policy solution. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org -- B_3288271616_1181695 Índice-tipo: text/html; charset="ISO-8859-1" quecodifica: cit-quoted-printable URGENTE: Statement on Domain Name Front Running Dear Members: Statement on Domain Name Front Running Apresentado a NARALO pelo correio eletrônico, 1 março 2008 Caros diretores da placa de ICANN: Quando nós estivermos cientes que você tem monitorado o ultraje público em resposta às atividades do registrar que foram descritas vària como "dianteiro-funcionando" e/ou do "reservation domínio" ou atividades "carro-prenda" ou do "carro-reserva", nós somos da vista que a obrigação proteger a estabilidade operacional de serviços do registrar requer agora o estabelecimento provisório imediato de uma política do consenso que curtailing tais práticas ser feito exame de acordo com a autoridade da placa sob as provisões ajustadas para fora na seção 4.3.4 do acordo do accreditation do registrar, que indica: "uma especificação ou uma política estabelecida pela placa de ICANN de diretores em uma base provisória, sem uma recomendação prévia pelo conselho de uma organização suportando de ICANN, serão consideradas também ser uma política do consenso se adotado pela placa de ICANN de diretores por um voto ao menos de dois terços de seus membros, assim que long como a placa determina razoavelmente que o estabelecimento provisório imediato de uma especificação ou de uma política no assunto é necessário para manter a estabilidade operacional de serviços do registrar, de serviços do registro, do DNS, ou do Internet, e que a especificação ou a política proposta estão costuradas tão estreita quanto praticável para conseguir aqueles objetivos." Seja recomendado por favor que nós alcançamos esta conclusão baseada na parte nas seguintes considerações: 1. O uso "carro-prende" ou de sistemas da "carro-reserva" estêve ativamente sob a discussão dentro do círculo eleitoral dos registrars desde de outubro adiantado 2007 em que três registrars diferentes avançaram primeiramente o conceito dentro do contexto de uma votação da palha no impacto aos registrants eram os AGP a ser eliminados em sua totalidade (veja a nota de rodapé 1 no fundo da página) 2. O uso desta prática do reservation do Domain Name em seguida veio ser adotado por um registrar large-volume (soluções da rede) em ou aproximadamente por 8 janeiro 2008, e a prática condemned imediatamente pela comunidade em grande (com cobertura extensiva nos meios do tech, na imprensa geral, em largo de mundo dos blogs, em forums do Domain Name, e em listas da discussão da comunidade). 3. As ações de soluções da rede spawned agora um projeto similar na parte de um outro registrar large-volume (register.com) e nós não temos nenhuma razão acreditar que outros registrars large-volume refrain ràpidamente de ajustar acima esforços comparáveis (veja a nota do pé 2). Quando nós reconhecermos que nós somos incapazes de apontar a uma definição de ICANN-approved de "a estabilidade operacional do registrar presta serviços de manutenção" (porque nenhuma tal definição existe dentro dos contratos atuais de ICANN ou dos materiais suportando), nós faz exame da orientação do original ICP-3 da política de ICANN que posits que as atividades que não interferem com a operação do DNS seja, geralmente falando, aqueles que se operam dentro das normas comunidade-estabelecidas. Tais normas tendem a respeitar um jogo de princípios long-established tais como o princípio de menos astonishment. Quando os registrants procuraram atualmente por um Domain Name nestes registrars usando práticas normativas da busca, astonished claramente por aquele que resultados de seus esforços: a inabilidade registar prontamente o Domain Name de sua escolha com um registrar mais do competidor e/ou o Domain Name que selecionaram aparecer no WHOIS com o nome do registrar como o registrant do ecord de r. (otnote 3 de Fo A confiança da comunidade na abilidade de ICANN's de controlar o Domain Name System está na estaca. É impróprio para tais atividades do registrar proseguir unabated em um vaccuum da política. Conformemente nós convidamos a placa de ICANN para estabelecer uma política estreito-costurada provisória como um stopgap até que hora como as organizações suportando política-recomendando relevantes de ICANN possa fornecer uma solução detalhada da política do consenso. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org </BODY> </HTML> --B_3288271616_1181695-- -------> [FRANCAIS] TRADUCTION AUTOMATIQUE NON REVISEE DE L'ORIGINAL > Ce message est dans le format de MIME. Puisque votre lecteur de > courrier ne comprend pas > ce format, un certain ou tous ce message peut ne pas être lisibles. -- Contenu-type B_3288271616_1181695 : text/plain ; charset="ISO-8859-1" Contenu-transférer-codant : citer-imprimable Chers Membres : Le rapport reproduit ci-dessous sur la pratique connue sous le nom d'avant Running² de nom de ³Domain a été approuvé par le NARALO 10 mars 2008. L'ALAC a passé en revue ce rapport le 11 mars 2008, et par la décision de l'ALAC vous êtes invité à enregistrer toutes les objections à ce rapport plus tard que lundi 17 mars au 1200 de UTC après qu'il soit considéré approuvé par l'ALAC et communiqué à le conseil par la chaise à sa convenance. Le rapport peut être trouvé au URL suivant en plus d'être reproduit ci-dessous : https://st.icann.org/naralo/index.cgi?statement_to_the_icann_board_on_domain _ front_running Rapport sur le fonctionnement avant de Domain Name présenté à NARALO par courrier électronique, 1 mars 2008 Chers directeurs de conseil d'ICANN : Tandis que nous nous rendons compte que vous ayez surveillé l'outrage public en réponse aux activités de conservateur qui ont été différemment décrites en tant que "avant-courant" et/ou "réservation de domaine" ou activités "chariot-tenez" ou de "chariot-réservation", nous sommes d'avis que l'obligation de sauvegarder la stabilité opérationnelle des services de conservateur exige maintenant l'établissement provisoire immédiat d'une politique de consensus raccourcissant de telles pratiques d'être pris selon l'autorité du conseil sous les dispositions présentées à la section 4.3.4 de l'accord d'accréditation de conservateur, qui énonce : "des spécifications ou une politique établie par le conseil d'administration d'ICANN sur une base provisoire, sans recommandation antérieure par le Conseil d'une organisation de support d'ICANN, seront également considérées comme une politique de consensus si adopté par le conseil d'administration d'ICANN par une voix au moins de deux-tiers de ses membres, à condition que le conseil détermine raisonnablement que l'établissement provisoire immédiat des spécifications ou d'une politique sur le sujet est nécessaire pour maintenir la stabilité opérationnelle des services de conservateur, des services d'enregistrement, du DNS, ou de l'Internet, et que les spécifications ou la politique proposées sont aussi étroitement travaillées que faisable pour atteindre ces objectifs." Soyez conseillé svp que nous avons tiré cette conclusion basée en partie sur les considérations suivantes : 1. L'utilisation "chariot-se tiennent" ou des systèmes d'"chariot-réservation" a été activement à l'étude chez le collège électoral de conservateurs depuis début octobre 2007 où trois conservateurs différents ont avancé la première fois le concept dans le contexte d'un scrutin de paille sur l'impact aux registrants étaient les AGP à éliminer en sa totalité (voir l'apostille 1 en bas de la page) 2. L'utilisation de cette pratique en matière de réservation de Domain Name après est venue pour être adoptée d'ici un conservateur de large volume (solutions de réseau) sur ou environ 8 janvier 2008, et la pratique a été immédiatement condamnée par la communauté dans son ensemble (avec l'assurance étendue dans les médias de technologie, la pression générale, dans les blogs dans le monde entier, sur des forum de Domain Name, et sur des listes de discussion de la communauté). 3. Les actions des solutions de réseau a maintenant engendré un projet semblable de la part d'un autre conservateur de large volume (register.com) et nous n'avons aucune raison de croire que d'autres conservateurs de large volume s'abstiendront à installer rapidement des efforts comparables (voir l'apostille 2). Tandis que nous identifions que nous ne pouvons pas se diriger à un ICANN-approvedla définition "de la stabilité opérationnelle du conservateur entretient" (car aucune une telle définition n'existe dans les contrats courants d'ICANN ou les matériels de support), nous prennent des conseils du document ICP-3 de politique d'ICANN qui pose en principe que les activités qui n'interfèrent pas l'opération du DNS soyez, d'une manière générale, ceux qui fonctionnent dans des normes communauté-établies. De telles normes tendent à respecter un ensemble de principes établis depuis longtemps tels que le principe de moindre étonnement. Quand les registrants recherchent actuellement un Domain Name à ces conservateurs en utilisant des pratiques en matière normatives de recherche, ils sont clairement étonnés par cela quels résultats de leurs efforts : l'incapacité d'enregistrer aisément le Domain Name de leur choix avec un conservateur plus concurrentiel et/ou le Domain Name qu'ils ont choisi apparaître dans le WHOIS avec le nom du conservateur en tant que registrant du disque. (apostille 3 La confiance de la communauté dans la capacité d'ICANN's de contrôler le Domain Name System est en jeu. Il est inadéquat que de telles activités de conservateur procèdent inchangé dans un vaccuum de politique. En conséquence nous invitons le conseil d'ICANN pour établir une politique étroit-travaillée provisoire comme bouche-trou jusqu'au moment où les organismes de support derecommandation appropriés d'ICANN peuvent provide à comprehensive consensus policy solution. -- Regards, ICANN At-Large le Personnel courrier électronique : staff(a)atlarge.icann.org -- B_3288271616_1181695 Contenu-type : text/html ; charset="ISO-8859-1" Contenu-transférer-codant : citer-imprimable <HTML> <HEAD> <TITLE>URGENT: Statement on Domain Name Front Running</TITLE> </HEAD> <BODY> Dear Members: Statement on Domain Name Front Running Présenté à NARALO par courrier électronique, 1 mars 2008 Chers directeurs de conseil d'ICANN : Tandis que nous nous rendons compte que vous ayez surveillé l'outrage public en réponse aux activités de conservateur qui ont été différemment décrites en tant que "avant-courant" et/ou "réservation de domaine" ou activités "chariot-tenez" ou de "chariot-réservation", nous sommes d'avis que l'obligation de sauvegarder la stabilité opérationnelle des services de conservateur exige maintenant l'établissement provisoire immédiat d'une politique de consensus raccourcissant de telles pratiques d'être pris selon l'autorité du conseil sous les dispositions présentées à la section 4.3.4 de l'accord d'accréditation de conservateur, qui énonce : "des spécifications ou une politique établie par le conseil d'administration d'ICANN sur une base provisoire, sans recommandation antérieure par le Conseil d'une organisation de support d'ICANN, seront également considérées comme une politique de consensus si adopté par le conseil d'administration d'ICANN par une voix au moins de deux-tiers de ses membres, à condition que le conseil détermine raisonnablement que l'établissement provisoire immédiat des spécifications ou d'une politique sur le sujet est nécessaire pour maintenir la stabilité opérationnelle des services de conservateur, des services d'enregistrement, du DNS, ou de l'Internet, et que les spécifications ou la politique proposées sont aussi étroitement travaillées que faisable pour atteindre ces objectifs." Soyez conseillé svp que nous avons tiré cette conclusion basée en partie sur les considérations suivantes : 1. L'utilisation "chariot-se tiennent" ou des systèmes d'"chariot-réservation" a été activement à l'étude chez le collège électoral de conservateurs depuis début octobre 2007 où trois conservateurs différents ont avancé la première fois le concept dans le contexte d'un scrutin de paille sur l'impact aux registrants étaient les AGP à éliminer en sa totalité (voir l'apostille 1 en bas de la page) 2. L'utilisation de cette pratique en matière de réservation de Domain Name après est venue pour être adoptée d'ici un conservateur de large volume (solutions de réseau) sur ou environ 8 janvier 2008, et la pratique a été immédiatement condamnée par la communauté dans son ensemble (avec l'assurance étendue dans les médias de technologie, la pression générale, dans les blogs dans le monde entier, sur des forum de Domain Name, et sur des listes de discussion de la communauté). 3. Les actions des solutions de réseau a maintenant engendré un projet semblable de la part d'un autre conservateur de large volume (register.com) et nous n'avons aucune raison de croire que d'autres conservateurs de large volume s'abstiendront à installer rapidement des efforts comparables (voir la note de pied 2). Tandis que nous identifions que nous ne pouvons pas se diriger à une définition d'ICANN-approved de "la stabilité opérationnelle du conservateur entretient" (car aucune une telle définition n'existe dans les contrats courants d'ICANN ou les matériels de support), nous prennent des conseils du document ICP-3 de politique d'ICANN qui pose en principe que les activités qui n'interfèrent pas l'opération du DNS soyez, d'une manière générale, ceux qui fonctionnent dans des normes communauté-établies. De telles normes tendent à respecter un ensemble de principes établis depuis longtemps tels que le principe de moindre étonnement. Quand les registrants recherchent actuellement un Domain Name à ces conservateurs en utilisant des pratiques en matière normatives de recherche, ils sont clairement étonnés par cela quels résultats de leurs efforts : l'incapacité d'enregistrer aisément le Domain Name de leur choix avec un conservateur plus concurrentiel et/ou le Domain Name qu'ils ont choisi apparaître dans le WHOIS avec le nom du conservateur en tant que registrant de l'ecord de r. (otnote 3 de Fo La confiance de la communauté dans la capacité d'ICANN's de contrôler le Domain Name System est en jeu. Il est inadéquat que de telles activités de conservateur procèdent inchangé dans un vaccuum de politique. En conséquence nous invitons le conseil d'ICANN pour établir une politique étroit-travaillée provisoire comme bouche-trou jusqu'au moment où les organismes de support derecommandation appropriés d'ICANN peuvent fournir une solution complète de politique de consensus. -- Regards, ICANN At-Large le Personnel courrier électronique : staff(a)atlarge.icann.org -- B_3288271616_1181695 -- Service d'aide à l'intercompréhension Vérifiez les règles pour un meilleur usage: http://funredes.org/tradauto/index.htm/regles Intercomprehension aid service Check the rules for better use: http://funredes.org/tradauto/index.htm/rules Serviço do dae de compreensão Verificar as réguas para o uso melhor: http://funredes.org/tradauto/index.htm/reguas Servicio de ayuda a la intercomprensión Leer las reglas para un mejor uso: http://funredes.org/tradauto/index.htm/reglas

1 0

URGENT: Statement on Domain Name Front Running
by At-Large Staff March 13, 2008

March 13, 2008

Dear Members: The statement reproduced below on the practice known as ³Domain Name Front Running² was approved by the NARALO on 10 March 2008. The ALAC reviewed this statement on 11th March 2008, and by decision of the ALAC you are kindly asked to register any objections to this statement not later than Monday 17 March at 1200 UTC after it will be considered approved by the ALAC and transmitted to the Board by the Chair at her convenience. The statement may be found at the following URL in addition to being reproduced below: https://st.icann.org/naralo/index.cgi?statement_to_the_icann_board_on_domain _front_running Statement on Domain Name Front Running Presented to NARALO by electronic Mail, 1 March 2008 Dear ICANN board directors: While we are aware that you have been monitoring the public outrage in response to registrar activities that have been variously described as "front-running" and/or "domain reservation" or "cart-hold" or "cart-reserve" activities, we are of the view that the obligation to safeguard the operational stability of Registrar Services now requires the immediate temporary establishment of a consensus policy curtailing such practices to be taken in accordance with the board's authority under the provisions set out in section 4.3.4 of the Registrar Accreditation Agreement, that states: "A specification or policy established by the ICANN Board of Directors on a temporary basis, without a prior recommendation by the council of an ICANN Supporting Organization, shall also be considered to be a Consensus Policy if adopted by the ICANN Board of Directors by a vote of at least two-thirds of its members, so long as the Board reasonably determines that immediate temporary establishment of a specification or policy on the subject is necessary to maintain the operational stability of Registrar Services, Registry Services, the DNS, or the Internet, and that the proposed specification or policy is as narrowly tailored as feasible to achieve those objectives." Please be advised that we have reached this conclusion based in part upon the following considerations: 1. The use of "cart-hold" or "cart-reserve" systems has been actively under discussion within the registrars constituency since early October 2007 when three different registrars first advanced the concept within the context of a straw poll on the impact to registrants were the AGP to be eliminated in its entirety (see footnote 1 at the bottom of the page) 2. The use of this domain name reservation practice next came to be adopted by a large-volume registrar (Network Solutions) on or about 8 January 2008, and the practice was immediately condemned by the community at large (with extensive coverage in the Tech media, the general press, in blogs world wide, on domain name forums, and on community discussion lists). 3. The actions of Network Solutions has now spawned a similar project on the part of another large-volume registrar (register.com) and we have no reason to believe that other large-volume registrars will refrain from rapidly setting up comparable efforts. (see Footnote 2). While we recognize that we are unable to point to an ICANN-approved definition of "operational stability of Registrar Services" (as no such definition exists within either current ICANN contracts or supporting materials), we take guidance from the ICANN Policy Document ICP-3 which posits that activities that do not interfere with the operation of the DNS are, generally speaking, those that operate within community-established norms. Such norms tend to respect a set of long-established principles such as the principle of least astonishment. When registrants currently search for a domain name at these registrars using normative search practices, they are clearly astonished by that which results from their efforts: the inability to readily register the domain name of their choice with a more competitive registrar and/or the domain name that they have selected appearing in the WHOIS with the name of the registrar as the registrant of record. (Footnote 3 The community's trust in ICANN's ability to manage the Domain Name System is at stake. It is inappropriate for such registrar activities to proceed unabated in a policy vaccuum. Accordingly we call upon the ICANN board to establish a temporary narrowly-tailored policy as a stopgap until such time as the relevant policy-recommending ICANN Supporting Organizations can provide a comprehensive consensus policy solution. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

Report on the OneDay AtLarge workshop
by At-Large Staff March 12, 2008

March 12, 2008

Dear all, Please find attached the Report on the ³OneDay ALAC/AtLarge² workshop that took place at the ICANN New Delhi conference. -- Regards, ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0