May 2012 - Nsi-wg - lists.ogf.org

Issue 56 in ogf-nsi-project: Overloaded usage of 'Provisioned' state
by ogf-nsi-project＠googlecode.com 19 Sep '12

19 Sep '12

Status: Accepted Owner: tkudoh...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.1 FixedInVersion-2.0 New issue 56 by guy.robe...(a)gmail.com: Overloaded usage of 'Provisioned' state http://code.google.com/p/ogf-nsi-project/issues/detail?id=56 Description of Issue: In the state machine defined in NSI v1.1, the 'Provisioned' state is overloaded. Two meanings are associated with this state: 1. All child NSAs have acknowledged receipt of the provision command 2. All child NSAs have confirmed provisioning complete Discussion of Issue: Should we refine the state-machine to disambiguate these two different understandings of 'Provisioned'. A proposal has been made to add a new message 'Connection-State up'. Resolution of Issue:

1 1

Re: [Nsi-wg] Issue 32 in ogf-nsi-project: Interface version discovery
by ogf-nsi-project＠googlecode.com 16 Sep '12

16 Sep '12

Comment #3 on issue 32 by guy.robe...(a)gmail.com: Interface version discovery http://code.google.com/p/ogf-nsi-project/issues/detail?id=32 John M. has some ideas ... John to write-up a proposal.

1 2

Re: [Nsi-wg] Issue 24 in ogf-nsi-project: ServiceException needs further details
by ogf-nsi-project＠googlecode.com 16 Sep '12

16 Sep '12

Comment #6 on issue 24 by imo...(a)gmail.com: ServiceException needs further details http://code.google.com/p/ogf-nsi-project/issues/detail?id=24 Discussion on the Wed call 1. rename messageId to errorId 2. Appendix captures a list of errorId values and their meanings 3. errorId and text are both fields that are included by the entity Inder

1 3

Re: [Nsi-wg] Issue 39 in ogf-nsi-project: STP syntax
by ogf-nsi-project＠googlecode.com 16 Sep '12

16 Sep '12

Comment #2 on issue 39 by jmacau...(a)gmail.com: STP syntax http://code.google.com/p/ogf-nsi-project/issues/detail?id=39 I am confused by this agreement. An STP is defined as a OGF URN that is composed of the NSnetwork and localId already. Is this asking me to break out the STP into two discrete elements?

1 4

Topology section
by Jeroen van der Ham 31 May '12

31 May '12

Hi all, I've made a start on the topology section for the NSI v2.0 document. It's not finished yet, but at least it contains some start. Unfortunately, I'll be on holiday next week, so I won't be able to further write on this. If others feel they can contribute, please do so. The document is available for reading at: https://docs.google.com/document/d/1HIo7uQl7DbTe_y-cnPOrqDkspoRBaTKVVrrldUR… Guy should be able to give out edit access rights too. Jeroen.

6 21

STP lists and path ordering
by John MacAuley 30 May '12

30 May '12

This one has to do with whether the existing STP list with ordering information is sufficient to understand the path a service should take, or has been computed to take. I have included the basic schema for reference. As an example let us use a connection request through three domains (A, B, and C) with source STP A1 and destination STP C2. Let us assume that the chosen path is A1->A2->B1->B2->C1->C2. With the existing schema definitions we would get something like this: { sourceSTP=A1 destSTP=C2 stpList={ (1,A2), (2,B1), (3,B2), (4,C1) } } If I remember correctly, the issue we have was that this model is: 1. There is an assumption that sourceSTP A1 is the edge of the connection, and routing will proceed inside domain A, not immediately to the domain adjacent to STP A1. 2. Assumes because A1 and A2 are in the same domain the connection is routed internally to that domain. 3. Assumes that when two STP are adjacent in the ordered list, but in different domains, that there must be an SDP between the two. For example, A2 and B1 must be topologically adjacent and share an SDP. So I guess the question is should we be using SDP here instead of STP? John. <xsd:complexType name="PathType"> <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:sequence> </xsd:complexType> <xsd:complexType name="StpListType"> <xsd:sequence> <xsd:element name="stp" type="tns:OrderedServiceTerminationPointType" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:complexType name="OrderedServiceTerminationPointType"> <xsd:sequence> <xsd:element name="stpId" type="tns:StpIdType" /> </xsd:sequence> <xsd:attribute name="order" type="xsd:int" /> </xsd:complexType>

3 6

Discussion on recursive queries
by Inder Monga 30 May '12

30 May '12

Please look at this presentation: https://docs.google.com/presentation/d/1_FqvdNfqwa5Kn-4uV47OKEBmJWZ6GNktiFl… PDF attached for offline view. Inder -- Inder Monga 510-486-6531 http://www.es.net Follow us on Twitter: ESnetUpdates/Twitter <http://bit.ly/bisCAd> Visit our blog: ESnetUpdates Blog <http://bit.ly/9lSTO3><http://bit.ly/d2Olql>

1 0

Query types
by MacAuley, John (John) 30 May '12

30 May '12

Peoples, Can I propose we support three Query operation types? Currently we have two (Summary and Details) or which no one has implemented the recursive Details. I think we should revise the definition to the following: Summary - Will query reservation summary information held in the target NSA only. Details - Will query reservation detailed information held in the target NSA only. This will include child NSA connection segment information (new connectionId, path segment, etc.) and the target NSA's version of the connection segment state. Recursive - Will perform a recursive query to build detailed reservation information for all child NSA involved in the connection path. Sound good? John.

4 13

tomorrow's NSI conf call
by Guy Roberts 29 May '12

29 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: * tba 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 _____________________________________________________________________

1 0

NSI call Wednesday
by Guy Roberts 15 May '12

15 May '12

Hello Tomohiro, Inder, I will be in meetings on Wednesday, so won't make our weekly call. Would you be able to host this call? 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