[rfc-i] Anchor Naming character set

Jim Schaad ietf at augustcellars.com
Fri Dec 27 13:25:33 PST 2013

One issue that should be addressed for both v2 and v3 is the fact that we
are  using the type ID as the anchor and then using the anchor as the bullet
string for references.  This means that there is a new restriction placed on
anchor strings in v2 that was not present in v1.  Specifically that the
anchor strings cannot start with numbers.


A couple of different ways exist to deal with this.


1.       Vanity naming of some type (with the appropriate vocabulary change)

2.       Prefixing the anchor string with an underscore is to be treated
specially in producing the bullet string (specifically remove it)


This is currently a problem with the 3GPP and 802.11 specifications unless
you want to prefix them with something like SDO.802.11 or IEEE.802.11




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20131227/0e4579b4/attachment.htm>

More information about the rfc-interest mailing list