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

"optional" call Wed 8/12 at 9 ET
by John Vollbrecht 11 Aug '09

11 Aug '09

I apologize - I sent this to NML instead of NSI group - this is an NSI group call Wed - On Aug 10, 2009, at 12:48 PM, John Vollbrecht wrote: > We will have an optional call for discussing items in progress wed. > A week from tomorrow we will have a regular call. Both will use the > same call info > Call: +1-734-615-7474 (PSTN CALL-OUT DOES NOT WORK) or > +1-866-411-0013 (toll free US/Canada Only) > Enter access code: 0155180 > > Tentative agenda -- > > discuss relationships between NS agents - Joan, Tomohiro, Guy, John > discuss context for NSI -- Guy and others > discuss NML/ G.800 for NSI > > other? > > John >

1 0

Today's NSI-WG conf call minutes
by Guy Roberts 10 Aug '09

10 Aug '09

Hello All, The minutes from today's conf call are now available on gridforge: http://forge.gridforum.org/sf/go/doc15739?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 ------------------------------------------------------------------------------------------------------------------

3 5

G.805/G.800 applied to NSI
by Guy Roberts 05 Aug '09

05 Aug '09

John, See my comments in your G.805/G.800 document. I think that applying G.800 to a NSI network example as you have done here is an interesting exercise. I think the G.800 is a good model that looks well thought through and fits the NSI requirement for a vendor independent network description. G.800 is diagrammatic oriented, as far as I understand the use of this is that it can be used as an object oriented model for creating a database that describes a network in a network management system (TMN principles). But what we really need is a description language that will allow this network model to be exchanged over the NSI interface. I guess the process of creating such a language is the role of the NML group. As far as I can see ITU-T does not have anything like this for G.800 (because it is an object oriented database model only?). Perhaps Freek can comment on this in tomorrow's call. 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 ------------------------------------------------------------------------------------------------------------------

4 3

pointer to G.800 recommendation
by John Vollbrecht 04 Aug '09

04 Aug '09

http://www.itu.int/rec/T-REC-G.800/en The above is a pointer to the G.800 recommendation for transport networks. I had a hard tome finding it so I thought others might. It is the standards recommendation for describing a transport dataplane. It is the basis for what I described in attachment in the email I sent yesterday. John

1 0

call Wed 9 ET
by John Vollbrecht 04 Aug '09

04 Aug '09

I sent the original message to the wrong group -- sorry - This is for an NSI call Wed. -- John Begin forwarded message: > From: John Vollbrecht <jrv(a)internet2.edu> > Date: August 3, 2009 1:29:53 PM GMT-04:00 > To: Network Markup Language Working Group <nml-wg(a)ogf.org> > Cc: John Vollbrecht <jrv(a)internet2.edu> > Subject: call Wed 9 ET > > We will have a call Wed at 9 ET. A suggested agenda - > > 1. status document and plans > 2. ITU G.800 description -- see attached doc for description - > would be good to have table that maps G.800 and NML/NSI names > 3. context description for standard > > Some thoughts for context > > 1 - intent is to support Network Service Requestors and Agents that > may interoperate in different infrastructure modes, specifically a > Grid or VO mode where requestor knows the topology that of set of > networks, and network centric where user makes a request and the > network determines how to satisfy it possibly using other > collaborating networks > > 2- difference with GMPLS and ASON -- how it fits > > 3 - uses ITU G.800 data plane concepts - may modify names slightly > > 4- relation to IETF PCE > > 5 - relation to PerfSonar and NML > > 6 - security capabilities and limits > > Call info > +1-734-615-7474 (PSTN CALL-OUT DOES NOT WORK) or +1-866-411-0013 > (toll free US/Canada Only) > Enter access code: 0155180 > > > John > >

1 0