> -----Original Message----- > From: Doug Ewell [mailto:dewell at adelphia.net] > Sent: Sunday, July 10, 2005 1:50 PM > To: LTRU Working Group > Subject: [Ltru] Re: editorial nits in initial registry draft -01 > > Randy Presuhn <randy underscore presuhn at mindspring dot com> wrote: > > > Need to ensure that the "RFC 3066bis" in the Abstract gets replaced > > with the actual RFC number during the RFC editing process. > > Just let me know how to do that. I tried making this a > reference to [I-D.ietf-ltru-registry], but one tool or > another didn't like that in the Abstract. Don't put references in the abstract. It has to be complete when separated from the rest of the document. If you want to describe another document that will become an RFC, just use the current I-D name for now and add a note to the RFC Editor below the abstract to let them know that the name of the I-D should be replaced with "RFC <whatever>" when the registry document is published as an RFC. -Scott- _______________________________________________ Ltru mailing list Ltru at lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.