October 2011 - Nsi-wg - lists.ogf.org

Groups and Labels
by Jeroen van der Ham 20 Oct '11

20 Oct '11

Hello, Yesterday in the call Jerry and I briefly touched on the issue of Groups and Labels in network topologies. After numerous discussions, it seems that Jerry and I still have opposing views, and we do not seem to be getting closer to a solution. This is why I'm raising this as a group issue, so that we can have a broader discussion on this. The issue at stake here is handling network connections with labels. Take for example a circuit from CERN, through USLHCNet, NLR, ending up in San Antonio. One end of the connection uses VLAN 3000, this is not available end-to-end, so it gets converted to VLAN 3067 along the way. My viewpoint is that this label is an essential part in the definition of an end-point of a connection. The end-point is defined both by the place in the network (URN), as well as the label VLAN 3067. Both these elements, point and label, must be indicated, and available to the pathfinder in order to optimally calculate a connection. This does not pose any restrictions on how that calculation and/or negotiation takes place, but at least that information is available. From what I understand, Jerry's viewpoint is that the label is *not* an essential part of the end-point definition. An end-point is in the network, and a Group of STPs is described that derive from that end-point, which implicitly encode the label through the mapping. The value of the label is available to the intra-domain manager, but not inter-domain. Inter-domain path calculation takes place without knowledge of the label, assignment of labels is done by the domains themselves. My problem with the latter approach is that it is virtually impossible to do pathfinding when you mix domains that can and cannot swap labels. In the example above the label is translated by a transit-domain. If the label is not available in the pathfinding process, the domains basically have to guess at which label to use. If it turns out not to work, the requesting agent is groping in the dark for another possibility. Almost all circuits that are being made currently use a label. The OSCARS interface supports the user defining a label in a request. OpenDRAC supports the user defining a label in a request. Other NRMs probably do also, so why would NSI not support this? Jeroen.

1 1

minutes from Wednesday's NSI conf call
by Guy Roberts 20 Oct '11

20 Oct '11

The minutes from yesterday's NSI conf call are available here: http://forge.gridforum.org/sf/go/doc16350?nav=1 Guy _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

1 0

FIA demo topo v1.2
by Jerry Sobieski 20 Oct '11

20 Oct '11

Changes: - Removed link from GEANT to Netherlight, and removed associated STPs from topology - changed NSnetwork urns to lowercase nsnetwork - updated diagrams to reflect JGNX and GEANT changes - remove GRnet (not sure if they are able to participate...so made their perfSonar look like the others. - Added US LHCnet link from Netherlight to StarLight - updated some location info in the diagrams (Can someone confirm whether the GEANT should be located in Cambridge or in Paris?) - updated SOAP endpoints for Pionier, KRLight, KDDI, StarLight, GEANT,...

2 1

Issue 47 in ogf-nsi-project: Add WS-Secuirty policy definitions to WSDL for digital signing of NSI SOAP message
by ogf-nsi-project＠googlecode.com 19 Oct '11

19 Oct '11

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.Rio FixedInVersion-2.0 New issue 47 by jmacau...(a)gmail.com: Add WS-Secuirty policy definitions to WSDL for digital signing of NSI SOAP message http://code.google.com/p/ogf-nsi-project/issues/detail?id=47 Description of Issue: Need to validate the integrity of an NSI message as well as validate it is issued from the expected NSA. Discussion of Issue: It was previously agreed that the "transport layer" would digitally sign the NSI message to verify it was not tampered with, and is from the expected sender. This can be accomplished by using WS-Secuirty policy definitions in the WSDL. This mechanism is currently being used by OSCARS and is accepted as a common web service practice. Resolution of Issue: Add WS-Secuirty policy definitions to WSDL for digital signing of NSI SOAP message and NSA implement the solution.

1 0

Re: [Nsi-wg] Issue 1 in ogf-nsi-project: ConnectionStateType.TERMINATEING - maybe TERMINATING looks better
by ogf-nsi-project＠googlecode.com 19 Oct '11

19 Oct '11

Updates: Status: Fixed Comment #8 on issue 1 by jmacau...(a)gmail.com: ConnectionStateType.TERMINATEING - maybe TERMINATING looks better http://code.google.com/p/ogf-nsi-project/issues/detail?id=1 This issue was closed by revision r2.

1 4

Re: [Nsi-wg] Issue 7 in ogf-nsi-project: change reservation name in WSDL
by ogf-nsi-project＠googlecode.com 19 Oct '11

19 Oct '11

Updates: Status: Fixed Labels: FixedWithUpdater4 Comment #3 on issue 7 by jmacau...(a)gmail.com: change reservation name in WSDL http://code.google.com/p/ogf-nsi-project/issues/detail?id=7 Renamed all "reservation" related messages to "reserve" with update r4. Closing issue #7. ------------------------------------------------------------------------ r4 | jmacauley(a)gmail.com | 2011-10-14 15:18:20 -0400 (Fri, 14 Oct 2011) | 1 line Changed reservation message set to reserve as per issue #7. Closing issue #7. ------------------------------------------------------------------------

1 1

Issue 46 in ogf-nsi-project: Remove remote import of schema from local copies of SAML related schema files.
by ogf-nsi-project＠googlecode.com 19 Oct '11

19 Oct '11

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.0 FixedInVersion-1.SC New issue 46 by jmacau...(a)gmail.com: Remove remote import of schema from local copies of SAML related schema files. http://code.google.com/p/ogf-nsi-project/issues/detail?id=46 Description of Issue: There are still "<!DOCTYPE ...>" descriptions in "xenc-schema.xsd" and "xmldsig-core-schema.xsd". The descriptions should be removed or commented out because they cause remote access to the www.w3.org site during compilation and introduce some delay. Discussion of Issue: We have already provided local copies of the SAML schema and modified the import statements to load from the local copy. I see no reason not to accommodate this request. Resolution of Issue: JM will comment out the problem import statements.

1 2

Issue 45 in ogf-nsi-project: Update WSDL name space for trunk and ogf-nsi-cs-v1.sc to distinguish version.
by ogf-nsi-project＠googlecode.com 19 Oct '11

19 Oct '11

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.0 FixedInVersion-1.SC New issue 45 by jmacau...(a)gmail.com: Update WSDL name space for trunk and ogf-nsi-cs-v1.sc to distinguish version. http://code.google.com/p/ogf-nsi-project/issues/detail?id=45 This one came to me in a dream last night. I forgot to update the name space version to uniquely identify the SuperComputing 2011 version.

1 2

Issue 43 in ogf-nsi-project: Submit NSI Connection Services WSDL v1.rio to subversion
by ogf-nsi-project＠googlecode.com 19 Oct '11

19 Oct '11

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.0 FixedInVersion-1.1 New issue 43 by jmacau...(a)gmail.com: Submit NSI Connection Services WSDL v1.rio to subversion http://code.google.com/p/ogf-nsi-project/issues/detail?id=43 Submit reference WSDL used in the GLIF Rio demo into subversion as a basis for future changes.

1 4

Issue 44 in ogf-nsi-project: Branch NSI WSDL trunk for SuperComputing 2011
by ogf-nsi-project＠googlecode.com 19 Oct '11

19 Oct '11

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.0 FixedInVersion-1.1 New issue 44 by jmacau...(a)gmail.com: Branch NSI WSDL trunk for SuperComputing 2011 http://code.google.com/p/ogf-nsi-project/issues/detail?id=44 Create a snapshot branch of the NSI WSDL with SuperComputing fixes so that we have a stable version for developers to code against.

1 3