From: art <art-bounces@xxxxxxxx> on behalf of Bob Hinden <bob.hinden@xxxxxxxxx> Sent: 11 September 2021 17:03 Hi Warren, > On Sep 10, 2021, at 4:19 PM, Warren Kumari <warren@xxxxxxxxxx> wrote: > > > Seems reasonable to consider, assuming a BCP can update an Informational RFC? > > Any RFC can update any previous RFC? There are some questions about the > use of "Updates" (see draft-kuehlewind-update-tag); different WGs use it > for different things. If you are trying to catch the eye of > implementers, maybe it would help, but perhaps ask your AD. > > Yup, it should be able to. > W Are you sure? For example, can an “Experimental" RFC update an RFC at “Standard”? Can an RFC from one Stream update an RFC in another Stream? Lots of other cases come to mind. This seems a lot more subtle than any RFC can update any other RFC. <tp> I agree. A case in point is RFC8966 which deprecates TLS1.0 and TLS1.1 and updates rather a lot of RFC in doing so. Some of these are ISE and the permission of the ISE Editor was sought, and obtained, before going ahead so I do not think that any I-D from one stream can update any I-D from another. Tom Petch Bob -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
