Automating DNSSEC Delegation Trust Maintenance
RFC 7344

Note: This ballot was opened for revision 13 and is now closed.

(Richard Barnes) Yes

Comment (2014-06-11)
No email
send info
I actually sort of agree with Pete that this would be better as PS.  But I don't care enough to block the document.

(Joel Jaeggli) Yes

(Jari Arkko) No Objection

Alissa Cooper No Objection

Comment (2014-06-10)
No email
send info
Section 1:
'This document is a compilation of two earlier drafts: draft-barwood-
   dnsop-ds-publish[I-D.ds-publish] and draft-wkumari-dnsop-ezkeyroll.'

Does draft-wkumari-dnsop-ezkeyroll exist or was that supposed to be a reference to draft-kumari-ogud-dnsop-cds? Either way, a citation is needed.

Section 2.2:
'After a Child DNS Operator first signs the zone, there is a need to
   interact with the Parent, for example via a delegation account
   interface, to "upload / paste-in the zone's DS information".' 

What is being quoted here?

(Spencer Dawkins) No Objection

(Adrian Farrel) No Objection

(Stephen Farrell) No Objection

Comment (2014-06-12)
No email
send info
You don't say (or I missed it while reading in a hurry;-) if
a child can have the new key be the same as the old key.
What happens if a child does that?

(Brian Haberman) No Objection

Barry Leiba (was Discuss) No Objection

Comment (2014-06-10)
No email
send info
Thanks for a very well written document, and for a good separation of normative and informative references.

Version -14 addresses my minor comments and clarifies the IANA considerations -- thanks.

(Ted Lemon) No Objection

Comment (2014-06-11)
No email
send info
I support Pete's DISCUSS.

(Kathleen Moriarty) No Objection

(Pete Resnick) (was Discuss) No Objection

(Martin Stiemerling) No Objection