<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
hola creo ke se estan ekivocando con sus mails.... me han esatad mandando una informacion que desconosco y ke no me interesa:)<BR><BR>
<DIV>
<H1><FONT color=#0000ff size=5 face="Lucida Handwriting, Cursive"></FONT> </H1></DIV><BR><BR><BR>
<P><BR>> From: Joao@c-l-i.net<BR>> To: lacnog@lacnic.net<BR>> Date: Mon, 22 Mar 2010 18:03:06 -0700<BR>> Subject: Re: [lacnog] Signing of the ARPA zone<BR>> <BR>> no hay mucho que decir, la verdad.<BR>> La zona .arpa del DNS está ahora firmada con DNSSEC y se está <BR>> trabajando en limpiar la estructura de delegaciones en arpa para a <BR>> continuación firmar con DNSSEC las zonas contenidas en arpa (por <BR>> ejemplo in-addr.arpa, ip6.arpa, etc), e164.arpa ya está firmada desde <BR>> hace tiempo.<BR>> Ahora se pueden verificar las respuestas de DNS configurando la clave <BR>> para .arpa en su servidor de nombres y a partir de julio, cuando se <BR>> firme también la raíz del DNS (el dominio ".") se podrá seguir la <BR>> cadena de verificaciones desde ahí.<BR>> <BR>> Posteriormente imagino que los RIRs irán firmando sus zonas bajo in- <BR>> addr.arpa e ip6.arpa y asi hasta llegar hasta los usuarios del espacio <BR>> de direcciones que mantienen su propio DNS inverso<BR>> <BR>> Saludos<BR>> Joao<BR>> <BR>> On 22 Mar 2010, at 17:26, Nicolás Ruiz wrote:<BR>> <BR>> > Podría alguien más familiarizado con todo este proceso comentar un <BR>> > poco sobre esto? Yo en particular estoy bien crudo, pero no sé por <BR>> > donde comenzar.<BR>> ><BR>> > nicolás<BR>> ><BR>> > Joe Abley wrote:<BR>> >> Colleagues,<BR>> >> This is a follow-up to the operational announcement regarding <BR>> >> changes to the ARPA top-level domain that was sent on 2010-03-10. <BR>> >> Apologies in advance for duplicates received through different <BR>> >> mailing lists.<BR>> >> As of 2010-03-17 1630 UTC all the authoritative servers for ARPA <BR>> >> are serving a signed ARPA zone.<BR>> >> We would like to solicit feedback from the technical community to <BR>> >> allow us to identify any operational ill-effects that this change <BR>> >> has caused. We will monitor this mailing list for feedback, and I <BR>> >> will also distribute any feedback sent to me personally so that it <BR>> >> can be considered.<BR>> >> If no harmful effects have been identified by 2010-03-21 the trust <BR>> >> anchor for the ARPA zone will be published through the IANA ITAR at <BR>> >> <https://itar.iana.org/>.<BR>> >> Regards,<BR>> >> Joe<BR>> >> Begin forwarded message:<BR>> >>> From: Joe Abley <joe.abley@icann.org><BR>> >>> Date: 10 March 2010 16:13:46 EST<BR>> >>> To: Joe Abley <joe.abley@icann.org><BR>> >>> Subject: Signing of the ARPA zone<BR>> >>><BR>> >>> Colleagues,<BR>> >>><BR>> >>> This is a technical, operational announcement regarding changes to <BR>> >>> the ARPA top-level domain. Apologies in advance for duplicates <BR>> >>> received through different mailing lists.<BR>> >>><BR>> >>> No specific action is requested of operators. This message is for <BR>> >>> your information only.<BR>> >>><BR>> >>> The ARPA zone is about to be signed using DNSSEC. The technical <BR>> >>> parameters by which ARPA will be signed are as follows:<BR>> >>><BR>> >>> KSK Algorithm and Size: 2048 bit RSA<BR>> >>> KSK Rollover: every 2-5 years, scheduled rollover to follow RFC 5011<BR>> >>> KSK Signature Algorithm: SHA-256<BR>> >>> Validity period for signatures made with KSK: 15 days; new <BR>> >>> signatures published every 10 days<BR>> >>> ZSK Algorithm and Size: 1024 bit RSA<BR>> >>> ZSK Rollover: every 3 months<BR>> >>> ZSK Signature Algorithm: SHA-256<BR>> >>> Authenticated proof of non-existence: NSEC<BR>> >>> Validity period for signatures made with ZSK: 7 days; zone <BR>> >>> generated and re-signed twice per day<BR>> >>><BR>> >>> The twelve root server operators [1] will begin to serve a signed <BR>> >>> ARPA zone instead of the (current) unsigned ARPA zone during a <BR>> >>> maintenance window which will open at 2010-03-15 0001 UTC and <BR>> >>> close at 2010-03-17 2359 UTC. Individual root server operators <BR>> >>> will carry out their maintenance at times within that window <BR>> >>> according to their own operational preference.<BR>> >>><BR>> >>> The trust anchor for the ARPA zone will be published in the ITAR <BR>> >>> [2], and in the root zone in the form of a DS record once the root <BR>> >>> zone is signed.<BR>> >>><BR>> >>> If you have any concerns or require further information, please <BR>> >>> let me know.<BR>> >>><BR>> >>> Regards,<BR>> >>><BR>> >>><BR>> >>> Joe Abley<BR>> >>> Director DNS Operations, ICANN<BR>> >>><BR>> >>> [1] <http://www.root-servers.org/><BR>> >>> [2] <https://itar.iana.org/><BR>> >> _______________________________________________<BR>> >> LACNOG mailing list<BR>> >> LACNOG@lacnic.net<BR>> >> https://mail.lacnic.net/mailman/listinfo/lacnog<BR>> ><BR>> > _______________________________________________<BR>> > LACNOG mailing list<BR>> > LACNOG@lacnic.net<BR>> > https://mail.lacnic.net/mailman/listinfo/lacnog<BR>> <BR>> _______________________________________________<BR>> LACNOG mailing list<BR>> LACNOG@lacnic.net<BR>> https://mail.lacnic.net/mailman/listinfo/lacnog<BR> <br /><hr />¿Te falta espacio para tus correos? <a href='www.hotmailhotness.com.mx' target='_new'>Enciende tu hotness con Hotmail</a></body>
</html>