Re: [regext] review draft-ietf-regext-change-poll

I talked to Jim Gould about this feedback yesterday. We didn't reach a conclusion, so I'm throwing this to the list to see if anyone else cares and might have a preference for a change proposal. In Section 2.1 there's a description of the "custom" operation and how it uses an attribute named "o

Re: [regext] review draft-ietf-regext-change-poll

I like this, reading for the first time, this is what we need to notify the registrar when DNSSEC information is changed for a domain at the registry by the DNS Operator or the registry itself. Type: Create/Delete DNSSEC DS or DNSKEY Who: DNS Operator Name or the Registry itself. Reason: CDS o

Re: [regext] review draft-ietf-regext-change-poll

Scott, Thanks for the review and feedback. Below are my replies to the feedback prefixed with “JG-“. — JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com On 8/22/17, 7:05 AM, "regext on beha

Re: [regext] review draft-ietf-regext-change-poll

Jack, I’m glad that you see value in the use of draft-ietf-regext-change-poll. For a DNSSEC change of a domain, my recommendation is to leverage the domain mapping (domain info response) that would include the DNSSEC extension according to RFC 5910 and include the change poll extension with th