[xml2rfc] shorter refs to i-ds
randy@psg.com (Randy Bush) Mon, 11 November 2002 12:49 UTC
From: randy@psg.com
Date: Mon, 11 Nov 2002 04:49:54 -0800
Subject: [xml2rfc] shorter refs to i-ds
References: <E18Ay4w-000AhW-00@rip.psg.com> <20021110132659.1369578a.mrose+internet.xml2rfc@dbc.mtview.ca.us> <E18B1bE-000GHA-00@rip.psg.com> <20021110163748.7b489dc4.mrose@dbc.mtview.ca.us> <5.1.0.14.2.20021111083333.04373240@127.0.0.1>
Message-ID: <E18BE0n-000AUL-00@rip.psg.com>
> A maybe simpler suggestion: if the reference tag is longer than some > length (say 12-16 chars), wrap the following text to a new line? > > [I-D.ietf-ipngwg-addr-arch-v3] > Gupta, M. and S. Deering, "IP Version > 6 Addressing Architecture", draft- > ietf-ipngwg-addr-arch-v3-11 (work in > progress), October 2002. > > [RFC2434] Narten, T. and H. Alvestrand, > "Guidelines for Writing an IANA > Considerations Section in RFCs", BCP > 26, RFC 2434, October 1998. works for me > (I'm guessing that most I-D refs will become RFCs in the lifetime of a > draft, so any problem sort-of dissipates.) while this is true for normative references, it need not be the case for informative ones. randy
- [xml2rfc] shorter refs to i-ds Scott W Brim
- [xml2rfc] shorter refs to i-ds Randy Bush
- [xml2rfc] shorter refs to i-ds Graham Klyne
- [xml2rfc] shorter refs to i-ds Randy Bush
- [xml2rfc] shorter refs to i-ds Marshall Rose
- [xml2rfc] shorter refs to i-ds Randy Bush
- [xml2rfc] shorter refs to i-ds Marshall Rose
- [xml2rfc] shorter refs to i-ds Randy Bush