This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] Updated DNS migration document
- Previous message (by thread): [dns-wg] Updated DNS migration document
- Next message (by thread): [dns-wg] .ORG DNSSEC Survey
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
García Fernández, Fernando
Fernando.Garcia at tecnocom.es
Mon Jun 9 15:05:02 CEST 2008
Hi Regarding the first point. (use of RFC3330 address), this was a doubt I had when creating the original document. But using only this range would introduce confusion in the document, because I would need to subnet it and the different address ranges would all look the same. So after speaking with other RIPE people we decided to use algo RFC 1918. I think it¹s use doesn¹t create any problem if examples are literally used and help the reader to understand the document. Regarding the other two points. I agree with them. If I can help in rewriting this elements (the examples and graphs, because my english is not so good), I¹ll be glad to do it. The corrections to the document look ok to me in a first sight. Regards, Fernando Garcia El 09/06/08 14:27, "Mohsen Souissi" <mohsen.souissi at nic.fr> escribió: > Jim, > > On 27 Apr, Jim Reid wrote: > | Here is the latest version of the DNS migration document. I've > | included the comments made by Joao and Jarle. > | Does anyone have anything else to add? > > ==> I know, it's quite late but I have just found time to review this > document. In case it's not too late, please find below my remarks and > suggestions. It's up to the authors to take all or part of it into > account. > > First, I have some general comments: > > 1) I would recommend to use RFC3330 addresses for example > IPv4 addresses. That's to say, within: 192.0.2/24 > > 2) It would be a good idea (and also helpful by the way for > administrators) to give examples of Name Servers supporting IPv6 > transport (numbering within 2001:db8::/32, RFC 3849) > > In that case, all illustrations with IPv4 addersses would be completed > by IPv6 addresses, when needed. > > 3) I think that it would be better to choose an NS list for > example.com zone, such that not all of them be inside the zone itself > > For example: > > example.com. IN NS master.example.com. > IN NS slave.example.net. > > and later "slave.example.org" (for the replacement). > > > Attached below are my comments and suggestions (with '^' for locating > the context and "==>" for my text). For readers only interested in the > "diffs" a diff file is als <<image.png>> o attached. > > Mohsen. > -- Fernando García Fernández Responsable de Dominios D.G. Telecomunicaciones, Redes y Sistemas Josefa Valcarcel, 26 Edificio Merrimack III Madrid - 28027 Tel. Fijo: (+34) 901900900 ext 40383 Fax: (+34) 914313240 Tel. Móvil: (+34) 649428591 E-mail: fernando.garcia at tecnocom.es http://www.tecnocom.es Por favor, antes de imprimir este mensaje, asegúrate de que es necesario. Ayudemos a cuidar el medio ambiente Confidencial. Para uso exclusivamente interno. Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente.Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.El correo electrónico vía Internet no permite asegurar la confidencialidad de los mensajes que se transmiten ni su integridad o correcta recepción. Tecnocom no asume ninguna responsabilidad por estas circunstancias. This message is intended exclusively for its addressee and may contain information that is CONFIDENTIAL and protected by a professional privilege or whose disclosure is prohibited by law. If you are not the intended recipient you are hereby notified that any read, dissemination, copy or disclosure of this communication is strictly prohibited by law. If this message has been received in error, please immediately notify us via e-mail and delete it.Internet e-mail neither guarantees the confidentiality nor the integrity or proper receipt of the messages sent. Tecnocom does not assume any liability for those circumstances. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/dns-wg/attachments/20080609/47a93bc9/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 5371 bytes Desc: image.png URL: </ripe/mail/archives/dns-wg/attachments/20080609/47a93bc9/attachment.png>
- Previous message (by thread): [dns-wg] Updated DNS migration document
- Next message (by thread): [dns-wg] .ORG DNSSEC Survey
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]