I think that's fine, and that it doesn't change the meaning of anything. Alexis
On Fri, Feb 6, 2026 at 10:58 AM Paul Hoffman <[email protected]> wrote: > My weak preference is "- Continue to reference RFC 7996 but add mention of > RFC 9896 (e.g., "obsoleted by [RFC9896]").", but I defer to Alexis on this. > > --Paul Hoffman > > On Feb 6, 2026, at 10:54, Rebecca VanRheenen < > [email protected]> wrote: > > > > Hi Paul and Alexis, > > > > We have a question for you prior to publishing this document. > > > > RFC 7996 has recently been obsoleted by RFC 9896. > > > > RFC 7996 is mentioned in the document header and two times in the body > of this document: > > > > Current: > > This document updates RFCs 7841, 7991, 7992, 7993, 7994, 7995, 7996, > > 7997, 8729, 8730, and 9720. > > > > All instances of "RFC Editor" or "RFC Series Editor" in [RFC7991], > > [RFC7992], [RFC7993], [RFC7994], [RFC7995], [RFC7996], and [RFC7997] > > are replaced by "RFC Production Center (RPC)”. > > > > We don’t see any instances of "RFC Editor" or "RFC Series Editor” in RFC > 9896. > > > > Please review and let us know how you would like to proceed. Below are > some options: > > > > - No updates are needed; this document can still update RFC 7996 to note > where the organization name changed. > > - Continue to reference RFC 7996 but add mention of RFC 9896 (e.g., > "obsoleted by [RFC9896]"). > > - Remove mention of RFC 7996 altogether since it’s already been > obsoleted. >
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
