December 2009 - Nsi-wg - lists.ogf.org

vote on naming for Agents types
by Guy Roberts 22 Dec '09

22 Dec '09

Hi All, On the latest NSI conference call we have been pondering a suitable name for the two instances of an Agent that resides on either end of a Network Service Interface. Up to now the term 'Requestor Agent' has been used to identify the agent that originates the connection request, and 'Provider Agent' for the agent that processes (reserves, provisions etc) the request. Objections have been raised to this terminology based on the desire to break away from the old use of 'provider' as used in ISP. We would like to hold a ballot in the NSI group for preferred name. The following names have been suggested, please respond with an email to me with the number of your preferred choice. 1. Requestor Agent, Provider Agent 2. Requestor Agent, Service Agent 3. Requestor Agent, Granter Agent 4. Requestor Agent, Implementer Agent 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 ------------------------------------------------------------------------------------------------------------------

9 8

new outline of architecture doc
by John Vollbrecht 18 Dec '09

18 Dec '09

Attached is a revised outline of architecture doc. I list the sections below. The doc has some detail about what might be in each section. Comments are most welcome. Also volunteers to write portions. Thanks for your review. John The idea is to describe step by step pieces of the architecture. Each section (after the first 2) has some implications for the interface that will be included. 1. Abstract and Summary 2. Context and Motivation 3. NS Interface concepts and terminology [define NSI in general and Transport /NSI ] 4. NSI Transport Service Description [define Transport Service offerred over the interface] 5. Transport Service actors [define actor with multiple agents] 6. Interoperating Transport Actors [describe multiple actors] 7. Infrastructures of NS Actors (describe different types of multi- actor infrastructures) Appendix - compare architecture capabilities of existing implementations vs architecture

1 0

AutoBAHN reservation protocol
by michalb＠man.poznan.pl 17 Dec '09

17 Dec '09

Hello All, AutoBAHN reservation protocol attached. Best regards, Michal

1 0

Sessions for OGF28
by Guy Roberts 17 Dec '09

17 Dec '09

Hello all, I have requested 4 sessions for the NSI group at OGF28. The first will be an introduction for newcomers and status update. The remaining 3 sessions will be for detailed working group discussions. A more detailed agenda for the working will be provided closer to the meeting date. OGF28 will be held in Munich on March 15-19. Keep an eye on the OGF website for the times of these NSI sessions - timeslots will be assigned a few weeks before the meeting. 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 conference call minutes
by Guy Roberts 16 Dec '09

16 Dec '09

Hello all, The minutes for today's NSI conference call are available here: http://forge.gridforum.org/sf/go/doc15838?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

Call tomorrow
by John Vollbrecht 15 Dec '09

15 Dec '09

We have a call tomorrow at 9 ET Call infoCall: +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 I suggest the following agenda 1) discuss creating topics for research group - place holder for things we want to hold for later conversation 2) discuss issues I sent out in earlier email - a) naming of agents on either side of NSI and b) end points of transport in group controlled by NMA 3) discuss the revised outline attached below - this is slightly revised from outline we worked out at Banff assign primary authors 4)plan next call -- I suggest Jan 13 with goal to get a document in place for review by then This is very big agenda, so we will need to limit conversation and perhaps take it to the list in order to get through it (I am not sure we are able to do this :( ) John

1 0

NSI - Call Issues
by John Vollbrecht 15 Dec '09

15 Dec '09

We will have a call tomorrow at 9ET. I suggest that this be the last call this year and that we restart calls either Jan 6 or Jan 13. We can continue exchanges on skype and by email during this time. I would like to try to have a skeleton document to start discussing by the middle of January and a document for OGF ready by early February. To do this we will have to make some assignments tomorrow or soon after, and probably work in smaller groups to come up with wording. I have two issues that need to be decided for the document. 1) Naming of two sides of NSI interface. We originally named these the requestor agent and network service agent. This after significant discussion, especially about the fact that we should not use provider because it had connotations of the commercial providers. Later we decided to go ahead and use the name provider because Network Service Agent was confusing with other names like Network Service Actor. Also requestor and provider are terms used by others so seemed reasonable. The person who was most strongly against using the name provider was not on the call when we made the decision to change, and he continues to feel strongly that it is a bad name. I think we made a decision not to use provider and should not change it without agreement from the parties involved in the decision. Therefore I would like to change the name of different sides of the NSI to something else. Suggestions are a) requester agent- service agents, b) client agent - server agents. We need to determine the name in order to make the document. I think this is a NSI group decision, and I am hoping we can decide tomorrow. 2) There is an issue with naming end points on the transport resource controlled by an NSA. To explain- A NS Service agent deals with connections between ports. In NML terms the ports are part of a group of connected links and nodes. The edge of the group might be a node or a link. The problem is that in NML terms a link does not have a port. So we need to have a different name for the end points of connections. I think the options are make up a NSI name for the end points, or to have NML define a name. A couple issues with possible solutions. a) If NSI define a name for endpoints then it will have to map back to NML concept for port in case of node and I am not sure what for a link. b) if NML were to say that both links and nodes have ports, then node ports would not be physical, or perhaps they would be defined by a connector at the physical layer. I note that in G.800 both links and nodes have ports, and where ports are connected there is a point. This seems useful when saying that segments are connections between ports and segments are concatenated at points. I am not sure how it fits with other NML concepts. This seems a decision that needs input from NML to decide. Probably this will take some discussion and we may have to have interim names till we decide. -- I would like to talk about these on the call tomorrow. We can continue online if needed. I will send a second email will a proposed outline of a architecture doc and call info. Let me know if you have suggestions for other agenda items. John

4 4

Meeting: {NSI Protocol} December 14, 2009 06:00 AM America/Los_Angeles {3338}
by Chin Guok 14 Dec '09

14 Dec '09

Chin Guok has modified a Cisco MeetingPlace Meeting. Date/Time: December 14, 2009 at 06:00 AM America/Los_Angeles Length: 120 (minutes) Frequency: This occurrence of the meeting only. Meeting ID: 3338 Meeting Password: Phone Number: 510-665-5437 TO ATTEND THE WEB CONFERENCE AND THEN JOIN WITH AUDIO: 1. Go to: http://abm.es.net/a/c3bc354d6276705a6a3908dcea2108cd 2. Sign in as a Guest or with your Cisco MeetingPlace User ID, and click on Attend Meeting. 3. Click on CONNECT and enter your phone and click OK. The system will now call you. TEST YOUR BROWSER BEFORE YOU ATTEND YOUR FIRST WEB CONFERENCE Visit http://abm.es.net to test your web browser for compatibility with the web conference.Follow this link to your home page,change to your preferred language and look for the browser test link at the bottom of the page. For more information about Cisco MeetingPlace including Meeting Tips and FAQ's, please visit http://abm.es.net/mpweb/html/help/000/output/index.html

1 0

Meeting: {NSI Protocol} December 14, 2009 06:00 AM America/Los_Angeles {3338}
by Chin Guok 14 Dec '09

14 Dec '09

Chin Guok has modified a Cisco MeetingPlace Meeting. Date/Time: December 14, 2009 at 06:00 AM America/Los_Angeles Length: 120 (minutes) Frequency: This occurrence of the meeting only. Meeting ID: 3338 Meeting Password: Phone Number: 510-665-5437 TO ATTEND THE WEB CONFERENCE AND THEN JOIN WITH AUDIO: 1. Go to: http://abm.es.net/a/c3bc354d6276705a6a3908dcea2108cd 2. Sign in as a Guest or with your Cisco MeetingPlace User ID, and click on Attend Meeting. 3. Click on CONNECT and enter your phone and click OK. The system will now call you. TEST YOUR BROWSER BEFORE YOU ATTEND YOUR FIRST WEB CONFERENCE Visit http://abm.es.net to test your web browser for compatibility with the web conference.Follow this link to your home page,change to your preferred language and look for the browser test link at the bottom of the page. For more information about Cisco MeetingPlace including Meeting Tips and FAQ's, please visit http://abm.es.net/mpweb/html/help/000/output/index.html

1 0

Meeting: {NSI Protocol} December 14, 2009 06:00 AM America/Los_Angeles {3338}
by Chin Guok 14 Dec '09

14 Dec '09

Chin Guok has modified a Cisco MeetingPlace Meeting. Date/Time: December 14, 2009 at 06:00 AM America/Los_Angeles Length: 120 (minutes) Frequency: This occurrence of the meeting only. Meeting ID: 3338 Meeting Password: Phone Number: 510-665-5437 TO ATTEND THE WEB CONFERENCE AND THEN JOIN WITH AUDIO: 1. Go to: http://abm.es.net/a/c3bc354d6276705a6a3908dcea2108cd 2. Sign in as a Guest or with your Cisco MeetingPlace User ID, and click on Attend Meeting. 3. Click on CONNECT and enter your phone and click OK. The system will now call you. TEST YOUR BROWSER BEFORE YOU ATTEND YOUR FIRST WEB CONFERENCE Visit http://abm.es.net to test your web browser for compatibility with the web conference.Follow this link to your home page,change to your preferred language and look for the browser test link at the bottom of the page. For more information about Cisco MeetingPlace including Meeting Tips and FAQ's, please visit http://abm.es.net/mpweb/html/help/000/output/index.html

1 0