Re: [eppext] FW: [IANA #814915] INSERT “Extensible Provisioning Protocol Mapping: Defensive Registration"

[Gavin Brown <[e-mail]>]

Here is my review as DE:

1. This extension seems to define functionality specific to the .name
TLD. Familiarity with the particulars of that TLD's business model seems
to be assumed, but for interoperability purposes, an explanation of the
context that this extension was designed for would be useful.

2. The specification appears to create a new "domain-like" object
mapping. I wonder whether any consideration was made of extending RFC
5731 domain objects instead, and what the basis of the decision was.

3. It's not clear whether <defReg:name> values exist in the same
namespace as RFC 5731 domains. Could a server contain a defReg object
whose <defReg:name> is the same as the <domain:name> property of an
RFC5731 domain? This goes back to my comment in #1 above about the lack
of context.

3. Section 3.2.1 describes how the extension can be used in conjunction
with the "idnLang" extension; however, this extension is not listed in
the references.

4. As others have, I'd also like to voice my concerns about the IP terms
in the Legal Disclaimer. The purpose of registering an EPP exension in
the registry is to facilitate harmonisation and interoperability, and
yet the Legal Disclaimer seems designed to discourage that.

5. The specification seems to meet some of the requirements in RFC 7451
Section 2.1.1, in that, in that it meets the guidelines in RFC 3735.
However, there is no comentary on Security or Privacy considerations.
Since the defReg object mapping is very similar to RFC 5731, I would
expect to see some discussion of authorisation and controls on
disclosure of authInfo codes.

G.

On 23/03/2015 17:39, Hollenbeck, Scott wrote:
> Submitted for DE evaluation.
> 
> Scott
> 
> -----Original Message-----
> From: Amanda Baber via RT [mailto:[e-mail]] 
> Sent: Monday, March 23, 2015 12:42 PM
> Cc: Hollenbeck, Scott
> Subject: [IANA #814915] INSERT “Extensible Provisioning Protocol Mapping: Defensive Registration"
> 
> #8 of 18.
> 
> -----BEGIN FORM-----
> Name of Extension:
> “Extensible Provisioning Protocol Mapping: Defensive Registration"
> 
> Document Status: 
> Informational
> 
> Reference: 
> http://www.verisigninc.com/assets/defensive-registration-mapping.pdf
> 
> Registrant Name and Email Address:
> VeriSign Inc., [e-mail]
> 
> TLDs: .name
> 
> IPR Disclosure: None
> 
> Status: Active
> 
> Notes: None
> -----END FORM-----
> 
> —
> 
> 
> JG
> 
> 
> 
> 
> 
> James Gould
> Distinguished Engineer
> [e-mail]
> 
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
> 
> VerisignInc.com
> 
> “This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”
> 
> Download BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png
> 
> image/png 4KiB
> Image not shown because display is disabled in system configuration.
> _______________________________________________
> EppExt mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/eppext
> 

-- 
Gavin Brown
Chief Technology Officer
CentralNic Group plc (LSE:CNIC)
Innovative, Reliable and Flexible Registry Services
for ccTLD, gTLD and private domain name registries
https://www.centralnic.com/

CentralNic Group plc is a company registered in England and Wales with
company number 8576358. Registered Offices: 35-39 Moorgate, London,
EC2R 6AR.