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

Two small schema issues
by John MacAuley 17 Aug '13

17 Aug '13

Peoples, During coding I noticed a couple schema issues that will need to be addressed after the GLIF demo. I will submit an update for them, but please do not incorporate the update until after the demo. 1. Removal of ftypes namespace and import statement from ogf_nsi_services_p2p_v2_0.xsd as a hold over from when the STP definition was in the service schema. This is will be a backward compatible change and will not result in any impact to existing code. 2. The only dependency the ogf_nsi_services_types_v2_0.xsd has on the ftypes namespace is for the "TypeValuePairListType" as seen below in the labels definition. There can be build issues when importing the WSDL through jax-ws and the services through jaxb compilers. Conflicting package names can result if the default namespace is used during compile for the package names. To fix this issue I would like to remove use of the ftypes namespace in the services types by replacing labels within the STP definition with something local to the ogf_nsi_services_types_v2_0.xsd file.  <xsd:complexType name="StpType"> <xsd:annotation> <xsd:documentation xml:lang="en"> The Service Termination Point (STP) type used for path selection. Elements: networkId - A globally unique identifier (URN) that identifies the Network. Rather than forcing parsing of an STP to determine the Network, a separate Network object is defined to allow an intermediate NSA to forward the message to the target Network without needing to know about the STPs within that domain. localId - A locally unique identifier for the STP within the associated network. labels - Technology specific attributes associated with the Service Termination Point. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element name="networkId" type="xsd:string" /> <xsd:element name="localId" type="xsd:string" /> <xsd:element name="labels" type="ftypes:TypeValuePairListType" minOccurs="0" /> </xsd:sequence> </xsd:complexType> Thanks, John

1 0

Re: [Nsi-wg] Tutorial Topologies
by Freek Dijkstra 16 Aug '13

16 Aug '13

Hi Chin, Sorry for not responding sooner. Off-list, you brought up the following issue. I hope it is OK to quote you on-list. You brought up an important issue. >> Thanks for sending out the topologies. >> >> I tried importing them into the topology service that Ahmed >> implemented (at http://lstest.es.net) but ran a couple of issues, one >> small, and the other a bit more involved. >> [...] >> As for the more involved issue, our parser is unable to distinguish >> between what is a reference, and what is not, so for example: >> >> Excerpt from aruba.xml: >>  >> <nml:Relation type="http://schemas.ogf.org/nml/2013/05/base#hasOutboundPort"> >> <nml:PortGroup id="urn:ogf:network:aruba.example:2013:aruba-bonaire"> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> <nml:LabelGroup labeltype="http://schemas.ogf.org/nml/2012/10/ethernet#vlan">1780-1783</nml:LabelGroup> >> <nml:Relation type="http://schemas.ogf.org/nml/2013/05/base#isAlias"> >> <nml:PortGroup id="urn:ogf:network:bonaire.example:2013:aruba-bonaire"/> >> </nml:Relation> >> </nml:PortGroup> >> </nml:Relation> >> >> Excerpt from bonaire.xml: >>  >> <nml:Relation type="http://schemas.ogf.org/nml/2013/05/base#hasInboundPort"> >> <nml:PortGroup id="urn:ogf:network:bonaire.example:2013:aruba-bonaire"> >> <nml:LabelGroup labeltype="http://schemas.ogf.org/nml/2012/10/ethernet#vlan">1780-1783</nml:LabelGroup> >> <nml:Relation type="http://schemas.ogf.org/nml/2013/05/base#isAlias"> >> <nml:PortGroup id="urn:ogf:network:aruba.example:2013:aruba-bonaire"/> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> </nml:Relation> >> </nml:PortGroup> >> </nml:Relation> >> >> After we import the aruba.xml topology into the topology server, when >> we import bonaire.xml, our server doesn't know Bonaire's aliased >> "aruba-bonarie" port group is a reference, and overwrites Aruba's entry. This very issue is covered in section 4.3 of GFD.206. This is a verbatim quote of that section: > 4.3 Combining Object Descriptions > > A given object may have multiple attributes and relations. These > attributes and relations may be described in different places in a > syntax. It is up to the parser to combine all attributes and > relations. > > NML currently does not have a mechanism to check if a given > description of an object is complete. Thus, it does not distinguish > between a full description of an object or merely a pointer to an > object. > > Parsers should be aware that the NML descriptions do not provide any > guarantee regarding the integrity nor the authenticity of the > description. Parsers are advised to use external mechanism to avoid > that an erroneous description of an object in one (possibly > malicious) topology description pollutes a correct description of the > same object in another topology description. So basically, the idea is that the second (reference) description does not overwrite the original description, but augments it, combining the two. Either solution (replacing or augmenting a description) raises some security issues, in that an attacker may add false descriptions of STP, in order to insert malicious information in the topology. For that reason, it is highly recommended that NSI implementations take the source of information into account, and are very selective in accepting information from a domain, that describes information about another topology. I believe NSI has some mechanisms to In fact, the whole isAlias construct is made specifically to make it easier to reference between sources of information. So my recommendation is not to accept any information about a STP or Port, from another domain, except as the destination of an "isAlias" relation. >> I had a couple of thoughts on this, but they may be a complete hack >> and ugly. >> >> 1. If an "empty" element (that has no further nested elements, e.g. >> Bonaire's "aruba-bonarie" port group) matches an existing "non-empty" >> element (e.g. Aruba's "aruba-bonarie" port group), it is assumed to be >> a reference. This might make things like modify complicated, but >> maybe if we can make the assumption that only "non-empty" elements can >> modify existing elements, that might work. >> >> 2. Use the "isAlias" relation to assume referencing. This will only >> be specific to NML/NSI, but then it may be acceptable compromise. The second one is true for all relations: <nml:SomeObject id="A"> <nml:Relation type="http://....#someRelation"> <nml:OtherObject id="B"> In this case, A the _source_ and B is the _domain_ of the relation. B is always a reference. This object B can contain some more information, but I strongly recommend to be careful to accept any information from any source other than the domain. (judged by the nsi:managedBy relation from topology to NSA). Hope this helps! Freek -- SURFsara has a new telephone number: + 31 20 800 1300. Freek Dijkstra | Group Leader | Network Innovation & Support | SURFsara | | Science Park 140 | 1098 XG Amsterdam | +31 20 800 1320 | | Freek.Dijkstra(a)surfsara.nl | www.surfsara.nl | Available on Mon | Tue | Thu | Fri |

1 0

Transition!
by Jeroen van der Ham 15 Aug '13

15 Aug '13

Hi all, After about 10 years of research in network topology descriptions and related areas, I feel it is time for some change :) As of September 1st I will be moving to a new job. But don't worry, I will not be going very far away: I will be moving to the education side and will be teaching at the System and Network Engineering Master at the UvA. In that position I will also have one day a week available for research, which at the start will be used to make sure that the transition goes as smoothly as possible. I will still be attending the GLIF and NSI meetings in Singapore, but after that it is far less likely I will be able to travel or contribute to meetings. It has really been a pleasure and privilege to work in these great communities and to have been able to (heatedly ;)) discuss ideas with international peers. You have all made me feel very welcome and every meeting of GLIF and OGF has always been a very enjoyable experience. I will certainly miss the friendly dinners in remote locations :). Some of my responsibilities will be taken over by Paola Grosso while the research group looks for a new post-doc. If you have any questions, feel free to contact me. Thank you all, Jeroen van der Ham.

1 0

NSI-WG meeting Wed 8/14 Topology service presentation slides
by Chin Guok 15 Aug '13

15 Aug '13

Hi all, I apologize for not sending this out sooner, but here are the slides from today's NSI-WG topology service presentation. - Chin

1 0

Topology Service presentation/demo for NSI call for tomorrow (Wed 8/14)
by Chin Guok 15 Aug '13

15 Aug '13

Hi all, We had a summer intern (Ahmed El-Hassany) working at ESnet on some topology stuff in the last couple months, and he put together a prototype topology service that might be useful for the NSI-WG. Just some background, Ahmed was the primary architect of the GENI Topology service which uses the RSpec format, so he has a bunch of experience behind him. Unfortunately he has now taken up a research position at UC Berkeley, so the prototype topology service will remain in its current state till we find resources to further its development. Having said that, a testing instance of the service is running at http://lstest.es.net:8080/urns. The documentation of using it is located at https://github.com/ahassany/topology-service/wiki/Using-NML-NSI-Topology-Se…. All the tutorial topologies that Jeroen put up on GitHub (see forwarded email) has been loaded into the service. You can list all NSAs by: curl http://lstest.es.net:8080/urns/ Or get a specific one by: curl http://lstest.es.net:8080/urns/urn:ogf:aruba.example:2013:nsa <http://lstest.es.net:8080/urns/urn:ogf:network:es.net:2013:nsa> For tomorrow's meeting, Ahmed will do show-and-tell, so please log into www.readytalk.com and use the 7-digit access code 8937606 to access the "show" portion of the meeting. Time: 7:00 PDT 10:00 EDT, 15:00 BST, 16:00 CEST, 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: - Prototype topology service presentation/demo Thanks all. - Chin -------- Original Message -------- Subject: [Nsi-wg] Tutorial Topologies Date: Thu, 8 Aug 2013 13:20:40 +0200 From: Jeroen van der Ham <vdham(a)uva.nl> To: NSI Working Group <nsi-wg(a)ogf.org> Hi all, I have created new topologies for the tutorials. These follow the same schema as the updated Automated GOLE topologies. The new tutorial topologies should follow the same topology as the old ones. The domain names for all of them are "aruba.example" (using the IETF reserved namespace for examples). They can be found at the tutorial repository: https://github.com/jeroenh/NSI-Tutorial-Topologies/tree/master/topos Jeroen. -- Chin Guok NOC: (510) 486-7600 ESnet Network Engineering Group (AS293) (800) 333-7638 Lawrence Berkeley National Laboratory

1 1

Network portion of an STP
by John MacAuley 13 Aug '13

13 Aug '13

Peoples, What am I suppose to put in the network portion of the STP? I was looking in the topology schema and there is nothing specifically called "network" so should I assume it is the topology URN? networkId = "urn:ogf:network:example.org:2013:topology" As a follow-up, do I also then populate the local portion with the full URN of the port? localId = "urn:ogf:network:example.com:2013:eth0-out" Thank you! John

4 4

DynamicKL NSI 2.0 is available
by 이경민 13 Aug '13

13 Aug '13

3 2

Tutorial Topologies
by Jeroen van der Ham 08 Aug '13

08 Aug '13

Hi all, I have created new topologies for the tutorials. These follow the same schema as the updated Automated GOLE topologies. The new tutorial topologies should follow the same topology as the old ones. The domain names for all of them are "aruba.example" (using the IETF reserved namespace for examples). They can be found at the tutorial repository: https://github.com/jeroenh/NSI-Tutorial-Topologies/tree/master/topos Jeroen.

1 0

minutes from today's NSI conf call
by Guy Roberts 07 Aug '13

07 Aug '13

.... are available here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6529 _____________________________________________________________________ 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 07 Aug '13

07 Aug '13

Hi all, The following is dial-in information for Wednesday's NSI call: Time: 7:00 PDT 10:00 EDT, 15:00 BST, 16:00 CEST, 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: - Service Definition schema documentation - Error message handling - CS doc editing - Chairing next weeks call _____________________________________________________________________ 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