Skip to main content

Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)
draft-hollenbeck-epp-secdns-08

Yes

(David Kessens)
(Jon Peterson)

No Objection

(Alex Zinin)
(Bert Wijnen)
(Bill Fenner)
(Brian Carpenter)
(Margaret Cullen)
(Sam Hartman)

Recuse


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

Allison Mankin Former IESG member
Yes
Yes (2005-07-07) Unknown
David should add in the Protocol Quality section of the writeup that:

1. there was extensive review of the protocol choices and details of
    the spec on the dnsop mailing list though it was not a working group document
2. there is a full implementation by neustar, and it has been testbedded and
    demonstrated - a slideset on public demo can be referenced if you want
David Kessens Former IESG member
Yes
Yes () Unknown

                            
Jon Peterson Former IESG member
Yes
Yes () Unknown

                            
Alex Zinin Former IESG member
No Objection
No Objection () Unknown

                            
Bert Wijnen Former IESG member
No Objection
No Objection () Unknown

                            
Bill Fenner Former IESG member
No Objection
No Objection () Unknown

                            
Brian Carpenter Former IESG member
No Objection
No Objection () Unknown

                            
Margaret Cullen Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection (2005-06-30) Unknown
  Many references to RFC 4035 ought to be references to 4034.

  The public keys in the examples a very small!
Sam Hartman Former IESG member
No Objection
No Objection () Unknown

                            
Ted Hardie Former IESG member
No Objection
No Objection (2005-07-05) Unknown
The document requests a namespace assignment of: 

urn:ietf:params:xml:ns:secDNS-1.0

Would it make sense to consider urn:ietf:params:xml:ns:eppsecDNS-1.0
or something similar?  We may, after all, have multiple XML-based
protocols that deal with this stuff, and early disambiguation may help.
Obviously not a problem for real protocol processors (since any namespace
string is distinct to them), but it might help provide early clue to those
looking for DNSSec-related XML namespaces later.
Scott Hollenbeck Former IESG member
Recuse
Recuse (2005-06-30) Unknown
A comment on Russ' comment: the public keys are small because they've been truncated to fit page limits for display purposes.  That's described at the beginning of the document.