[Nsi-wg] Network and STP Identifiers

[Freek Dijkstra]

On 8-10-2014 15:15, John MacAuley wrote:

>   <ns2:BidirectionalPort id="urn:ogf:network:es.net:2013:lbl-mr2:xe-8/2/0:*">
>   <ns2:PortGroup id="urn:ogf:network:es.net:2013:lbl-mr2:xe-8/2/0:*:in"/>
>   <ns2:PortGroup id="urn:ogf:network:es.net:2013:lbl-mr2:xe-8/2/0:*:out"/>

Sorry, these are invalid according to RFC 2141: A URN may never contain
a slash ("/").

See section 2.3.2 of RFC 2141:

   RFC 1630 [2] reserves the characters "/", "?", and "#" for particular
   purposes. The URN-WG has not yet debated the applicability and
   precise semantics of those purposes as applied to URNs. Therefore,
   these characters are RESERVED for future developments.  Namespace
   developers SHOULD NOT use these characters in unencoded form, but
   rather use the appropriate %-encoding for each character.

So formally, the "?" and "#" are also not allowed according to RFC 2141.

However, there is a extension of RFC 2141 in progress that does allow
these for special purpose as the "query part" and "fragment identifier".

See Appendix A of draft-ietf-urnbis-rfc2141bis-urn:

   o  Allows the URI query component after the URN as assigned.
   o  Allows the URI fragment identifier component after the URN as
      assigned.
   o  Disallows "-" at the end of a NID.
   o  Allows the "~" and "&" characters in an NSS.
   o  Formally registers 'urn' as a URI scheme.

See
https://tools.ietf.org/html/draft-ietf-urnbis-rfc2141bis-urn-07#appendix-A

Freek

-- 
Freek Dijkstra
| Group Leader & Network Expert | Infrastructure Services | SURFsara |
| Science Park 140 | 1098 XG Amsterdam | +31 6 4484 7459 |
| Freek.Dijkstra at surfsara.nl | www.surfsara.nl |

Available on Mon | Tue | Wed | Thu |