On 21/01/2022 16:38, Paul Hoffman wrote:
Why is any of this worth any effort from the IETF or the RFC Editor? Are there readers of RFCs who are confused about specific three-digit RFCs and think "I need to implement/operate this, it's current"? Even if so, would those same implementers/operators be the kind of people who would know where to find out that an RFC has been marked as historic, and what that means? This seems like a lot of effort for no defined (or discernible) value to the RFC-reading community.
I agree. It would be far simpler to create a new category 'Unknown' which means that the RFC were created before the current processes were in place and so cannot be placed in any of the other categories. Nor do they conform in many other ways e.g. Security Considerations, IANA Considerations, because the need for them was not then apparent.
Those that matter- e.g. 793 - get updated eventually and it would be more productive to put effort into those.
Tom Petch
--Paul Hoffman
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
