[regext] Re: [IANA #1410981] expert review for draft-ietf-regext-epp-eai (xml-registry)

["Gould, James" <[e-mail]>]

Tim,

Thank you for the review.  In your note, is the concern that the namespace prefix is being used for the element name (e.g., “addlEmail”)?  I found similar definitions in the following EPP RFCs, which are broadly implemented:

•         EPP RFC 5730 with xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" and <element name="epp" type="epp:eppType"/>.

•         Allocation Token Extension in RFC 8495 with “xmlns:allocationToken="urn:ietf:params:xml:ns:allocationToken-1.0" and <element name="allocationToken"  type="allocationToken:allocationTokenType" />

•         Registry Fee Extension in RFC 8748 with “xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0" and <element name="fee" type="fee:feeType" maxOccurs="unbounded" />

•         Login Security Extension in RFC 8807 with xmlns:loginSec="urn:ietf:params:xml:ns:epp:loginSec-1.0" and <element name="loginSec" type="loginSec:loginSecType" />

Thanks,

--

JG

[cid87442*image001.png@01D960C5.C631DA40]

James Gould
Fellow Engineer
[e-mail]<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[e-mail]>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com<http://verisigninc.com/>

From: Tim Bray <[e-mail]>
Date: Thursday, January 16, 2025 at 4:14 PM
To: "[e-mail]" <[e-mail]>
Cc: "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: [EXTERNAL] [regext] Re: [IANA #1410981] expert review for draft-ietf-regext-epp-eai (xml-registry)


Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

I admired the Chinese characters in the example in 5.2.5

In section 6.1 I see


  <element name="addlEmail" type="addlEmail:addlEmailType" />

Note that the value of the type attribute contains the “quoted name” addlEmail:addlEmailType where the “addlEmail” is a namespace prefix declared above. It is not a requirement on XML parsers to make the namespace-prefix mappings available in element or attribute content, although many of them can do so and I note that in general YANG does this all the time. This is the first Internet-Draft I’ve seen that has this nonstandard behavior and (a) isn’t YANG and (b) is in attribute value not element content.  So, worth raising a flag over.   -Tim

On Jan 15, 2025 at 4:52:56 PM, David Dong via RT <[e-mail]<mailto:[e-mail]>> wrote:
Dear Tim Bray, Martin Thomson (cc: regext WG),

As the designated experts for the IETF XML Registry registry, can you review the proposed registrations in draft-ietf-regext-epp-eai-23 for us? You've previously reviewed -10 of the I-D. Please see:

https://datatracker.ietf.org/doc/draft-ietf-regext-epp-eai/<https://secure-web.cisco.com/16208pCDQ8HDOrevx0GpUgeubmKL83TkqgubfPt9LCo0mIRSsaOKHVvmr1tSZkGriOyWcFqe9jHAHEOAADbEp8kIkWQNgEVrhBCxB2i_ysgNfJd1LwZqytyFQPRipQ0HK8glai8-51-Ia6klb54E4HB0-1TSfBt4ImgknNcIo76HF5MjeU8i4KbN6_wZONlPiYrgHf7rr_47VcAvPZZnGclkWchhwbaWydIJYnzl2JKHMBMAQyHsx6djJSo45Cg07Ty9GsK6e0CQH80rdYVwwmqq6ByWWSN7LzrNIoMgHlxY/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-epp-eai%2F>

The due date is January 29th.

If this is OK, when the IESG approves the document for publication, we'll make the registration at:

https://www.iana.org/assignments/xml-registry/<https://secure-web.cisco.com/1fmACYw8fQv21E6D304OcxZk3y87X0wKYGKW9ZJ083OMQxqovyaqHQA87V8Ln3aMTVqpFhTc7SfPIV_-Xe4DFLcZotm6TpRBKz9alyGI7dnnhvt6tRaznoasGBlk6afecHjvPvLS3xU0pp7QFZaK-8Rzm-8JL6ogVmRjWgXkBbyqek2VBmp6kIAjUGn0v0ylNjvYSlF_hH3wRJYjBkW7S4t6WYtZovGxaxYjqpy3-GXfEJWWgrbvJPaWtkp-ZsmFjEDv9vWJjutkcvQHKBweRnuBwE4M1rZrhHv35sVjRo4g/https%3A%2F%2Fwww.iana.org%2Fassignments%2Fxml-registry%2F>

Unless you ask us to wait for the other reviewer, we’ll act on the first response we receive.

With thanks,

David Dong
IANA Services Sr. Specialist