> On 13 Mar 2025, at 12:40, Martin Thomson <m...@lowentropy.net> wrote:
> 
> On Thu, Mar 13, 2025, at 10:33, Paul Hoffman wrote:
>> a) People generally agree that we should indicate obsolescence and 
>> historic status on RFCs
>> b) The metadata near the top of the definitive format for an RFC can 
>> change if that RFC is made obsolete or historic
>> c) All the publication formats will be regenerated when (b) happens
>> d) The indicator of the status change will be at or near the top of the 
>> regenerated publication formats
> 
> I like this formulation better.  For one, it requires less of a fundamental 
> change to how the revision is produced relative to the original.

Works for me too.  Thanks.

Jay


-- 
Jay Daley
IETF Executive Director
exec-direc...@ietf.org

-- 
rswg mailing list -- rswg@rfc-editor.org
To unsubscribe send an email to rswg-le...@rfc-editor.org

Reply via email to