I suggest separating things:
1) We have long allowed citation of I-Ds for informational purposes. I
don't think anyone wants to prohibit that.
2) Whatever we say in our boilerplate, we can't stop other folks from
citing I-Ds in the equivalent of normative fashions. So be it.
3) It would be really strange to cite an I-D as a normative reference in
an IETF RFC. Did you mean to cite that particular version normatively?
Or are you so confident that the I-D will not change before it becomes
an RFC that you insist on citing it now? And not merely waiting to
publish the RFC till the cited document is actually done?
4) Related to 3, citing an I-D for an IANA registry that requires a
stable specification seems very odd. Do we intend the code point to
mean any version of the document (even though they probably differ? Do
we intend the code point to mean the behavior in this version of the
document, even though the IETF may later decide that the right behavior
is something else? If we claimed to want a stable specification so
implementations using the code point interoperate (as distinct from an
FCFS registry where the point is just to make sure folks don't collide)
then we need to actually be stable. (If we discover that while we
thought we wanted interoperable code points all we really want is
non-conflicting code points then fix the rules for the specific registry.)
Yours,
Joel
On 12/10/2024 3:46 PM, Eliot Lear wrote:
And this is where we run into problems, because the moment you change
that boiler plate, you will devalue the RFC series and create support
and interoperability problems as people end up implementing different
versions of a specification. And to be clear, IANA is the LEAST of
our problems. The IETF needs a way to have not-ready-for-prime-time
DRAFT work without fear ofcreating a mess.
Eliot
_______________________________________________
rfc-interest mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
rfc-interest mailing list -- [email protected]
To unsubscribe send an email to [email protected]
