[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

As there have been no objections, this closes the WGLC and this document will be submitted to the IESG for consideration as a proposed standard. This document has been in progress for quite some time. It represents a great deal of work by many people, including having been through an IETF last

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

ailto:shollenbeck=40verisign@dmarc.ietf.org>>, "a...@gulbrandsen.priv.no<mailto:a...@gulbrandsen.priv.no>" mailto:a...@gulbrandsen.priv.no>>, "regext@ietf.org<mailto:regext@ietf.org>" mailto:regext@ietf.org>> Subject: [EXTERNAL] [regext] Re: WGL

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://verisigninc.com/> From: James Galvin Date: Monday, December 2, 2024 at 8:55 AM To: Joseph Yee Cc: "Hollenbeck, Scott" , "a...@gulbrandsen.priv.no" , "regext@ietf.org" Subject: [EXTERNAL] [regext]

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

.@gmail.com>> Cc: "Hollenbeck, Scott" mailto:shollenbeck=40verisign@dmarc.ietf.org>>, "a...@gulbrandsen.priv.no<mailto:a...@gulbrandsen.priv.no>" mailto:a...@gulbrandsen.priv.no>>, "regext@ietf.org<mailto:regext@ietf.org>" mailto:rege

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

" , "regext@ietf.org" Subject: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09) Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know t

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09) 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. Hollenbeck, Scott writes: Please note

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

> -Original Message- > From: Andrew Newton (andy) > Sent: Friday, November 22, 2024 2:14 PM > To: Hollenbeck, Scott > Cc: regext@ietf.org > Subject: [EXTERNAL] Re: [regext] Re: WGLC: draft-ietf-regext-epp-eai (was: > WGLC: draft-ietf-regext-rdap-rir-search-09) &g

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

On Fri, Nov 22, 2024 at 10:25 AM Hollenbeck, Scott wrote: > > > 1. Section 2 discusses the migration to a newer version of the extension > > with a > > SHOULD but the text does not describe the migration process nor references > > one. Either the SHOULD should be lowercased, the migration process

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

> -Original Message- > From: Andrew Newton (andy) > Sent: Thursday, November 21, 2024 4:17 PM > To: REGEXT Working Group > Subject: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: > draft-ietf-regext-rdap-rir-search-09) > > Caution: This email

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

I support this document but have the following issues: 1. Section 2 discusses the migration to a newer version of the extension with a SHOULD but the text does not describe the migration process nor references one. Either the SHOULD should be lowercased, the migration process should be specified,

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

inline On Wed, Nov 20, 2024 at 7:29 AM Hollenbeck, Scott wrote: > > -Original Message- > > From: Arnt Gulbrandsen > > Sent: Monday, November 18, 2024 11:15 AM > > To: regext@ietf.org > > Subject: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-epp-ea

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

> -Original Message- > From: Arnt Gulbrandsen > Sent: Monday, November 18, 2024 11:15 AM > To: regext@ietf.org > Subject: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: > draft-ietf-regext-rdap-rir-search-09) > > Caution: This email ori

[regext] Re: WGLC: draft-ietf-regext-epp-eai

I support publishing Mario Il 18/11/2024 15:17, James Galvin ha scritto: My apologies folks, I got the subject line wrong. The document in WGLC is: https://datatracker.ietf.org/doc/draft-ietf-regext-epp-eai/22/ Please also take this message as a reminder to indicate your support or any que

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

> -Original Message- > From: James Galvin > Sent: Monday, November 18, 2024 9:17 AM > To: kowa...@denic.de > Cc: REGEXT Working Group > Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-epp-eai (was: WGLC: > draft-ietf-regext-rdap-rir-search-09) > [SAH] [snip] Please note that I have

[regext] Re: WGLC: draft-ietf-regext-epp-eai

+1 On 18.11.24 15:17, James Galvin wrote: My apologies folks, I got the subject line wrong. The document in WGLC is: https://datatracker.ietf.org/doc/draft-ietf-regext-epp-eai/22/ Please also take this message as a reminder to indicate your support or any question or concerns you might have

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

Hollenbeck, Scott writes: Please note that I have a comment from Joseph Yee that needs to be addressed if there's no objection to do so. Why does it need to be addressed? EPP doesn't even try to tell you that a contact object will be invalidated if the domain is transferred, or that a contact

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

On Mon, Nov 18, 2024 at 3:48 PM Arnt Gulbrandsen wrote: > > James Galvin writes: > > https://datatracker.ietf.org/doc/draft-ietf-regext-epp-eai/22/ > > > > Please also take this message as a reminder to indicate your > > support or any question or concerns you might have. > > Since I've been criti

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

+1 -- JG James Gould Fellow Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com On 11/18/24, 10:05 AM, "Dmitry Belyavsky" mailto:beld...@gmail.com>> wrote: Caution: This email originated from outside the organizatio

[regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC: draft-ietf-regext-rdap-rir-search-09)

James Galvin writes: https://datatracker.ietf.org/doc/draft-ietf-regext-epp-eai/22/ Please also take this message as a reminder to indicate your support or any question or concerns you might have. Since I've been critical about some aspects of older revisions, I'll just state for the record