Early permanent ID allocation is not something currently done in the IETF. Although there is already a potential requirement to do this, implementing it will imply yet another new potential requirement on the technical publisher.
o Potential Req-INDEX-7 - When an permanent ID is allocated early, the technical publisher must provide a disclaimer and pointer in the index to resolve searches on that permanent ID. The post approval version of the draft must be stored until the document is published since it could expire before publication. The text of the disclaimer that comes up could be something like: "RFC xxxx is currently in publication. A preliminary version of this specification is available at <pointer to the draft>. This draft is believed to be technically stable and has been approved by the IETF. Please ignore the expiration date on the draft as no further versions of this draft are expected prior to publication of the RFC. However, technical changes and delays in publication of this RFC are possible and the user should be aware of the inherent dangers of using pre-publication versions of documents. and any other disclaimers, blah, blah, blah" It is also recommended that the technical publisher retains control of the allocation of permanent identifiers. This is especially true when multiple organizations (IESG, IAB, IRTF) share a single identifier sequence. One way that this might work is for the IESG to request "publication" or "publication with early allocation" Stephen _______________________________________________ Techspec mailing list [email protected] https://www1.ietf.org/mailman/listinfo/techspec
