Summary: Has a DISCUSS. Has enough positions to pass once DISCUSS positions are resolved.
I’m not certain about the intended status of this document. I understand that this was discussed in the group but this document does specify a protocol extension and as such Proposed Standard or Experimental would be the two usual choices. The shepherd write-up mentions that this extension only has a limited scope, however, not sure what that is supposed to mean and it also doesn’t seems a good reason for informational (but experimental maybe). There are informational RFCs that document protocols of existing deployments for informational purposed only, meaning that there is a good reason to have a description of an existing protocol in a stable reference while the process of publishing the RFC would not change any technical means of that protocol but only document what’s out there. Usually these kind of RFC have a title like “Campany’s X protocol for something”. However, this seems not to be the case here or at least it's not clear from the content of the document.
From the Designated Expert review: OLD: <import namespace="urn:iana:xml:ns:eppcom-1.0" schemaLocation="eppcom-1.0.xsd"/> NEW: <import namespace="urn:iana:xml:ns:eppcom-1.0"/>
Thank you for the work put into this document. The document is easy to read. I have a couple of comments and nits. Feel free to ignore all of them as their sole goal is to improve your document. Regards, -éric == COMMENTS == -- Section 5 -- "When performing a domain Create, either of the bundle names will be accepted. If the domain name is available, both BDN and RDN will be registered." Should it rather be "If BDN and RDN are available, then both..." ? -- Section 11 -- The 2 sentences about the experience gained in 15 years should be put in a different paragraph and even perhaps moved in the implementation status. Unsure also whether the DS/DNSKEY part should be part of the security considerations. == NITS == Generic, I find it weird to have all dates in the examples dated in 1999 or 2001 or 2012 ;-)