Hi all,
As Scott mentioned, this WG Last Call ended last week; let’s officially
close it. We had more than six participants in favor, a few suggestions,
and no objections. Scott has already published a new version of the
document that incorporates almost all the feedback. Next, Scott will
publish another version, incorporating the latest suggestions. After
that, the document will be ready for submission to the IESG.
Gavin Brown will be the document shepherd for this document. Once we
have a new version of the document, the chairs will ask him to write a
write-up and then submit it to the IESG.
Thank you all,
Your REGEXT co-chairs Antoin, Jim, and Jorge
On 19/03/26 7:27 AM, Scott Hollenbeck wrote:
*From:*James Galvin <[email protected]>
*Sent:* Wednesday, March 18, 2026 10:49 PM
*To:* Jorge Cano <[email protected]>
*Cc:* [email protected];
[email protected]; [email protected]
*Subject:* [regext] Re: WG Last Call:
draft-ietf-regext-ext-registry-epp-03 (Ends 2026-03-09)
Speaking as a participant,
I support publication of this document.
I do have two what I consider to be editorial suggestions for
consideration.
1. The last sentence in Section 2.1 has a "should not" and I think
that should be "SHOULD NOT". Here is the sentence:
Should they decline to do so, perceived similarity should not be a
sufficient reason for rejection as long as all other requirements are
met.
[SAH] Maybe. This isn’t interoperability guidance. What’s there now
seems clear enough, but with the “as long as” text that’s there we’ve
provided context that explains why. I’ll make the change as long as no
one objects.
2. In the Security Considerations, there is only a back reference to
RFC3735. Shouldn't we include a back reference to STD69 so that we
include all the Security Considerations sections from EPP?
[SAH] That seems like a good idea. Another update is needed before
this goes to the IESG.
Scott
_______________________________________________
regext mailing list [email protected]
To unsubscribe send an email [email protected]
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
