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] RFC 7344 support in the RIPE database
- Previous message (by thread): [dns-wg] RFC 7344 support in the RIPE database
- Next message (by thread): [dns-wg] RFC 7344 support in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Mon Nov 26 15:04:32 CET 2018
Tony, On 14/11/2018 12.39, Tony Finch wrote: > OK, now we have got the ICANN and IETF meetings out of the way, what are > the next steps to make progress on this? Do we need a formal proposal and > if so is there an example I can clone and hack? Thank you for pushing this forward! I can't think of any examples of such a request exactly, but I am happy to be corrected. Generally we leave the details of exactly how stuff works up to the RIPE NCC, and I think that makes sense for any request about RFC 7344 support. My own thinking is that we can request update & deletion support immediately, since those are clearly specified, but that we need to think a bit about what recommendations we can make for bootstrapping adding DS records, if we want that at all (I think we do, but reasonable people may disagree). Perhaps the RIPE NCC can use RIPE Atlas to get a widely distributed view of a given domain to ensure that any new CDS records are the same across the entire delegation, and if those stay stable for a while (72 hours? a week?) then create a new DS record? Cheers, -- Shane
- Previous message (by thread): [dns-wg] RFC 7344 support in the RIPE database
- Next message (by thread): [dns-wg] RFC 7344 support in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]