From joe.abley at icann.org Mon May 3 09:17:51 2010 From: joe.abley at icann.org (Joe Abley) Date: Mon, 3 May 2010 05:17:51 -0700 Subject: [lacnog] Root Zone DNSSEC Deployment Technical Status Update Message-ID: <1F034EBC-F37F-4ACC-9B42-F75F3498C125@icann.org> Root Zone DNSSEC Deployment Technical Status Update 2010-05-03 This is the fifth of a series of technical status updates intended to inform a technical audience on progress in signing the root zone of the DNS. ** The final transition to the DURZ will take place on ** J-Root, on 2010-05-05 between 1700--1900 UTC. ** ** After that maintenance all root servers will be serving the ** DURZ, and will generate larger responses to DNS ** queries that request DNSSEC information. ** ** If you experience technical problems or need to contact ** technical project staff, please send e-mail to rootsign at icann.org ** or call the ICANN DNS NOC at +1 310 301 5817, e-mail preferred ** if possible. ** ** See below for more details. RESOURCES Details of the project, including documentation published to date, can be found at . We'd like to hear from you. If you have feedback for us, please send it to rootsign at icann.org. DEPLOYMENT STATUS The incremental deployment of DNSSEC in the Root Zone is being carried out first by serving a Deliberately Unvalidatable Root Zone (DURZ), and subsequently by a conventionally signed root zone. Discussion of the approach can be found in the document "DNSSEC Deployment for the Root Zone", as well as in the technical presentations delivered at RIPE, NANOG, IETF and ICANN meetings. Twelve of the thirteen root servers have already made the transition to the DURZ. No harmful effects have been identified. The final root server to make the transition, J-Root, will start serving the DURZ in a maintenance window scheduled for 1700--1900 UTC on 2010-05-05. Initial observations relating to this transition will be presented and discussed at the DNS Working Group meeting at the RIPE meeting in Prague on 2010-05-06. PLANNED DEPLOYMENT SCHEDULE Already completed: 2010-01-27: L starts to serve DURZ 2010-02-10: A starts to serve DURZ 2010-03-03: M, I start to serve DURZ 2010-03-24: D, K, E start to serve DURZ 2010-04-14: B, H, C, G, F start to serve DURZ To come: 2010-05-05: J starts to serve DURZ 2010-07-01: Distribution of validatable, production, signed root zone; publication of root zone trust anchor (Please note that this schedule is tentative and subject to change based on testing results or other unforeseen factors.) A more detailed DURZ transition timetable with maintenance windows can be found in the document "DNSSEC Deployment for the Root Zone", the most recent draft of which can be found on the project web page at . From ernesto at lacnic.net Tue May 4 19:20:56 2010 From: ernesto at lacnic.net (=?iso-8859-1?Q?Ernesto_Maj=F3?=) Date: Tue, 4 May 2010 19:20:56 -0300 Subject: [lacnog] =?iso-8859-1?q?INFORMACION_IMPORTANTE_/_INFORMA=C7=C3O_I?= =?iso-8859-1?q?MPORTANTE_/_RELEVANT_INFORMATION?= Message-ID: <5F54E03A-6913-4B21-9B06-4285C6B2F842@lacnic.net> Portugu?s a continua??o] [English will follow] ----------------------------------------- INFORMACI?N IMPORTANTE El pr?ximo d?a 5 de mayo entre las 17:00 - 19:00 UTC el servidor ra?z de DNS J comenzar? a servir una "Deliberately Unvalidatable Root Zone (DURZ)" como parte del proceso de la implementaci?n de DNSSEC en la zona ra?z. Este es el ?ltimo de los servidores ra?z del DNS en hacer la transici?n y al igual que con las cambios anteriores no se esperan efectos negativos al realizarse esta migraci?n. Como parte del proceso de migraci?n a DNSSEC, los paquetes de DNS transmitidos sobre UDP podr?an ya no ser menores a 512 bytes como tradicionalmente se manejaba en la zona ra?z. En caso de que el mensaje sea rechazado, es posible que el servidor reintente la petici?n usando TCP en lugar de UDP. Este cambio en el tama?o de los paquetes transmitidos por el sistema de DNS y el uso de TCP puede ocasionar problemas con algunos equipos de red como firewalls y enrutadores o incluso con algunas versiones antiguas de servidores recursivos (resolvers) de DNS. Para verificar la correcta operaci?n de los "resolvers", incluyendo la red sobre la que est?n y si estos tienen alg?n problema con la respuesta aceptada por los servidores de DNS, los ISPs y operadores de redes tienen al alcance un par de herramientas: https://www.dns-oarc.net/oarc/services/replysizetest http://labs.ripe.net/content/testing-your-resolver-dns-reply-size-issues Para m?s informaci?n relacionada con la versiones de software de DNS recursivo que soportan la Deliberately-Unvalidatable Root Zone (DURZ): http://www.root-dnssec.org/wp-content/uploads/2010/03/draft-icann-dnssec-resolver-testing-00.txt ---------------------------------------- INFORMA??O IMPORTANTE Na pr?xima quarta-feira 5 de maio das 17:00 ?s 19:00 UTC o servidor ra?z do DNS J vai come?ar servir uma "Deliberately Unvalidatable Root Zone (DURZ)" como parte do processo da implementa??o do DNSSEC na zona ra?z. Este ? o ?ltimo dos servidores ra?z do DNS em fazer a transi??o e da mesma forma que com as mudan?as anteriores n?o est?o sendo esperados efeitos negativos quando for realizada essa migra??o. Como parte do processo de migra??o para DNSSEC, os pacotes de DNS transmitidos sobre UDP poderiam j? n?o ser menores que 512 bytes como tradicionalmente na zona ra?z. Se a mensagem for rejeitada, ? poss?vel que o servidor reintente o pedido usando TCP no lugar de UDP. Essa mudan?a no tamanho dos pacotes transmitidos pelo sistema de DNS e o uso de TCP pode provocar problemas em alguns equipamentos de rede como firewalls e routers ou inclusive em algumas vers?es antigas de servidores recursivos (resolvers) de DNS. Para verificar a opera??o correta dos ?resolvers?, incluindo a rede sobre a que est?o, e no caso desses tiverem algum problema com a resposta aceita pelos servidores de DNS, os ISPs e operadores de redes ter?o dispon?veis duas ferramentas: https://www.dns-oarc.net/oarc/services/replysizetest http://labs.ripe.net/content/testing-your-resolver-dns-reply-size-issues Para mais informa??es relativas ?s vers?es de software de DNS recursivo que sustentam a Deliberately-Unvalidatable Root Zone (DURZ) acesse: http://www.root-dnssec.org/wp-content/uploads/2010/03/draft-icann-dnssec-resolver-testing-00.txt ------------------------------------- RELEVANT INFORMATION On May 5, between 17:00 and 19:00 UTC, as part of the process for the implementation of DNSSEC in the root zone, the ?J? DNS root server will begin serving a "Deliberately Unvalidatable Root Zone (DURZ)". This is the last of the DNS root servers to make the transition and, as with previous changes, it is anticipated that the migration will not have any negative effects. As part of the process for migrating to DNSSEC, DNS packets transmitted over UDP may now be larger than 512 bytes (traditionally, in the case in the root zone, packets were limited to 512 bytes). If a message is rejected, the server may attempt to comply with the request once again using TCP instead of UDP. This change in the size of the packets transmitted by the DNS system and the use of TCP may cause problems with some network equipment, such as firewalls and routers, or even with some older version of DNS recursive servers (resolvers). In order to test the proper operation of the resolvers, including the network on which they are installed, to check whether they have any DNS reply size issues, a couple of tools are available to ISPs and network operators: https://www.dns-oarc.net/oarc/services/replysizetest http://labs.ripe.net/content/testing-your-resolver-dns-reply-size-issues For further information on which recursive DNS software versions support the Deliberately-Unvalidatable Root Zone (DURZ): http://www.root-dnssec.org/wp-content/uploads/2010/03/draft-icann-dnssec-resolver-testing-00.txt -------------- next part -------------- An HTML attachment was scrubbed... URL: From joe.abley at icann.org Wed May 5 18:23:09 2010 From: joe.abley at icann.org (Joe Abley) Date: Wed, 5 May 2010 14:23:09 -0700 Subject: [lacnog] Root Zone DNSSEC Deployment Technical Status Update Message-ID: Root Zone DNSSEC Deployment Technical Status Update 2010-05-05 This is the sixth of a series of technical status updates intended to inform a technical audience on progress in signing the root zone of the DNS. ** The final transition to a signed root zone took place today ** on J-Root, between 1700--1900 UTC. ** ** All root servers are now serving a signed root zone. ** ** All root servers will now generate larger responses to DNS ** queries that request DNSSEC information. ** ** If you experience technical problems or need to contact ** technical project staff, please send e-mail to rootsign at icann.org ** or call the ICANN DNS NOC at +1 310 301 5817, e-mail preferred ** if possible. ** ** See below for more details. RESOURCES Details of the project, including documentation published to date, can be found at . We'd like to hear from you. If you have feedback for us, please send it to rootsign at icann.org. DEPLOYMENT STATUS The incremental deployment of DNSSEC in the Root Zone is being carried out first by serving a Deliberately Unvalidatable Root Zone (DURZ), and subsequently by a conventionally signed root zone. Discussion of the approach can be found in the document "DNSSEC Deployment for the Root Zone", as well as in the technical presentations delivered at RIPE, NANOG, IETF and ICANN meetings. All of the thirteen root servers have now made the transition to the to the DURZ. No harmful effects have been identified. The final root server to make the transition, J-Root, started serving the DURZ in a maintenance window between 1700--1900 UTC on 2010-05-05. Initial observations relating to this transition will be presented and discussed at the DNS Working Group meeting at RIPE 60 in Prague on 2010-05-06. PLANNED DEPLOYMENT SCHEDULE Already completed: 2010-01-27: L starts to serve DURZ 2010-02-10: A starts to serve DURZ 2010-03-03: M, I start to serve DURZ 2010-03-24: D, K, E start to serve DURZ 2010-04-14: B, H, C, G, F start to serve DURZ 2010-05-05: J starts to serve DURZ To come: 2010-07-01: Distribution of validatable, production, signed root zone; publication of root zone trust anchor (Please note that this schedule is tentative and subject to change based on testing results or other unforeseen factors.) From joe.abley at icann.org Tue May 18 14:12:22 2010 From: joe.abley at icann.org (Joe Abley) Date: Tue, 18 May 2010 10:12:22 -0700 Subject: [lacnog] Root Zone DNSSEC Deployment Technical Status Update Message-ID: <98E9A48B-154D-4589-B8C7-C193B16C4CF1@icann.org> Root Zone DNSSEC Deployment Technical Status Update 2010-05-17 This is the seventh of a series of technical status updates intended to inform a technical audience on progress in signing the root zone of the DNS. CHANGE IN DEPLOYMENT SCHEDULE The date for the publication of the root zone trust anchor and the distribution of a validatable, signed root zone originally planned for 2010-07-01 has been changed. This final stage of root DNSSEC deployment is now scheduled to take place on 2010-07-15. The schedule change is intended to allow ICANN and VeriSign an additional two weeks for further analysis of the DURZ rollout, to finalise testing and best ensure the secure, stable and resilient implementation of the root DNSSEC production processes and systems. Prior to 2010-07-15 the U.S. Department of Commerce (DoC) will issue a public notice announcing the publication of the joint ICANN-VeriSign testing and evaluation report as well as the intent to proceed with the final stage of DNSSEC deployment. As part of this notice the DoC will include a public review and comment period prior to taking any action. This change has been reflected in the deployment plan and other documentation, and updated documents will be published at . PLANNED DEPLOYMENT SCHEDULE Already completed: 2010-01-27: L starts to serve DURZ 2010-02-10: A starts to serve DURZ 2010-03-03: M, I start to serve DURZ 2010-03-24: D, K, E start to serve DURZ 2010-04-14: B, H, C, G, F start to serve DURZ 2010-05-05: J starts to serve DURZ To come: 2010-06-16: First Key Signing Key (KSK) Ceremony 2010-07-15: Distribution of validatable, production, signed root zone; publication of root zone trust anchor (Please note that this schedule is tentative and subject to change based on testing results or other unforeseen factors.) From mehmet at akcin.net Tue May 18 15:02:46 2010 From: mehmet at akcin.net (Mehmet Akcin) Date: Tue, 18 May 2010 11:02:46 -0700 Subject: [lacnog] GSM Provider Curacao Message-ID: <6CA0A5BA-D77E-4D57-B035-A8F3D657B3E3@akcin.net> anyone from GSM Provider in Curacao "ANT CURACAGO TELECOM GSM" is on this list? can you find me if you are on site in LACNIC meeting? or email me offlist. there is a problem with GSM provided time. Mehmet From francisco at arias.com.mx Tue May 18 15:46:49 2010 From: francisco at arias.com.mx (Francisco Arias) Date: Tue, 18 May 2010 14:46:49 -0400 Subject: [lacnog] GSM Provider Curacao In-Reply-To: <6CA0A5BA-D77E-4D57-B035-A8F3D657B3E3@akcin.net> References: <6CA0A5BA-D77E-4D57-B035-A8F3D657B3E3@akcin.net> Message-ID: Try "Eldert Louisa" Regards, Francisco. On 18 May 2010 14:02, Mehmet Akcin wrote: > anyone from GSM Provider in Curacao "ANT CURACAGO TELECOM GSM" ?is on this list? can you find me if you are on site in LACNIC meeting? or email me offlist. > > there is a problem with GSM provided time. > > Mehmet > _______________________________________________ > LACNOG mailing list > LACNOG at lacnic.net > https://mail.lacnic.net/mailman/listinfo/lacnog > From francisco at arias.com.mx Tue May 18 15:46:49 2010 From: francisco at arias.com.mx (Francisco Arias) Date: Tue, 18 May 2010 14:46:49 -0400 Subject: [lacnog] GSM Provider Curacao In-Reply-To: <6CA0A5BA-D77E-4D57-B035-A8F3D657B3E3@akcin.net> References: <6CA0A5BA-D77E-4D57-B035-A8F3D657B3E3@akcin.net> Message-ID: Try "Eldert Louisa" Regards, Francisco. On 18 May 2010 14:02, Mehmet Akcin wrote: > anyone from GSM Provider in Curacao "ANT CURACAGO TELECOM GSM" ?is on this list? can you find me if you are on site in LACNIC meeting? or email me offlist. > > there is a problem with GSM provided time. > > Mehmet > _______________________________________________ > LACNOG mailing list > LACNOG at lacnic.net > https://mail.lacnic.net/mailman/listinfo/lacnog > From aservin at lacnic.net Wed May 19 11:10:22 2010 From: aservin at lacnic.net (Arturo Servin) Date: Wed, 19 May 2010 10:10:22 -0400 Subject: [lacnog] =?iso-8859-1?q?Fwd=3A_=5BLACNIC/Anuncios=5D_+Raices=3A_A?= =?iso-8859-1?q?cuerdo_para_instalaci=F3n_de_copia_de_Servidor_Ra=EDz_F_en?= =?iso-8859-1?q?_HAITI?= References: <49522.190.4.176.38.1274277643.squirrel@webmail.lacnic.net.uy> Message-ID: <17170738-7B13-4539-8262-DB4A40B672DC@lacnic.net> Un importante anuncio. An important announcement. Saludos/Regards, -as Begin forwarded message: > From: alexandra at lacnic.net > Date: 19 May 2010 10:00:43 EDT > To: anuncios at lacnic.net > Subject: [LACNIC/Anuncios] +Raices: Acuerdo para instalaci?n de copia de Servidor Ra?z F en HAITI > > Curazao, Mayo de 2010.- > > Continuando con el esfuerzo para el desarrollo y estabilidad de Internet > en Am?rica Latina y el Caribe, LACNIC conjuntamente con la Asociaci?n > Haitiana para el Desarrollo de Tecnolog?as de la Informaci?n y > Comunicaci?n (AHTIC) realizaron hoy la firma del Acuerdo que permitir? > instalar en Haiti una copia anycast de un Servidor Ra?z. > > Este importante hecho se realiz? durante la reuni?n anual de LACNIC XIII > que en estos momentos se est? llevando a cabo en Curazao, donde Ra?l > Echeberr?a, Director Ejecutivo de LACNIC, Paul Vixie, Presidente de ISC y > Max Larson Henry en representaci?n de AHTIC, procedieron a firmar el > acuerdo. > > Como en el caso de otros seis pa?ses de la regi?n a trav?s del proyecto > +Ra?ces, LACNIC (Registro de Direcciones IP para Am?rica Latina y el > Caribe), ISC (Internet System Consortium) y AHTIC instalar?n > para la regi?n una copia del Servidor Ra?z F en Haiti. > > El Proyecto +Raices es una iniciativa de LACNIC que conjuntamente con ISC > promueve la instalaci?n de copias del Servidor F en Am?rica Latina y el > Caribe. A la fecha ya han sido instaladas copias en Chile, Argentina, > Venezuela, Panam?, Ecuador y Sint Maarten significando una notable mejora > en el acceso directo a la red por parte de usuarios y proveedores de > servicios de Internet de esos pa?ses y una contribuci?n relevante a la > estabilidad de Internet en toda la regi?n y a nivel global. > > Este proyecto es un ejemplo de los modelos de cooperaci?n > multistakeholder promovidos por la Cumbre Mundial de la Sociedad de la > Informaci?n, donde organismos gubernamentales y privados pueden trabajar > juntos en beneficio de la estabilidad y el crecimiento de Internet en la > regi?n, con los cuales LACNIC se encuentra fuertemente comprometido. > > El sistema de nombres de dominio consiste en millones de servidores > interconectados entre s?, de los cuales los llamados servidores ra?z son > los que poseen la informaci?n que da inicio a las consultas a este > sistema. Una limitante t?cnica no permite que ?stos sean m?s de 13, los > cuales se identifican con letras de la A a la M. De estos 13 servidores > ra?z originales, diez estaban ubicados en Estados Unidos, dos en Europa y > uno en Jap?n, lo cual generaba bastante preocupaci?n respecto del peque?o > n?mero de servidores y de su concentraci?n geogr?fica. > > Para resolver este problema, desde hace pocos a?os se ha empezado a usar > una t?cnica llamada anycast, que permite crear clones de estos > servidores ra?z (llamados espejos), los cuales una vez en operaci?n son > indistinguibles de los originales. Esto agrega mayor eficiencia en el > sistema y al mismo tiempo mayor seguridad y estabilidad. Es a trav?s de > esta tecnolog?a anycast que se realizan las instalaciones de servidores > ra?z en el marco del proyecto +Raices > > Como se recordar?, el Registro de Direcciones de Internet para Am?rica > Latina y el Caribe (LACNIC), es la organizaci?n internacional, con sede > en Montevideo, que administra el espacio de direcciones IP, N?meros de > Sistemas Aut?nomos (ASN), Resoluci?n Inversa y otros recursos para la > regi?n de Am?rica Latina y el Caribe (LAC) en nombre de la comunidad > Internet. > > > > > > > > > _______________________________________________ > Anuncios mailing list > Anuncios at lacnic.net > https://mail.lacnic.net/mailman/listinfo/anuncios Arturo L. Servin Niembro Gerente Area T?cnica Tel.: +598 2 6042222 Fax: +598 2 6042222 ext. 112 Rambla Rep. de M?xico 6125 - C.P. 11400 Montevideo, Uruguay aservin _ at _ lacnic.net http://www.lacnic.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From aservin at lacnic.net Fri May 21 16:37:49 2010 From: aservin at lacnic.net (aservin at lacnic.net) Date: Fri, 21 May 2010 16:37:49 -0300 (UYT) Subject: [lacnog] Recursos RPKI HE / RPKI resources RPKI Message-ID: <50333.206.107.224.162.1274470669.squirrel@webmail.lacnic.net.uy> Hola, Les env?o un site con algunos recursos de RPKI de Hurricane Electric. En el sitio pueden ver los ROAs de los bloques de IP. Por lo pronto HE a?n no est? obteniendo certificados de de LACNIC pero estaremos trabajando en ello en las pr?ximas semanas. El sitio tambi?n tiene algunos recursos interesantes como presentaciones (http://rpki.he.net/rpki_presentations.html) y los drafts que se est?n desarrollando en el IETF (http://rpki.he.net/ietf_drafts.html) Tambi?n este es el link con las herramientas de visualizaci?n de rutas y ASs: http://bgp.he.net/ Saludos, -asn Hello, I am sending you some interesting resources about RPKI from Hurricane Electric. In the website you can see the IP addresses ROAs. For now HE is not pulling certificates from LACNIC but we will work on it in the next few weeks. The website also has some interesting resources such as presentations (http://rpki.he.net/rpki_presentations.html) and the IETF drafts that has been discussed (http://rpki.he.net/ietf_drafts.html) Also this is the link with the visualisation tools for ASs and routes. http://bgp.he.net/ Regards, -als Arturo L. Servin Chief Technical Officer | LACNIC Tel.: +598 2 6042222 | Fax: +598 2 6042222 ext. 112 Rambla Rep. de M?xico 6125 - C.P. 11400 | Montevideo, Uruguay http://www.lacnic.net From rs-lists at seastrom.com Sat May 29 20:52:08 2010 From: rs-lists at seastrom.com (Robert Seastrom) Date: Sat, 29 May 2010 19:52:08 -0400 Subject: [lacnog] Postel Network Operator's Scholarship Application Deadline June 1st Message-ID: <3040661A-38F4-42DA-8169-738E54DD3C5F@seastrom.com> [Sent to multiple lists; apologies for the duplicates] On behalf of the North American Network Operators' Group (NANOG) and the American Registry for Internet Numbers (ARIN), I would like to remind all interested individuals that the deadline for application for the 2010 Postel Network Operator's Scholarship is June 1st. For more information please see http://www.nanog.org/scholarships/postel.php Kind regards, -Rob Seastrom, on behalf of the Postel Scholarship Selection Committee.