- Nsi-wg - lists.ogf.org

Today's NSI conf call
by Guy Roberts 09 May '12

09 May '12

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: * Contributions to NSI v2.0 text for CS protocol spec. Guy _____________________________________________________________________ ** Guy Roberts, PhD Senior Transport Network Architect * * 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 _____________________________________________________________________

2 1

Issue 60 in ogf-nsi-project: Restructure NSI operations into common header components and core operation body.
by ogf-nsi-project＠googlecode.com 09 May '12

09 May '12

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.1 FixedInVersion-2.0 New issue 60 by jmacau...(a)gmail.com: Restructure NSI operations into common header components and core operation body. http://code.google.com/p/ogf-nsi-project/issues/detail?id=60 Description of Issue: Refactor existing NSI CS WSDL and schema into a common NSI framework header and specific CS operation body. Discussion of Issue: As discussed at OGF 34 in Oxford. See attached slide presentation. Resolution of Issue: Restructure common elements into SOAP header and leave CS operation specifics in SOAP body. Attachments: NSI_Oxford_NSI-CS_v1.1_Changes.ppt 418 KB

1 1

Issue 59 in ogf-nsi-project: Support nested ServiceExceptions to capture downstream NSA errors.
by ogf-nsi-project＠googlecode.com 09 May '12

09 May '12

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.1 FixedInVersion-2.0 New issue 59 by jmacau...(a)gmail.com: Support nested ServiceExceptions to capture downstream NSA errors. http://code.google.com/p/ogf-nsi-project/issues/detail?id=59 Description of Issue: We need to be able to capture ServiceExceptions from downstream NSA in the request tree. Discussion of Issue: Support nested ServiceExceptions. Resolution of Issue: Agreed on the following schema update. <xsd:complexType name="ServiceExceptionType"> <xsd:annotation> <xsd:documentation xml:lang="en"> Common service exception used for both SOAP faults and the protocol Failed message. Elements: nsaId - NSA that generated the service exception. errorId - Error identifier uniquely identifying each known fault within the protocol. text - User friendly message text describing the error. variables - A collection of type/value pairs providing addition information relating to the error. downStreamException - Heirarchical list of service exceptions capturing failures withing the request tree. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element name="nsaId" type="types:NsaIdType" /> <xsd:element name="errorId" type="xsd:string" /> <xsd:element name="text" type="xsd:string" /> <xsd:element name="variables" type="saml:AttributeStatementType" minOccurs="0" /> <xsd:element name="downStreamException" type="tns:ServiceExceptionType" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType>

1 1

Issue 58 in ogf-nsi-project: Branch NSI WSDL trunk to maintain NSI CS version 1.1
by ogf-nsi-project＠googlecode.com 09 May '12

09 May '12

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Task Priority-Medium FoundInVersion-1.1 FixedInVersion-1.1 New issue 58 by jmacau...(a)gmail.com: Branch NSI WSDL trunk to maintain NSI CS version 1.1 http://code.google.com/p/ogf-nsi-project/issues/detail?id=58 Description of Issue: Branch current trunk to capture NSI CS version 1.1 and open up development of NSI 2.0. Resolution of Issue: Create new branch ogf-nsi-cs-v1.1.

1 1

GLIF Demo
by Jerry Sobieski 08 May '12

08 May '12

Hi all- I would like to formally propose that we do a reprise NSI and Automated GOLE interop demonstration we did last year with a similar effort this fall for the GLIF meeting in October. As always, demos are a lot of work, but I believe we need to cap the efforts over this past year with an appropriate public display for both NSI evolution and the enhanced scope and reach of the AutomatedGOLE architecture. If anyone objects, please send me a note asap. As always, we will be flexible in the planning details, but we need to make the commitment now if we wish to have the facilities we need in October. Thanks Jerry Here is the proposed demo description: Plugfest 2 "Windy City" - NSI v2.0 First Look + GLIF Automated GOLE Pilot Project. This demonstration will provide an alpha test of the newly minted OGF NSI version 2.0 protocols utilizing an expanded global Automated GOLE testbed facility. As a reprise to the successful NSI "Plugfest Rio" demonstrations at GLIF 2011 Rio de Janiero, the Plugfest Windy City demonstration is intended to show new features of NSI v2.0 as well as interoperability among numerous NSI implementations. The demonstrations will include a functional interoperability matrix that the NSI developers will be exercising. And some of the subtle but very important new features of NSI v2 will be highlighted and explained with informal presentations and demos - features such as enhanced topology management, sophisticated path planning, ease of use, versioning, authorization, and many more. You will have an opportunity to talk to the NSI development experts and get the low down and dirty straight from the guys (and gals) in the software development trenches. No hidden wires, and no nets.

1 0

NSI CS v2.0Oxford state machin
by Chin Guok 02 May '12

02 May '12

Hi all, Here's a write up on the state machine we discussed at Oxford. We have reiterated it a few time to clean up some of the messaging and states. Please send your comments this way. Thanks. - Chin

1 1

minutes from today's NSI conf call
by Guy Roberts 02 May '12

02 May '12

... are available here: https://forge.ogf.org/sf/go/doc16438?nav=1 _____________________________________________________________________ ** 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

Practical Pathfinding
by Paul Boven 02 May '12

02 May '12

Hi everyone, Please find attached our presentation on some of the practicalities of pathfinding, for discussion in today's or an upcoming telecon. Regards, Paul Boven, Fedde Bloemhof. -- Paul Boven <boven(a)jive.nl> +31 (0)521-596547 Unix/Linux/Networking specialist Joint Institute for VLBI in Europe - www.jive.nl VLBI - It's a fringe science

1 0

Today's NSI conf call
by Guy Roberts 02 May '12

02 May '12

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: * Contributions to NSI v2.0 text for CS protocol spec. 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

Query modifications - Issue 49
by John MacAuley 01 May '12

01 May '12

Peoples, I am down to the last couple of changes I had intended to commit for this first draft version of the WSDL. The first one I would like to discuss is Issue 49 http://code.google.com/p/ogf-nsi-project/issues/detail?id=49 which is titled "Missing information in detailed query?". I have included both the QuerySummaryResultType and QueryDetailsResultType in this e-mail for reference (removed comments due to length). Is the issue that the QuerySummaryResultType does not contain a list of direct child NSA and their connection state, and therefore, you do not know the child NSA involved in the connection to go query? I think the QueryDetailsResultType is extremely detailed. In the next e-mail I will discuss the issue of stpList and ordered path. Thanks, John. <xsd:complexType name="QuerySummaryResultType"> <xsd:sequence> <xsd:group ref="tns:ReservationInfoGroup" /> <xsd:element name="connectionState" type="tns:ConnectionStateType" /> <xsd:element name="path" type="tns:PathType" /> </xsd:sequence> </xsd:complexType> <xsd:complexType name="QueryDetailsResultType"> <xsd:sequence> <xsd:group ref="tns:ReservationInfoGroup" /> <xsd:element name="detailedPath" type="tns:DetailedPathType" /> </xsd:sequence> </xsd:complexType> <xsd:complexType name="DetailedPathType"> <xsd:sequence> <xsd:element name="providerNSA" type="types:NsaIdType" /> <xsd:element name="connectionId" type="tns:ConnectionIdType" /> <xsd:element name="connectionState" type="tns:ConnectionStateType" /> <xsd:element name="pathList" type="tns:PathListType" minOccurs="0" /> </xsd:sequence> <xsd:attribute name="order" type="xsd:int" /> </xsd:complexType> <xsd:complexType name="PathListType"> <xsd:sequence> <xsd:element name="path" type="tns:ComponentPathType" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:complexType name="ComponentPathType"> <xsd:sequence> <xsd:element name="directionality" type="tns:DirectionalityType" default="Bidirectional"/> <xsd:element name="sourceSTP" type="tns:ServiceTerminationPointType" /> <xsd:element name="destSTP" type="tns:ServiceTerminationPointType" /> <xsd:element name="stpList" type="tns:StpListType" minOccurs="0" /> <xsd:element name="children" type="tns:ChildListType" minOccurs="0" /> </xsd:sequence> <xsd:attribute name="order" type="xsd:int" /> </xsd:complexType> <xsd:complexType name="ChildListType"> <xsd:sequence> <xsd:element name="child" type="tns:DetailedPathType" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType>

1 0