Samuel Weiler skrev:
On Wed, 26 Nov 2008, Russ Housley wrote:
2. Independent submission informational RFC
...
Today, the IESG asks the RFC Editor to hold the rejected alternative
until the standards-track document is in the RFC Editor queue, and
the informational document will be published with a note indicating
that a standards-track alternative is available in RFC xxxx. That is
the point of the response you are questioning.
Having jumped through some very slow hoops several years ago to get
some IANA assignments in a 'Specification Required' registry, I worry
about the substantive effects of delaying publication for this (or
any) reason, when delaying publication might cause codepoint
assignments to also be delayed. That said, the registration policy
for that particular registry has since changed, and I'm not sure what
other registries might be affected. (RFC4020 provides for early
allocation in Standards Action registries, but not Specification
Required registries.)
I'm content to see this document be published as-is, but I'd welcome
thoughts on how to avoid blocking IANA assignments as a side effect of
publication delay.
I thought the solution in the DLV case was useful, albeit not terribly
so - publish a "specification" that didn't really specify anything, but
got the codepoint, and then follow up with the real specification as an
ind-sub when that was appropriate.
Don't know if this particular delay mechanism was involved there, though.
Harald
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf