February 2010 - Nsi-wg - lists.ogf.org

NML topology
by John Vollbrecht 09 Mar '10

09 Mar '10

Attached is set of ppt slides to describe interdomain topology. I hope this helps - it is based on conversations in the NML group, and is my understanding of what the Glossary of terms that Guy is reviewing (and I think will review next Wed). I will be on vacation in Israel for the next couple weeks, and I don't expect to get much internet access. Perhaps some, but I don't count on it. I will be back and would like to have a call the week before OGF, and I will be there. I hope this helps. I think it needs to be discussed with NML group after it is is discussed in NSI. John

12 31

Re: [Nsi-wg] Google document for NSI architecture requiremnt capture
by Guy Roberts 26 Feb '10

26 Feb '10

Hello All, There is a mistake in the link for the NSI requirement Google document - here is the correct link: NSI Requirement Capture: http://docs.google.com/Doc?docid=0AZTOJNVUoixhZGZ4cjRiemtfMzQyaGZtOG4yZ2o&h… Guy From: Guy Roberts Sent: 26 February 2010 12:44 To: NSI WG Subject: Google document for NSI architecture requiremnt capture Hello All, As discussed in the last call I would like to refine our working processes to improve the productivity of the group. I note that over the past year I have accumulated more than 1000 emails on NSI discussions and minutes for 80 hours or more of discussions in meetings and conference calls - these contributions have been a fantastic contribution that has really led to a great analysis and refinement of the NSI concepts. To help summarize this information into a clear set of NSI requirements I have created a new Google document. This is designed to complement the existing 'Glossary of NSI terms'. This 'NSI Requirement Capture' document is intended to be a communal document where everyone can review the current NSI requirements and add their own additions and comments. I have kicked this off this with what I believe to be a summary of the basic NSI requirements. You can edit both documents here: Glossary of NSI definitions: http://docs.google.com/Doc?docid=0Ac4ZeyIu2P2YZGhrNHRtdjJfOTNkdzViZndmaw&hl… NSI requirement capture: http://docs.google.com/Doc?id=dfxr4bzk_342hfm8n2gj My intention is that the Glossary will be a list of 'defined' NSI words with a minimal definition for each term. Since this is a working document, these may be refined or added to over time. The requirements document is intended to be a place where well characterized requirements (requirements that can be implemented and measured) are gathered. This is also a working document, and requirements will be refined or added to over time. I would encourage you all to take a look at both documents and make contributions. Guy ------------------------------------------------------------------------------------------------------------------ Guy Roberts, Ph.D Network Engineering & Planning DANTE - www.dante.net<http://www.dante.net/> Tel: +44 (0)1223 371 316 City House, 126-130 Hills Road Cambridge, CB2 1PQ, UK ------------------------------------------------------------------------------------------------------------------

1 0

Google document for NSI architecture requiremnt capture
by Guy Roberts 26 Feb '10

26 Feb '10

Hello All, As discussed in the last call I would like to refine our working processes to improve the productivity of the group. I note that over the past year I have accumulated more than 1000 emails on NSI discussions and minutes for 80 hours or more of discussions in meetings and conference calls - these contributions have been a fantastic contribution that has really led to a great analysis and refinement of the NSI concepts. To help summarize this information into a clear set of NSI requirements I have created a new Google document. This is designed to complement the existing 'Glossary of NSI terms'. This 'NSI Requirement Capture' document is intended to be a communal document where everyone can review the current NSI requirements and add their own additions and comments. I have kicked this off this with what I believe to be a summary of the basic NSI requirements. You can edit both documents here: Glossary of NSI definitions: http://docs.google.com/Doc?docid=0Ac4ZeyIu2P2YZGhrNHRtdjJfOTNkdzViZndmaw&hl… NSI requirement capture: http://docs.google.com/Doc?id=dfxr4bzk_342hfm8n2gj My intention is that the Glossary will be a list of 'defined' NSI words with a minimal definition for each term. Since this is a working document, these may be refined or added to over time. The requirements document is intended to be a place where well characterized requirements (requirements that can be implemented and measured) are gathered. This is also a working document, and requirements will be refined or added to over time. I would encourage you all to take a look at both documents and make contributions. Guy ------------------------------------------------------------------------------------------------------------------ Guy Roberts, Ph.D Network Engineering & Planning DANTE - www.dante.net<http://www.dante.net/> Tel: +44 (0)1223 371 316 City House, 126-130 Hills Road Cambridge, CB2 1PQ, UK ------------------------------------------------------------------------------------------------------------------

1 0

Glossary of NSI terms
by Guy Roberts 24 Feb '10

24 Feb '10

A document containing a glossary of terms used in NSI have been prepared and is available for comment in Google docs at the following location: http://docs.google.com/Doc?docid=0Ac4ZeyIu2P2YZGhrNHRtdjJfOTNkdzViZndmaw&hl… Comments should be entered by Wednesday 3rd March. Google docs does not support document tracking, so to help keep track of comments, could you please follow these rules: 1. Please make sure you are logged into gmail or another Google application so that we can track who has make edits. 2. Please use comments (Insert -> Comment) to add your comments, this will automatically add a user id and date. 3. If you wish to re-work a sentence, please add the new re-worded sentence in a comment so that we can see the original. Regards, Guy ------------------------------------------------------------------------------------------------------------------ Guy Roberts, Ph.D Network Engineering & Planning DANTE - www.dante.net<http://www.dante.net/> Tel: +44 (0)1223 371 316 City House, 126-130 Hills Road Cambridge, CB2 1PQ, UK ------------------------------------------------------------------------------------------------------------------

1 0

minutes from today's meeting
by Guy Roberts 24 Feb '10

24 Feb '10

The minutes from today's NSI conference call are available here: http://forge.gridforum.org/sf/go/doc15887?nav=1 Guy ------------------------------------------------------------------------------------------------------------------ Guy Roberts, Ph.D Network Engineering & Planning DANTE - www.dante.net<http://www.dante.net/> Tel: +44 (0)1223 371 316 City House, 126-130 Hills Road Cambridge, CB2 1PQ, UK ------------------------------------------------------------------------------------------------------------------

1 0

glossary of terms
by Guy Roberts 24 Feb '10

24 Feb '10

Since OGF gridforge is down I have attached glossary document. Guy ------------------------------------------------------------------------------------------------------------------ Guy Roberts, Ph.D Network Engineering & Planning DANTE - www.dante.net<http://www.dante.net/> Tel: +44 (0)1223 371 316 City House, 126-130 Hills Road Cambridge, CB2 1PQ, UK ------------------------------------------------------------------------------------------------------------------

1 0

NSI Path/Connection manipulation and decomposition semantics (short)
by Jerry Sobieski 24 Feb '10

24 Feb '10

Can I propose some connection decomposition and manipulation semantics? Try these: Definition: A Service Termination/Transit Point "STP" identifies a location in the topology. STPs primarily denote a lowest level component of the topology where a service instance may begin, end, or transit. An STP may also identify a higher level topological construct where a service instance may begin, end, or transit. In the case of a higher level construct, the service instance may touch any sub-component to meet the termination or transit constraint. Definition: Given STPs A and Z, "A>Z" denotes a unidirectional Path beginning at A and ending at Z; Rule 1: Equivalence: Given two STPs J and K, If J==K ("J is topologically equivalent to K"), then K==J, and both identify the same location (object) in the topology. Rule 2: Concatenation: Given STPs A,M,N,,Z, a Connection C1:=(A>M), and a Connection C2:=(N>Z), then C1:C2 == (A>M):(N>Z) == (A>M>N>Z) "C1 concatenated with C2 is equivalent to ..." Implications: - If Connection A>M exists, and a Connection M>Z exists, Then by concatenation a Connection A>M>Z exists, and by implication A>Z exists. - Given J==K, then A>J == A>K; and (J>K)==J==K; - Given STPs A, M, N, and Z, If M==N, then (A>M):(N>Z) == A>M>N>Z == A>M>Z ==A>N>Z; Thoughts? Jerry

2 2

Wednesday's NSI conference call
by Guy Roberts 22 Feb '10

22 Feb '10

Hi All, The following is call information for Wednesday's NSI call -- same time as always. 9:00 ET, 14:00GMT. Call: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0155180 Agenda: Review glossary of NSI terms: http://forge.gridforum.org/sf/go/doc15885?nav=1 Review requirements for NSI topology modelling Guy ------------------------------------------------------------------------------------------------------------------ Guy Roberts, Ph.D Network Engineering & Planning DANTE - www.dante.net<http://www.dante.net/> Tel: +44 (0)1223 371 316 City House, 126-130 Hills Road Cambridge, CB2 1PQ, UK ------------------------------------------------------------------------------------------------------------------

1 0

context and motivation start
by John Vollbrecht 21 Feb '10

21 Feb '10

Attached is a draft of a possible context and motivation section. It needs to be discussed, edited, revised probably redone. I submit it as a strawman start for that section. John

1 0

Thoughts on a basic topology model for NSI
by Jerry Sobieski 17 Feb '10

17 Feb '10

Hi all- Relative to our brief discussion last week about topology and the NSI... We want the NSI to offer more power and options to the "user" - to break out of the traditional carrier models for interacting with the user. And I think our notions of Requesting aAgents and Providing Agents does that nicely and in a very elegant and scalable fashion. However, we still have a lot of discussion about pathfinding - about how the agents will go about decomposing a path request into sub-paths for tree or chain model processing, or how we decide which NRMs are responsible for a particular end point, etc. These all deal with *topology*. There are quite a few notions we take for granted that require some sort of topology model. For instance: a Service Termination Point. Whatever we end up caling it, the semantics of an STP is that it represents a point in the topology where a service connection can terminate. We talk about capturing path information for monitoring...that requires a notion of how the topology is defined. There are lots of topologically based assumptions we need to be more explicit about. So this set of slides tries to capture some thoughts of mine on how we can pose a simple minimalist topological model sufficient for our NSI purposes. I think it is consistent wth our thoughts and discussions. And while it may bump into things that the NML WG is considering, I doubt a) we have come up with anything conflicting, and b) we certanly have not gone to the details of how to describe or distribute a topology database - we just assume we have a TopoDB and that is contains these basic constructs. Comments are welcome...Its only a draft for consideration... Jerry While the NSI protocol itself does not impose a particular topology on the transport plane or the agents that manage it, we do impose some notions on the Connections we construct - e.g. that the NSAs will, as a group, be able to construct and reserve a suitable path for the request.

5 8