On 12/1/2024 1:15 PM, Brian E Carpenter wrote:
If people don't read the boilerplate, they might be misled. There's
nothing we can do about that.
To be strictly accurate, that's not entirely true. But we fairly
recently had a long, detailed, and enthusiastic conversation about
either reserving the RFC series for IETF documents (or a subset
thereof), or retiring the bare "RFC" moniker in favor of more specific
designations, and concluded that such a solution -- while it would
manifestly address the problem you identify -- was not what the
community wanted.
I'm not looking to re-open the conversation, but we should at least keep
in mind that we *do* know how to solve this problem if it appears to
become severe enough to overcome previous objections.
/a
_______________________________________________
rfc-interest mailing list -- rfc-interest@rfc-editor.org
To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
