[Nml-wg] Meeting notes conf call 2010-12-02

[Freek Dijkstra]

Conference call Thu December 2, 2010

Participants:
=============
Aaron Brown - I2
Freek Dijkstra - SARA
Chin Guok - ESnet
Jeroen vd Ham - U Amsterdam
Marcos Portnoi - U Delaware
Guy Roberts - DANTE
Jason Zurawski - I2
Inder Monga - ESnet

Agenda:
=======
- Tasklist as decided on OGF30
- Announcements on Geant3 (Freek)
- Status of urn:ogf
- VLAN description volunteers?
- Go through the 5 questions on identifiers
- Test some whiteboard software


Action Items (Revised 2010-12-02)
=================================
* Revise definition of multiplexing: Freek, Jeroen
* Setup a teleconference: Jeroen
* Specs for delegation of urn:ogf namespace: Freek, Richard, Joel Replogle
* Specs for urn:ogf:network identifiers: Freek
* Propose description of multicast and broadcast links: Richard, Freek,
<need extra volunteer>
* Create example of adaptation on Port/Link, and add to subversion:
Jeroen, Jason
* Given example of serial compound links with and without cross connect:
Freek
* How to specify properties of relations: <question postponed>
* Give examples (with numbers and next) how to specify the order of XML
elements: Aaron
* Request NSI requirements/solutions for channels and labels: Freek
* Jason will reserve the whiteboard facility at
http://internet2.na6.acrobat.com/venus during NML calls

Notes
=====

VLANs:
Freek has some ideas how to describe VLANs, but needs volunteers to help
think about it (hard is to define the logic and scalability.)
Guy: NSI is only point-to-point
VLANs needed for AutoBAHN
cNIS interpretation: does not touch on multi-point to multipoint

Adaptation on Port/Link:
Jason and Jeroen created examples.
Jeroen needs some more iterations
Jason: we will add the examples to the nml-base repository, for new
example document.

GFD publication process:
Jeroen - frustrated with information document publication process. took
long for public comments, no public comments, period ended but no action.
Guy has the same experience
Guy advises to apply pressure to Joel and Greg, with him and Richard
Hughes-Jones on the cc.
Joel Replogle is administrative responsible (assigning GFD numbers,
website, etc.)
Greg Newby is responsible for reviews and document contents.

Subversion:
A commit message to the mailing list is considered useful

Ordering in XML/RDF:
Three options:
  - use document order (not in XML spec, so not always reliable)
  - add order number to elements
  - refer to "next" element

Channels:
The question is how to use describe multiple labels to make NML more
scalable. Eg. how to describe 4000 VLANs between two domain, without
actually describing 4000 links and 2*4000 ports.
Guy: NSI Distinguishes between capability and configuration.
For capability, NSI advertises range of VLANs on a port, labels
For configuration, NSI advertises SDP/STP for each VLAN.
Concept of capability: format as list or range
Concept of circuits: format as SDP.
Physical instance can have multiple potential "SDPs"
Tomohiro mailed Freek a slide deck of ~20 slides, but this needs to be
condensed into clear requirements.
Freek will formally mail the NSI list requesting input.

GEANT3:
GEANT really wants the NML work and expects to provide more input (SA2
and JRA2).
Current discussion is who is going to provide this input and how.
Richard, Guy and Freek think that it best to make two people active in
the NML-WG, rather than making a working group in the GEANT3 project,
which will make a requirement document and sent that the NML-WG.
According to Freek, that is too late in the process, the scope and
requirements are there, we're now fine-tuning the schema, making sure it
will be useful.

Questions on Identifiers:
No more feedback than what was already given by Jeroen and Jason.

Adobe whiteboard software:
Works pretty good. Can be used for technical discussions. Jason will
reserve it for NML calls.