Hi Scott,

Thanks for following up on this. It dropped under the radar for a while. At least for me.

I think, even if the change is not a big one regext is the right place to do the work, this being the WG explicitly tasked with EPP extensions. AD-Sponsorship, being maybe a nice shortcut, won't cover for necessary expertise which is clearly within this WG. The changes being limited it can be a streamlined process IMHO heading quickly to WG last call just after adoption. I would support the adoption as a side note.

Reviewing the changes I have the following questions/remarks:

1) Change from "Informational" to "Other" in 2.2.1. If the intention is to remove the confusion between Informational RFCs and other documents, wouldn't it be useful to also advise IANA to update all non-RFC entries in the registry to "Other" as well?

2) In 2.2.3. a possibility to remove an entry was added. I think this is generally good, but quite under-specified. I am missing guidance what shall be a valid trigger to it. Would it be only the registrant, or anyone with enough of justification why some entry shall be removed? Would it be useful to have specific subject line "DELETE" specified similar to "INSERT" and "MODIFY"? Shall the delete case be limited to some specific cases? What criteria shall IESG apply when deciding? And finally why IESG at all and not DEs?

Kind Regards,

Pawel

On 18.09.25 14:34, Hollenbeck, Scott wrote:
The subject I-D was first published back in June. Andy Newton provided 
feedback, but that's been it. That begs the question: is there interest in 
seeing the draft proceed and be published as an update to RFC 7451, and if so, 
how should it proceed? I'm comfortable with the content as currently written, 
and I don't think there's much benefit to going through a working group 
adoption process. Might we ask Orie to AD-sponsor this minor update?

Scott

_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to