[Nml-wg] Notes from call March 8

[Jeroen van der Ham]

Notes for NML call March 8
==============================

Attendance: Aaron Brown (I2), Freek Dijkstra (SARA), Chin Guok (ESNet), Roman Łapacz (PSNC), Jeroen van der Ham (UvA)
Excused: Jason Zurawski

1. Action items from previous call:
-----------------------------------
* Freek to write use case on bidirectional and unidirectional links:
single fiber with two wavelengths in different directions.
* Jerry to write use case on bidirectional and unidirectional links
* Jerry to write usecase on NORDUnet being a geographical segregated
network (NY and CPH), with possible restrictions between the two
locations/networks
* Jerry to write this down federated and sub-NSA as a use case.
* Freek and Jerry look at the exact definition of NML:Topology and NSI
Network, and see if they can sync their definition
* Jeroen to move schema figure and check definitions
* Freek to check "at layer" relation and "Layer" object
* Jeroen to fix the identifiers section
* Jeroen to write the security considerations section (DONE!)
* Freek to provide link on book identifiers (DONE!)

We go through the items in a semi-random order:
- Freek to provide link on book identifiers
Done, we will present this also to the NSI as food for thought.

- Jeroen to write the security considerations section
Done, everyone agrees to the wording.

- Jeroen to move schema figure and check definitions
In progress. Jeroen notes that the document is not consistent currently with the wording of relations. Sometimes camelCase is used, other times written as separate words (located at). Group agrees that it should be camelCase. Jeroen to update the document accordingly.
Rest of checking is still in progress.

* Freek and Jerry look at the exact definition of NML:Topology and NSI
Network, and see if they can sync their definition
Done. Freek sent a summary to the list regarding recursive topologies. This will be discussed in more detail at the OGF.

* Versioning
Freek brought this issue up, Jason noted in an email that any proposal should be backed by examples and use-cases, which we all agree to. Freek will present this at OGF.

* LifeTime element
On the mailinglist there has been some discussion regarding the LifeTime document. 
Aaron mentions two use-cases: 
 - Part of a reservation in IDC is expressed as a Link which is then implemented on several physical links. This object has a LifeTime associated with it to express the duration of the reservation.
 - The Reservable bandwidth can be expressed in a similar way to describe available bandwidth at certain times.
Jeroen also mentions the Virtual Machines on for example PlanetLab. These are reservable resources, with a certain lifetime associated with it.

- Freek to write use case on bidirectional and unidirectional links:
single fiber with two wavelengths in different directions.
Freek has sent an email to the list describing a FttH use-case. This will be saved for a later date to check how the eventual schema stacks against use-cases.

- We discuss the agenda for the OGF, we have three sessions:
1) NML - NSI session, to present our work to NSI.
2) Example discussion session: Topology recursion, VLAN descriptions and LifeTime
3) Overflow and writing.

- Next call is in two weeks at the same time (16:00 UTC)

Action points for next call:
* Jeroen updates relations to camelCase
* Jeroen to check definitions in schema document
* Jeroen to fix the identifiers (sub)sections
* Freek to check "at layer" relation and "Layer" object
* Jerry to write use case on bidirectional and unidirectional links
* Jerry to write usecase on NORDUnet being a geographical segregated
network (NY and CPH), with possible restrictions between the two
locations/networks
* Jerry to write this down federated and sub-NSA as a use case.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 235 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.ogf.org/pipermail/nml-wg/attachments/20120308/5715d1c0/attachment.pgp>