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/dns-wg@ripe.net/
[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 ]
Tony Finch
dot at dotat.at
Mon Oct 22 15:58:30 CEST 2018
Ondřej Caletka <Ondrej.Caletka at cesnet.cz> wrote: > - opt-in basis I would like to make this as light-weight as possible. There are already one or two levels of opt-in: uploading DS records to the RIPE database, and publishing CDS records (tho the latter is completely automatic with Knot DNS). > - no support for insecure to secure bootstrapping (RFC 8078) - if this > automatic management is opt-in, during opting in, the user should also > bootstrap the first DS That makes sense. > I personally pretty like the idea of special mntner, because it also > stresses the fact that actual object can be modified without of the > consent of the regular mntner. Yes, and it addresses Anand's comment that RIPE does not normally update users' objects. But I'm a bit worried that it might be too obscure. If it can't be eliminated entirely, perhaps it can be addressed by hints in the web user interface? Tony. -- f.anthony.n.finch <dot at dotat.at> http://dotat.at/ Tyne, Dogger: West 5 or 6, increasing 6 to gale 8. Moderate or rough, becoming very rough in northeast Dogger. Fair. Good.
- 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 ]