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

Re: [Nsi-wg] Issue 26 in ogf-nsi-project: UUID format for ConnectionId
by ogf-nsi-project＠googlecode.com 24 Jan '12

24 Jan '12

Comment #2 on issue 26 by guy.robe...(a)gmail.com: UUID format for ConnectionId http://code.google.com/p/ogf-nsi-project/issues/detail?id=26 Jerry: the discrepancy is not a problem, so everything stays unchanged.

1 3

Re: [Nsi-wg] Issue 17 in ogf-nsi-project: minn/Max bandwidth
by ogf-nsi-project＠googlecode.com 24 Jan '12

24 Jan '12

Comment #2 on issue 17 by jmacau...(a)gmail.com: minn/Max bandwidth http://code.google.com/p/ogf-nsi-project/issues/detail?id=17 At the moment we return a reservationInfo structure in the reserveConfirmed message to let the requesting NSA know which parameters were selected by the provider for the reservation. With min/desired/max bandwidth in the reserve request, where do we put the actually commited bandwidth rate? So we say it comes back in the desired fields, or should we define a new structure for this in the confirmed response?

1 3

Re: [Nsi-wg] Issue 33 in ogf-nsi-project: getting WSDL from servers
by ogf-nsi-project＠googlecode.com 18 Jan '12

18 Jan '12

Updates: Labels: -FixedInVersion-1.1 FixedInVersion-2.0 Comment #4 on issue 33 by guy.robe...(a)gmail.com: getting WSDL from servers http://code.google.com/p/ogf-nsi-project/issues/detail?id=33 GR: some question about real benefit of this - coding needed to to use WDSL TK: this is needed to be a real Web-service compliant solution. Resolution: re-visit in release 2.0

1 2

Re: [Nsi-wg] Issue 15 in ogf-nsi-project: XML/WSDL name spaces documentation needed
by ogf-nsi-project＠googlecode.com 18 Jan '12

18 Jan '12

Updates: Status: Started Comment #3 on issue 15 by guy.robe...(a)gmail.com: XML/WSDL name spaces documentation needed http://code.google.com/p/ogf-nsi-project/issues/detail?id=15 Henrik : please add examples of SOAP payloads so that it is possible for the coder to see what is required to be sent to aid the development of new implementations. John to provide Guy with examples for documentation purposes

1 2

Re: [Nsi-wg] Issue 51 in ogf-nsi-project: run NTP on NSA hosts
by ogf-nsi-project＠googlecode.com 12 Jan '12

12 Jan '12

Updates: Summary: run NTP on NSA hosts Labels: -FoundInVersion-1.0 FoundInVersion-1.sc Comment #1 on issue 51 by guy.robe...(a)gmail.com: run NTP on NSA hosts http://code.google.com/p/ogf-nsi-project/issues/detail?id=51 Assigned to Guy Roberts to update documentation to reflect this.

1 1

Issue 50 in ogf-nsi-project: Pathfinding functionality review
by ogf-nsi-project＠googlecode.com 12 Jan '12

12 Jan '12

Status: New Owner: guy.robe...(a)gmail.com Labels: Type-Review Priority-Medium FoundInVersion-1.0 FixedInVersion-1.1 New issue 50 by guy.robe...(a)gmail.com: Pathfinding functionality review http://code.google.com/p/ogf-nsi-project/issues/detail?id=50 Description of Issue: Pathfinding. Currently the 'network-internal' path-finding is delegated to the network - this is not currently exported - how should this be done? TK: Static vs. dynamic information - topology is more static, connections and vlans are more dynamic. To scale well these should be handled in different ways. JS: Jeroen: Also an issue with vlan blocking found at Netherlight... this also needs to be solved. 'Label' (vlan) swapping needed based on negotiation between neighbouring networks. Jerry: negotiation in tree mode happens at RA when it has decided which connections point is needed. Jeroen: This means that we need some vlan information in NSI request. Jeroen: one STP per vlan does not scale. Jeroen: we need to have a way in the topology to express which vlans are available and which are not. Discussion of Issue: Resolution of Issue:

3 9

Re: [Nsi-wg] Issue 34 in ogf-nsi-project: time zones - document usage
by ogf-nsi-project＠googlecode.com 12 Jan '12

12 Jan '12

Updates: Status: Started Labels: FixedWithUpdateR6 Comment #3 on issue 34 by jmacau...(a)gmail.com: time zones - document usage http://code.google.com/p/ogf-nsi-project/issues/detail?id=34 Changed times in the form xsd:DateTime to be a new simpleType called DateTimeType that restricts dates to have a timezone or Z. This was done in update r6. Guy will need to update the CS protocol documentation to reflect the restriction. ------------------------------------------------------------------------ r6 | jmacauley(a)gmail.com | 2011-10-14 17:03:57 -0400 (Fri, 14 Oct 2011) | 1 line Changed times in the form xsd:DateTime to be a new simpleType called DateTimeType that restricts dates to have a timezone or Z as requested in issue #34. closing issue #34. ------------------------------------------------------------------------

1 2

Re: [Nsi-wg] Issue 38 in ogf-nsi-project: push/pop attributes from SOAP layer - documenation
by ogf-nsi-project＠googlecode.com 12 Jan '12

12 Jan '12

Updates: Labels: -Type-Defect Type-Documentation Comment #6 on issue 38 by jmacau...(a)gmail.com: push/pop attributes from SOAP layer - documenation http://code.google.com/p/ogf-nsi-project/issues/detail?id=38 Changed this to a documentation update.

1 2

Re: [Nsi-wg] Issue 23 in ogf-nsi-project: "NsiExceptionType" change to "serviceException"
by ogf-nsi-project＠googlecode.com 12 Jan '12

12 Jan '12

Updates: Status: Fixed Labels: FixedWithUpdateR5 Comment #4 on issue 23 by jmacau...(a)gmail.com: "NsiExceptionType" change to "serviceException" http://code.google.com/p/ogf-nsi-project/issues/detail?id=23 Renamed NsiExceptionType to ServiceExceptionType as per issue #23. Closing issue #23. ------------------------------------------------------------------------ r5 | jmacauley(a)gmail.com | 2011-10-14 16:30:54 -0400 (Fri, 14 Oct 2011) | 1 line Renamed NsiExceptionType to ServiceExceptionType as per issue #23. Renamed messageId to errorId in ServiceExceptionType as per Issue 24. Renamed ServiceException element to ServiceException as per issue #27. Closing issues #23 and #27. Updating issue 24 ------------------------------------------------------------------------

1 2

Re: [Nsi-wg] Issue 2 in ogf-nsi-project: GenericAcknowledgmentType
by ogf-nsi-project＠googlecode.com 12 Jan '12

12 Jan '12

Comment #11 on issue 2 by imo...(a)gmail.com: GenericAcknowledgmentType http://code.google.com/p/ogf-nsi-project/issues/detail?id=2 This was re-discussed on the Wed. call, with the following results: 1. Message transport layer takes care of ack retransmission in case of a packet loss. 2. Confirm/Fail message responses should be sent out without waiting on the receipt of the message ack. [comment on error recovery: if message transport layer is broken, say unidirectionally, the ack sending will eventually timeout and generate a message transport error that the NSA will need to handle] 3. From the receiving state machine perspective, receiving a confirm/fail message from a particular NSA should cancel out the need to receive an ACK. So the state machine should not only continue to process the confirm/fail message, but not gate on or wait for the ACK message. Hope this resolves this issue

1 2