December 2013 - Nsi-wg - lists.ogf.org

Re: [Nsi-wg] [Nml-wg] NSI Topology
by John MacAuley 04 Dec '13

04 Dec '13

Last night after working on this for a week I realized the labelType is really not required because of the restriction that a Port can only have a single Label, and therefore, only a single labelType. However, it still would not hurt to have it, although, it can be derived from the Port/PortGroups present. It has been over a month since I first did the edits, but if I remember correctly, I followed the existing pattern in the NML that had an ANY in the element definitions themselves. When I attempted to add the ANY to the NetworkObject I invalidated the existing elements that had an ANY member already (Universe destroying paradox where members could no longer be resolved). I agree though, refactoring all ANYs out of the specific element definitions and placing in the NetworkObject would be a clean solution. John On 2013-12-04, at 5:39 AM, Roman Łapacz <romradz(a)man.poznan.pl> wrote: > Hi John, > > regarding the changes in the base nml xsd schema I see main two changes: > 1) presence of xs:any element in each type definition > 2) labelType in Switching Service > > Did I miss something? > > I think that in case of 1) xs:any element can be added only to NetworkObject. This way you don't have to place it in each type definition (NetworkObject is already there). > > Best regards, > Roman > > > W dniu 2013-12-04 06:06, John MacAuley pisze: >> Peoples, >> >> As promised I have done a first pass at modelling the additional NSI topology concepts in NML. I did an overview of all the components we have defined to date so we can see how they all hang together. The slide pack attached is an overview of the proposal. The XML document attacked is an updated reference topology representation, and the schema files attached are the updated NML, NSI-EXT, and service definition schemas. >> >> John >> >> >> >> >> >> >> >> _______________________________________________ >> nsi-wg mailing list >> nsi-wg(a)ogf.org >> https://www.ogf.org/mailman/listinfo/nsi-wg > > _______________________________________________ > nml-wg mailing list > nml-wg(a)ogf.org > https://www.ogf.org/mailman/listinfo/nml-wg

1 0

NSI topology representation using NML
by John MacAuley 04 Dec '13

04 Dec '13

Peoples, I have taken another look over Jeroen's document "Network Service Interface Topology Representation" given the discussion we had today on the call. I must say that we are totally out of synch with the definition of an STP Identifier in Jeroen's document and what we have in the NSI CS (no specific fault on Jeroen). Specifically, if we look at section 2.2 and 2.3 the STP identifier is defined as follows: STP ID = urn:ogf:network:example.net:2013:A2?vlan=1781 urn:ogf:network: - describes that it is a network identifier. example.net:2013 - DNS name and a (at least) year to make a globally unique prefix creating the network identifier. A2?vlan=1781 - The local component identifying the STP in the context of the network identifier. The root STP ID "urn:ogf:network:example.net:2013:A2" would be an under specified STP referring to the bundle of STP enumerated by vlan. I believe, although not specifically stated, that "urn:ogf:network:example.net:2013:A2?vlan=1780-1790" would also allow me to under specify a range of vlan. This definition for an STP Identifier is in line with the Baton Rouge discussions. This is also how I build an internal STP identifier within my path finder implementation so I can refer to an STP using a single string. So there is a gap in definition between what we have defined as an STP identifier, and what is defined in the nsi-ext specification. We have taken multiple fields from NML objects and composed a complex STP Identifier: NSI CS STP Identifier = { networkId = NML Topology Identifier; localId = NML BidirectionalPort Identifier choice { label = NML Unidirectional Port Label; labelGroup = NML Unidirectional PortGroup LabelGroup; } } To compare the content of the two, here is an example of an STP from the Netherlight topology: <sourceStp> <networkId>urn:ogf:network:netherlight.net:2013:topology:a-gole:testbed</networkId> <localId>urn:ogf:network:netherlight.net:2013:port:a-gole:testbed:uva:1</localId> <label type="http://schemas.ogf.org/nml/2013/05/ethernet#vlan">1781</label> </sourceStp> versus something like this: urn:ogf:network:netherlight.net:2013:a-gole:testbed:port:uva:1?vlan=1781 where "urn:ogf:network:netherlight.net:2013:a-gole:testbed:" is the network portion, and "port:uva:1?vlan=1781" is the local portion. I must admit I am questioning the value of our complex STP definition. I understand the value of the being able to route on networkId, and the issue with URN opaqueness, but if we are constructing the URN following a specific set of rules, could we also not parse it similarly? John

4 7

reworked NSI framework document
by Guy Roberts 04 Dec '13

04 Dec '13

Hi all, I have reworked the NSI Framework as the current version is out of date and will not match the content of the Connection Service v2.0 protocol. Please find draft NSF v2.0 here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6526 Guy _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

1 0

Wednesday's NSI conf call
by Guy Roberts 04 Dec '13

04 Dec '13

The following is dial-in information for Wednesday's NSI call, time: 7:00 PDT 10:00 EDT, 15:00 GMT, 16:00 CET, 24: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: - NSI v2.0 topology and mapping to NML (John) - Returning under-specified STPs in response to a reserveRequest - OGF 40 dinner at Lincoln college Oxford _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

1 0

Draft NML for Service Domain and Adaptation
by John MacAuley 02 Dec '13

02 Dec '13

Peoples, I have attached an XML document that uses the SwitchingService, AdaptationService and DeadaptationService to model the concepts of NSI Service Domains and Adaptation. This uses a modified NML NSI-EXT schema that is not yet approved (it is also included). Although syntactically correct, I am not 100% sure it will meet our needs until i try to build a path finding graph using the new information. i will try to do prototype this week. John.

1 0