[Nsi-wg] NSI Identifier format

John MacAuley macauley at es.net
Fri Jan 17 05:37:17 EST 2014


NSI has the requirement that the networkId of a resource must be parseable from the resource identifier.  This is especially true for the STP identifier as we have a specific requirement that an STP identifier need not be exposed in topology, and therefore, the network identifier must be derivable from the STP identifier if the target network is to be determined.  The current URN format specification document published by the NML group for use as identifiers in NML [ref] defines the resource identifier as opaque, which also implies non-parseable.  We need to resolve this issue.

I have captured a proposal below for an NSI identifier that removes the opaque URN restriction and imposes structure on the URN.  I hope this generates positive discussions :-)

<NSI identifier> ::= <prefix> ":" <organization> ":" <type>

<prefix> ::= "urn:ogf:network"

<organization> ::= <string>

<type> ::= <nsa> | <network> | <stp> | <sdp> | <serviceAdaptation> | <serviceDomain> | <service> 

<nsa> ::= "nsa:" <nsaId>
<nsaId> ::= <string>

<network> :: = "network:" <networkId>   
<networkId> ::= <string>

<stp> ::= "stp:" <networkId> ":" <stpId>
<stpId> ::= <localId> <label>
<label> ::= “?” <labelType> “=” <labelValue> | “?”<labelType> | “”
<labelType> ::= <string>
<labelValue> ::= <string>

<sdp> ::= "sdp:" <sdpId>
<sdpId> ::= <string> /* Should this be some type of source/destination stpId combination. */

<serviceAdaptation> ::= "serviceAdaptation:" <networkId> ":" <serviceAdaptationId>
<serviceAdaptationId> ::= <string>

<serviceDomain> ::= "serviceDomain:" <networkId> ":" <serviceDomainId>
<serviceDomainId> ::= <string>

<service> ::= "service:" <networkId> ":" <serviceId>
<serviceId> ::= <string>


More information about the nsi-wg mailing list