Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

+1 Am 20.03.23 um 14:40 schrieb James Galvin: The document editors have indicated that the following document is ready for submission to the IESG to be considered for publication as a Proposed Standard: Registration Data Access Protocol (RDAP) Reverse Search

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

+1 Jasdip On 3/20/23, 9:41 AM, "regext on behalf of James Galvin" mailto:regext-boun...@ietf.org> on behalf of gal...@elistx.com > wrote: The document editors have indicated that the following document is ready for submission to the IESG to be considered for

[regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

The document editors have indicated that the following document is ready for submission to the IESG to be considered for publication as a Proposed Standard: Registration Data Access Protocol (RDAP) Reverse Search https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/20/

Re: [regext] Requesting a WGLC on draft-ietf-regext-rdap-redacted

The Chairs have received your request and added it to the list. Note that we only do one WGLC at a time and draft-ietf-regext-rdap-reverse-search-20 is next. We will move on draft-ietf-regext-rdap-redacted-11 when that completes. Thanks, Antoin and Jim On 13 Mar 2023, at 8:04, Gould,

Re: [regext] JSContact issues

On Fri, Mar 17, 2023 at 10:45 AM Mario Loffredo wrote: > > > 1) Section 3 has some strong MUST language regarding JSContact and > > EPP. As I'm reading it, I am trying to deduce what interoperability > > problem is being mitigated but, at least to me, it is not apparent. If > > there is some