> -----Original Message----- > From: Amanda Baber via RT <[email protected]> > Sent: Thursday, March 12, 2026 7:25 AM > Cc: [email protected]; [email protected] > Subject: [EXTERNAL] [regext] [IANA #1446204] Early review: draft-ietf-regext- > ext-registry-epp-03 (IETF 125) > > 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. > > Dear Authors, > > Before the IETF meeting, we check working group agendas for documents with > IANA-related issues. We have notes about this document: > > https://secure- > web.cisco.com/1WqDzfCLTniXF6eFMa9pe1EmWRxjauvFzAtXHVaJsUB- > D9ad3Cmx6_ZqhWT9JhtdzqkM2y21s2Zm-- > _HFUU97iKXS4EOUwqog8qwBTK7_gkME- > iE83BnCypGgUtQgAaxvfSjN03u1e- > qw2B623zWFRe3VI6KGQxFRgocyqDVUzQ37rWxYmZbuuA40q2HbKu4mAhN > 9ZagjCVVUHL0mDYqZ5EzhoJVv62uN_eAO5zTDeZIh77GHlY2WTdHafOPEH02 > myZaPQbei2B7Asdash9kEZDquTGSVkI- > TCGpsuAztmkWTdDwcCAbNjgH78SjIB- > 96/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf- > regext-ext-registry-epp-03 > > Section 2.2.1: About the line “If the registration is of an IETF Standards > Track > extension, this can simply be listed as "IESG, <[email protected]>"”: most > registries > use the IETF (with the IESG email address) in this context rather than the > IESG, > and apply it to registrations made by any IETF stream document, rather than > just Standards Track documents. Would it be appropriate to change this to > something like “If the extension is registered by an IETF stream RFC, this can > simply be listed as “IETF, <[email protected]>”? (“IESG” would also need to be > replaced with “IETF” in multiple registrations in Section 2.2.2.)
[SAH] Yes, that's fine. I'll make that change when I update the draft. Thanks for the catch, Amanda! Scott _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
