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] Tweaks to RIPE 663: Secondary DNS Service for ccTLD Operators
- Previous message (by thread): [dns-wg] DNS Privacy
- Next message (by thread): [dns-wg] Tweaks to RIPE 663: Secondary DNS Service for ccTLD Operators
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Thu May 26 14:33:58 CEST 2016
Hello, Anand just mentioned at his presentation at RIPE 72 that the RIPE NCC is now implementing RIPE 663: https://www.ripe.net/publications/docs/ripe-663 There were a couple of suggestions for tweaks to that: 1. Gaurab and I think that there should be an exemption for ccTLD who do not currently have IPv6 service. (There are a few tens of ccTLD who do not yet have IPV6, and I would like the RIPE NCC to be able to help them get IPv6 service if they want it.) 2. Gaurab mentioned that there are some ccTLD who have 3 servers but they are all in the same network. The document should be flexible in order to insure network diversity. I know the document is less than 6 months old and just being implemented now, but maybe we can revise it to include these two changes? I'm happy to do a quick pass at text for this if that makes sense. Cheers, -- Shane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/dns-wg/attachments/20160526/0c01003e/attachment.sig>
- Previous message (by thread): [dns-wg] DNS Privacy
- Next message (by thread): [dns-wg] Tweaks to RIPE 663: Secondary DNS Service for ccTLD Operators
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]