Subject: [ieee-ietf-coord] more detailed agenda

From: "Romascanu, Dan (Dan)" <[email-masked]>
Date: Thu, 2 May 2013 17:46:14 +0000

An updated agenda with some more details for the virtual meeting that starts in 15 min

1. Roll Call, Agenda Bashing, Minutes Approval

The draft minutes of the 3/16 face-to-face meeting are available at 
http://www.iab.org/wp-content/IAB-uploads/2013/01/2013-03-16-ietf-ieee-minutes.txt. 

2. Review of Other Action Items from Previous Meetings (not part of the 
shared items list)

  The group agreed to have two virtual meetings before the end of July; 
  Dan Romascanu will send out a poll to select the meeting dates - Done

  The coordination team will discuss scheduling the next face-to-face 
  meeting, desirably during 2014 - In progress

  ...

  Spencer Dawkins will add text to 4441rev regarding dual-use 
  Registries - to be addressed at #4

  The IEEE 802 EC will change the order in which registry information is 
  added to 802 documents in order to allow more time to deal with dual-
  use registry issues. - ?

3. IETF Tutorial at the July IEEE 802 Plenary

4. RFC 4441bis - status report presented by Spencer

5. Areas of shared interest between the IETF and IEEE 802.  Review of 
the list of items, status and action items - discussion led by Pat and 
Dan

6. Candidate activities for inclusion on the list: 
- 6tsch

The Working Group would focus one enabling IPv6 over the TSCH mode of the IEEE802.15.4e standard.

If formed, the working group will define an open standard-based architecture that covers the formation and the operation of a wireless mesh based on the TSCH technology, and the aggregation of multiple meshes over a high speed backbone, including security, link management for the IPv6 network layer consumption, peer management and routing. The group will document best practices, and standardize the missing components to achieve industrial-grade criteria for jitter, latency, scalability and reliability.

In particular the group will define how packets that belong to a deterministic IPv6 flow are marked and routed or forwarded over the mesh within jitter and latency budgets.  When possible, the group will reuse existing protocols such as IPv6 ND, RPL and 6LoWPAN with the minimum adaptation required to meet criteria for reliability and determinism within the mesh, and scalability over the backbone.

The WG will focus on three scheduling models: 
- a centralized route computation that builds and maintains the communication schedule, and distributes it to the nodes. 
This schedule includes forwarding information associated to time slots;  RPL operations only apply to emergency repair actions when the reference topology becomes unusable.
- a distributed resource reservation and signaling protocol that establishes tracks between source and destination nodes along  multi-hop routes identified by RPL.
- a best effort resource allocation that is used to transport data frames on a per hop basis in the absence of a reservation protocol.

Mail list https://www.ietf.org/mailman/listinfo/6tsch
- drafts and other documents are centralized at https://bitbucket.org/6tsch

Owners: Adrian, Ted

- 6lo

- CAPWAP extensions in OPSAWG

https://datatracker.ietf.org/doc/draft-chen-opsawg-capwap-extension/
https://datatracker.ietf.org/doc/draft-shao-opsawg-capwap-hybridmac/
https://datatracker.ietf.org/doc/draft-zhang-opsawg-capwap-eap/

- rfc5342bis

https://datatracker.ietf.org/doc/draft-eastlake-rfc5342bis/

7. Review of Action Items, date of the next virtual meeting