On 2/16/16 7:09 AM, Jacques Latour wrote: > Hi, > > I think it would fall under REGEXT once it's up? The REGEXT charter has a > section about DNS Operator. > >> The working group will also identify the requirements for a >> registration protocol where a third-party DNS provider is involved. >> These requirements will be documented in an Informational RFC.
based on on current progress I would expect regext to exist prior to or by IETF 92. > Jack > > >> -----Original Message----- >> From: DNSOP [mailto:dnsop-boun...@ietf.org] On Behalf Of John Levine >> Sent: February-13-16 4:45 PM >> To: dnsop@ietf.org >> Subject: [DNSOP] Any interest in draft-latour-dnsoperator-to-rrr-protocol ? >> >> I noticed the -02 of this draft go by yesterday. >> >> It's a very rough version of a DNSSEC key record bootstrap design in which >> the >> operator of the delegated zone pokes the operator of the upper level zone >> using http, which tells the upper level zone to import keys from the >> delegated >> zone's CDS and CDNSKEY records. >> >> Is there much interest in this? >> >> On my tiny DNS server I have over 100 signed zones where I can't install the >> upper level DS records because I'm not the registrant, I'm just running their >> DNS. It would be nice to have a way to do that that scales better than >> walking each of the registrants through their registrars' DNSSEC update >> processes. >> >> R's, >> John >> >> _______________________________________________ >> DNSOP mailing list >> DNSOP@ietf.org >> https://www.ietf.org/mailman/listinfo/dnsop > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
