[Nsi-wg] NSI call tomorrow
John MacAuley
macauley at es.net
Tue Apr 19 13:34:25 EDT 2016
Here is the updated inclusion/exclusion text from the document…
19.5.1.4 ClusionType
This type definition is used to model pathfinding inclusions/exclusions in a point-to-point service request. The possible types and values specified in an inclusion or exclusion will be defined in the service specific Service Definition.
Inclusions provide pathfinders with a specific set of resources to use in path computation. Different from an ERO in that an ERO provides a specific path through the network, while inclusions specifies the starting set of resources to be used in pathfinding (not all of the resources need be used).
Exclusions provide a mechanism allowing an RA to specify a set of resources that must be excluded when computing a path.
If an inclusion(s) is present it is used to build the initial routing graph, otherwise when absent the complete set of resources are used.
If exclusion(s) is present then the specified exclusion(s) are pruned from the graph.
Any ERO is applied during path finding using the resulting graph.
Figure 142 – ClusionType.
Parameters
The ClusionType has the following parameters (M = Mandatory, O = Optional):
Parameter
M/O
Description
type
M
Order attribute is provided only when the STP is part of an orderedSTPList.
lt
O
The Service Termination Point (STP).
lte
O
Less than equal to conditional element.
gt
O
Greater than conditional element.
gte
O
Greater than equal to conditional eement.
eq
O
Equal conditional element.
Table 108 - ClusionType parameters.
The following examples show use of the inclusion and exclusion mechanism within the p2ps element. In Figure 143 the p2ps reservation request uses the “stpId” inclusion element to include four networks in pathfinding, while using the exclusion element to exclude a range of stpId within the ESnet network.
<p2p:p2ps>
<capacity>10000</capacity>
<directionality>Bidirectional</directionality>
<symmetricPath>true</symmetricPath>
<sourceSTP>urn:ogf:network:kddilabs.jp:2013:topology:bi-ps?vlan=1780-1782</sourceSTP>
<destSTP>urn:ogf:network:uvalight.net:2013:topology:ps?vlan=1780-1782</destSTP>
<inclusion type="http://schemas.ogf.org/nsi/2013/12/services/point2point#stpId">
<eq xsi:type="types:StpIdType">urn:ogf:network:es.net:2013:</eq>
<eq xsi:type="types:StpIdType">urn:ogf:network:icair.org:2013:topology</eq>
<eq xsi:type="types:StpIdType">urn:ogf:network:manlan.internet2.edu:2013:</eq>
<eq xsi:type="types:StpIdType">urn:ogf:network:netherlight.net:2013:production7</eq>
</inclusion>
<exclusion type="http://schemas.ogf.org/nsi/2013/12/services/point2point#stpId">
<eq xsi:type="types:StpIdType">urn:ogf:network:es.net:2013::amst-cr5:3_1_1:+?vlan=1001-1009</eq>
</exclusion>
</p2p:p2ps>
Figure 143 – Inclusion/exclusion example #1.
Notice that in this previous example the type attribute utilizes a unique URI to identify the type of parameter represented in the inclusion and exclusion elements.
In Figure 144 the p2ps reservation request uses the “stpId” exclusion element to remove ESnet resources from pathfinding, removes all SDP with a capacity less that 10,000 mb/s, and excludes a specific set of resources with the listed SLRG values.
<p2p:p2ps>
<capacity>10000</capacity>
<directionality>Bidirectional</directionality>
<symmetricPath>true</symmetricPath>
<sourceSTP>urn:ogf:network:kddilabs.jp:2013:topology:bi-ps?vlan=1780-1782</sourceSTP>
<destSTP>urn:ogf:network:uvalight.net:2013:topology:ps?vlan=1780-1782</destSTP>
<exclusion type="http://schemas.ogf.org/nsi/2013/12/services/point2point#stpId">
<eq xsi:type="types:StpIdType">urn:ogf:network:es.net:2013:</eq>
</exclusion>
<exclusion type="http://services.ogf.org/nsi/2013/12/definitions/EVTS.A-GOLE#sdpCapacity">
<lt xsi:type="xsd:long">10000</lt>
</exclusion>
<exclusion type="http://services.ogf.org/nsi/2013/12/definitions/EVTS.A-GOLE#slrg">
<eq xsi:type="xsd:long">400</eq>
<eq xsi:type="xsd:long">501</eq>
<eq xsi:type="xsd:long">670</eq>
</exclusion>
</p2p:p2ps>
Figure 144 – Inclusion/exclusion example #2.
In this previous example there are two parameter types in included in the exclusion elements that have been defined in the Automated GOLE EVTS Service Definition as can be seen by their URI. The sematics of these parameters and their associated values can be determined from the Service Definition.
In Figure 145 the p2ps reservation request uses the “stpId” inclusion element to include in resources from the four specified networks, and then uses the exclusion element to exclude any SDP not equal to 10,000 mb/s from pathfinding.
<p2p:p2ps>
<capacity>10000</capacity>
<directionality>Bidirectional</directionality>
<symmetricPath>true</symmetricPath>
<sourceSTP>urn:ogf:network:kddilabs.jp:2013:topology:bi-ps?vlan=1780-1782</sourceSTP>
<destSTP>urn:ogf:network:uvalight.net:2013:topology:ps?vlan=1780-1782</destSTP>
<inclusion type="http://schemas.ogf.org/nsi/2013/12/services/point2point#stpId">
<eq xsi:type="types:StpIdType">urn:ogf:network:es.net:2013:</eq>
<eq xsi:type="types:StpIdType">urn:ogf:network:icair.org:2013:topology</eq>
<eq xsi:type="types:StpIdType">urn:ogf:network:manlan.internet2.edu:2013:</eq>
<eq xsi:type="types:StpIdType">urn:ogf:network:netherlight.net:2013:production7</eq>
</inclusion>
<exclusion type="http://services.ogf.org/nsi/2013/12/definitions/EVTS.A-GOLE#sdpCapacity">
<lt xsi:type="xsd:long">10000</lt>
<gt xsi:type="xsd:long">10000</gt>
</exclusion>
</p2p:p2ps>
Figure 145 – Inclusion/exclusion example #3.
On 2016-04-19, at 9:47 AM, Guy Roberts <Guy.Roberts at geant.org> wrote:
> The following is dial-in information for Wednesday's NSI call, time:
> 7:00 PDT 10:00 ET, 15:00 GMT, 16:00 CET, 23:00 JST
>
> 1. Dial Toll-Free Number: 866-740-1260 (U.S. & Canada) 2. International participants dial: Toll Number: 303-248-0285 Or International Toll-Free Number: http://www.readytalk.com/intl 3. Enter 7-digit access code 8937606, followed by "#"
>
> Agenda:
> - All to provide an update on the progress on document preparation:https://docs.google.com/spreadsheets/d/1IWCltcKtNfh4Z532iGsJgCWygornkx2bH06d2ZFroYU/edit
> - John to run through inclusions/exclusions examples as per emails to NSI email list on13 April.
>
>
>
>
> Guy Roberts PhD
> Senior Transport Network Architect
> Tel: +44 (0)1223 371316
> Mob: +44 (0)7881 336417
> Skype: guy1965
>
> GÉANT
> Networks • Services • People
> Learn more at www.geant.org
>
> <image001.gif>
>
> GEANT Limited, trading as GÉANT. Registered in England & Wales. Registration Number 2806796. Registered Office – City House, 126-130 Hills Road, Cambridge CB2 1PQ
>
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20160419/e587b074/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-04-19 at 12.41.19 PM.png
Type: image/png
Size: 32567 bytes
Desc: not available
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20160419/e587b074/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1626 bytes
Desc: not available
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20160419/e587b074/attachment-0001.bin>
More information about the nsi-wg
mailing list