Noting up front that my role has no say in this, I would make one observation:
> On 8 Jul 2026, at 15:00, Joel Halpern <[email protected]> wrote: > > As far as I can tell, this discussion has made a very good case for needing a > better way to produce revisions of RFCs. I am not confident I know what > the constraints and properties of a solution are. I do now understand that > saying "what we have works" is counter-factual. As part of the RFC Editor website refresh a lot of thought has gone into how to help consumers of RFCs, through an enhanced UI, understand RFCs that have been updated by other RFCs. The changes made so far are fairly basic - clearer banners and faster access to the related documents. A next step might be to highlight sections that have been edited by other RFCs and have a popup showing the text in the other RFC that edits it. So an automatically annotated RFC view. The next step beyond that might be the presentation of a synthetic document assembled from the base document and all of the edits. But at this point it seems like that’s a very long way round to an RFCXXXXX.VV model. Jay -- Jay Daley [email protected] www.ietf.org -- rswg mailing list -- [email protected] To unsubscribe send an email to [email protected]
