> -----Original Message-----
> From: James Galvin <gal...@elistx.com>
> Sent: Wednesday, July 10, 2024 4:36 PM
> To: Hollenbeck, Scott <shollenb...@verisign.com>
> Cc: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-epp-delete-bcp-03
>
> 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.
>
> As co-Chair, I was giving this document and discussion a quick review before
> closing the WGLC and handing over to the Document Shepherd and I noticed
> what I believe is an editorial point.
>
>
> Speaking as a working group participant, SAC125 offers a complementary
> analysis about sacrificial nameservers as currently appears in Section 5.  How
> do you feel about adding a single sentence to the introduction to Section 5,
> something like the following:
>
>
> For a broader consideration of the practice and its potential impact on both
> registries and registrars, “SAC125: SSAC Report on Registrar Nameserver
> Management” offers some complementary insight (https://secure-
> web.cisco.com/1wZOO7BUuBeT-
> AHajGVKNjoqp0g2E75OYaCXAzQkmuyqjjBQ_GgIFQPd7J-
> dclDAsBRRZM8mNHFL3rSf1rgz5H9s6n9aq8gsWPxOUHJPj9qRTRzly595xNW
> wqao1VWNAkA4RQtjX_R_ZQ4ObnkqwiL_apvUvrR2kd_btmjXiQZ0zR40jwku
> NWTtU8KFLsSlX8ZJ2scS94t4pEgY8z42zjNMmGz2b4VRroyZmm5dtdDRgJZs5
> hlisIEAQ2999CwRppQfVG8KUaod7XqpqFUFw_aqMUQQKPdIv47amdIa0o7P
> htYcEP42vZ56HGzgwbpAac/https%3A%2F%2Fitp.cdn.icann.org%2Fen%2Ffil
> es%2Fsecurity-and-stability-advisory-committee-ssac-reports%2Fsac-125-09-
> 05-2024-en.pdf).
>
>
> If you agree and agree it’s just an editorial nit, I’m comfortable letting it 
> get
> sorted with the Document Shepherd after the WGLC closes and before
> submission to the IESG.
>
> Of course, if anyone else has an opinion or comment please do jump in.

[SAH] Works for me.

Scott
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org

Reply via email to