2016-02-01: Potential Areas for IETF/IEEE802 Coordination v19
slides-interim-2021-ietfieee-05-sessa-2016-02-01-potential-areas-for-ietfieee802-coordination-v19-00

Potential Areas for IETF/IEEE802 Coordination

0. Revision History
0.0 Initial Revision - 9/4/2012
0.1 revised for the period between 9/5 and 10/29
0.2 revised according to input received on 01, still reflects the 9/5-10/29
time interval 0.3 revised after the 10/29/12 meeting 0.4 revised for the period
between 10/29 and 12/12 0.5 revised after the 12/17/12 meeting 0.6 revised for
the period between 12/17/12 and 2/5/13 0.7 revised for the period between
2/5/13 and 4/30/13 0.8 revised after the 5/2/13 meeting 0.9 revised for the
period between 5/2/13 and 9/22/13 0.10 revised after the 9/30 meeting 0.11
revised for the period between 9/30/13 and 1/22/14 0.12 revised after the
1/27/14 meeting 0.13 revised after the 6/18/14 meeting 0.14 revised with
updates before the 9/29/14 f2f meeting 0.15 revised for the period between
9/29/14 and 1/20/15 0.16 revised for the period between 1/20/15 and 6/15/15
0.17 revised for the period between 6/16/15 and 8/12/15 0.18 revised for the
period between 8/12/15 and 12/15/15 0.19 revised for the period between
12/15/15 and 1/28/16

1. IETF TRILL Fine-grained labeling and IEEE 802.1 tags
1.1 Description - CLOSED

-------------------------------------------------------------------------

2. IETF BFD and IEEE 802.1AX
2.1 Description - CLOSED
(Note: draft-ietf-bfd-on-lags was approved by the IESG on 12/19/2013 and
published as RFC 7130)

-------------------------------------------------------------------------

3. IETF NVO3 and IEEE 802.1 DCB
3.1. Description
IEEE 802.1Qbg VDP might be used as the basis for the communication that
NVO may need between an end system and an external box (e.g. bridge or
router) doing the NVO encapsulation. Coordination will help determine if
VDP is a suitable candidate and possibly to make any amendment needed in
VDP for NVO usage.

Liaison statement from NVO3 to IEEE 802.1 - about http://
datatracker.ietf.org/doc/draft-ietf-nvo3-hpvr2nve-cp-req/. It was
discussed at the IEEE 802.1 interim meeting in May 2015. PAR and CSD for
802.1Qcn- Amendment, VSI/VDP extensions for NVO3 were submitted. A
formal response will be provided at the July Plenary meeting.  (DONE)

6/18: Pat Thaler reported that the project work is ongoing, and that
802.1 will likely send a liaison back to NVO3 after the July meetings.
She added that interim teleconferences will be used so that people can
participate without having to attend a lot of face-to-face meetings.

9/29: IEEE 802.1Qcn PAR approved in June
Jan. 2016: editors identified (Li Yijhou, Paul Bottorf)

3.2. Relevant Documents
https://datatracker.ietf.org/liaison/1219/
http://datatracker.ietf.org/wg/nvo3/charter/
http://datatracker.ietf.org/doc/draft-ietf-nvo3-overlay-problem-statement - RFC
7364 http://datatracker.ietf.org/doc/draft-ietf-nvo3-framework - RFC 7365
http://datatracker.ietf.org/doc/draft-ietf-nvo3-use-case
http://datatracker.ietf.org/doc/draft-ietf-nvo3-gap-analysis
http://datatracker.ietf.org/doc/draft-ietf-nvo3-arch/
http://datatracker.ietf.org/doc/draft-ietf-nvo3-nve-nva-cp-req/
http://datatracker.ietf.org/doc/draft draft-ietf-nvo3-dataplane-requirements
http://datatracker.ietf.org/doc/draft-ietf-nvo3-security-requirements/
https://datatracker.ietf.org/doc/draft-ietf-nvo3-geneve/
https://datatracker.ietf.org/doc/draft-ietf-nvo3-vxlan-gpe/
http://datatracker.ietf.org/doc/draft-ietf-nvo3-hpvr2nve-cp-req/
http://ieee802.org/1/files/public/docs2015/cn-thaler-Qcn-draft-PAR.pdf
http://ieee802.org/1/files/public/docs2015/cn-yizhou-qbg-ext-for-nvo3-csd-v03.pdf
https://datatracker.ietf.org/liaison/1423/
http://www.ieee802.org/1/pages/802.1cn.html

3.3. Owners - Alia Atlas, Pat Thaler

3.4. Action Items
- follow-up and send documents for review as they are adopted as WG
items, WGLC and IETF LC.
- IEEE 802.1 to respond to the IETF NVO3 liaison statement by 7/17/15
- DONE, liaison response at https://datatracker.ietf.org/liaison/1423/

-------------------------------------------------------------------------

4. IETF awareness of IEEE 802.1Q-2011
4.1. Description - CLOSED

-------------------------------------------------------------------------

5. Enabling use of Local Addresses for virtualization and IoT (was:
Effect of virtualization on IEEE 802 architecture)
5.1. Description

At the 7/25/12 f2f meeting Glenn Parsons presented a brief overview of
the IEEE Registration Authority Committee (RAC) mission, highlighting
the current RAC policy on virtualization and asking what virtualization
policy would reduce the consumption of EUI-48 addresses.  Norman Finn
suggested this could be an area of collaboration between the IETF and
the IEEE 802.

Status 4/30/13 - Glenn Parsons submitted an I-D and gave presentations
at IETF-86 in the Technical Plenary, OPS and INT area meetings. The IEEE
RAC will finalize and approve the proposal by June.

9/9/13: draft-ieee-rac-oui-restructuring-01.txt submitted

Status 1/14/14 (Bob Grow): Right now that would just be a RAC document,

7/14/14 - Pat Thaler and Don Pannell gave presentations on regarding
concerns about potential global address consumption by IoT devices and
feasibil8ity of using local MAC addresses for such devices. Virtual
machines usually have a hypervisor with a physical port with a global
address to use to acquire a local MAC address for the VM and an
orchestration system to provide the address. In contrast, a protocol for
IoT devices should work without a global address for the physical port
and should allow for operation with or without an address server.

http://www.ieee802.org/1/files/public/docs2014/New-pannell-MAC-Address-Usage-0714-v1.pdf

http://www.ieee802.org/1/files/public/docs2014/new-addresses-thaler-local-address-acquisition-0714-v2.pdf

9/13/14 IEEE 802.1 drafted a PAR for an Amendment to IEEE 802 Overview
and Architecture, P802c Local Media Access Control (MAC) Addressing. If
the PAR is approved, the amendment will describe using a portion of the
address space for protocols assigning local addresses out of a CID block
associated with the protocol. A portion of the local address space will
continue to be used for assignment by local administrators.  Forwarding
the PAR will be considered at the November IEEE 802 meeting.

IEEE 802.1 is also considering a project to define a protocol for local
address claiming (i.e. without an address server) and local address
distribution using blocks from the CID space. The protocol would be
usable by IoT devices that do not have a global address assignment.

November 2014 - IEEE 802.1 approved the formation of the IEEE 802.1
Local Address Study Group (LASG)

January 2015 - First meeting of the LASG at the Atlanta IEEE 802.1
Interim. PARs and CSDs for the SG formation and a possible Local Address
Assignment Protocol were drafted for discussions.

March 2015 - Approval of the P802c project

June 2015 - Ralph Droms will monitor this and see if it will be of
interest to the IETF.

9/29: working on PAR on protocols for local address acquisition

P802c D0.1 available and discussed at the January 2016 interim

5.2. Relevant Documents
http://www.iab.org/2012/12/13/proposed-ieee-registration-authority-committee-oui-tier-restructuring/
http://www.ietf.org/proceedings/86/slides/slides-86-iab-techplenary-5.pdf
https://datatracker.ietf.org/doc/draft-ieee-rac-oui-restructuring/
http://standards.ieee.org/develop/regauth/tut/eui.pdf
http://www.ieee802.org/1/files/public/docs2014/new-addresses-thaler-local-address-par-v01.pdf
http://www.ieee802.org/1/pages/lasg.html
http://www.ieee802.org/1/files/public/docs2015/lasg-mjt-par-csd-update-0115-v01.pdf
http://www.ieee802.org/1/files/public/docs2015/lasg-mjt-protocol-par-csd-0115-v01.pdf
http://www.ieee802.org/1/pages/802c.html
http://www.ieee802.org/1/files/private/802-c-drafts/d0/802c-d0-1.pdf

5.3. Owners - Glenn Parsons, Pat Thaler, Ralph Droms

5.4. Action Items
- Liaison to IETF when relevant SG materials are available - Glenn
Parsons

-------------------------------------------------------------------------

6. IETF EMU and IEEE 802.1X, 802.11 and 802.16 security based on EAP
6.1. Description - CLOSED

-------------------------------------------------------------------------

7. IETF Ethernet MIB, ADSL MIB and IEEE 802.3
7.1. Description - CLOSED, see RFC 7124 and RFC 7448

-------------------------------------------------------------------------

8. IETF 6LOWPAN and IEEE 802.15
8.1. Description - CLOSED

-------------------------------------------------------------------------

9. IETF PAWS WG and 802.11, 802.19, 802.22
9.1 Description - CLOSED, see RFC 7545

-------------------------------------------------------------------------

10. IETF IPPM and LMAP, and IEEE 802.16 Metrology Study Group- CLOSED,
will reopen if/when it becomes clear that interaction is needed

-------------------------------------------------------------------------

11. IETF and IEEE 802.1 OmniRAN TG
11.1. Description
The 802.1 OmniRAN TG is authorized to create a recommended practice on Network
Reference Model and Functional Description of IEEE 802 Access Network (IEEE
P802.1CF). The project specifies an access network reference model, including
entities and reference points along with behavioral and functional descriptions
of communications among those entities to provide a generic model of IEEE 802
access network for connecting terminals to their access routers over a link
based on the family of IEEE 802 Standards. The specification describes the use
of IEEE 802 technologies to build heterogeneous access networks, which may
include multiple network interfaces, multiple network access technologies, and
multiple network subscriptions, aimed to unify the support of different
interface technologies, enabling shared network control and use of software
defined network (SDN) principles.

9/29/15: see status at https://www.iab.org
/wp-content/IAB-uploads/2015/09/omniran-15-0046-00-00TG-sept-2015-status-report-to-802wgs.pptx

2/1/16: OmniRAN TG created first draft of specification and currently focuses
on creation of initial text for all open sections. A draft with all sections
addressed is expected after the Jul 2016 IEEE 802 plenary meeting and is
intended to be shared with IETF for feedback and review.

11.2. Relevant Documents
Project status: http://www.ieee802.org/1/pages/802.1cf.html w/ link to draft
documents OmniRAN TG Wiki: https://mentor.ieee.org/omniran/bp/StartPage
https://www.iab.org/wp-content/IAB-uploads/2013/01/
omniran-15-0031-00-00TG-status-report-to-ietf-ieee-802-coordination.pdf
https://www.iab.org
/wp-content/IAB-uploads/2015/09/omniran-15-0046-00-00TG-sept-2015-status-report-to-802wgs.pptx
http://www.ieee802.org/1/files/private/cf-drafts/d0/802-1cf-d0-0.pdf

11.3. Owners - Max Riegel

11.4. Action Items - The IEEE with send relevant documents for review by
the IETF

-------------------------------------------------------------------------

12. IETF HOKEY and IEEE 802.21
12.1. Description CLOSED

-------------------------------------------------------------------------

13. IETF MIF and IEEE 802.21 - CLOSED.

-------------------------------------------------------------------------

14. IETF IPFIX Information Elements for Data Link monitoring - CLOSED,
see RFC 7133

-------------------------------------------------------------------------

15. IETF RADIUS attributes for IEEE 802 networks - CLOSED, see RFC 7268

-------------------------------------------------------------------------

16. IEEE802.1Q SRP (and Gen2 updates) and RSVP/SIP - CLOSED

-------------------------------------------------------------------------

17. IEEE 802.1AS/1588 and NTP - CLOSED

-------------------------------------------------------------------------

18. 802.1AS/1588, 802.1Q time aware shaper(s) and RTP - CLOSED

-------------------------------------------------------------------------

19. Common OAM proposal / Layer Independent OAM
19.1. Description - proposal made by Tissa Senevirathne and a group of TRILL
contributors at the IEEE 802.1 meetings in July and September to reuse the IEEE
802.1ag frame format for TRILL OAM. Needs coordination and architectural
consistency with the IEEE 802.1 architecture and OAM practice.

- 8/20/13: The TRILL WG re-chartered, new charter includes OAM.
Rechartering was communicated on the mail list.

- 9/25/13: Liaison Statement sent by the TRILL chairs to the IEEE 802
informing on the status of the work.

- 12/9/13: draft-ietf-trill-oam-framework approved by the IESG

- 1/22/14: new liaison statement sent by TRILL to IEEE 802.1

- Status 1/27/14 (Norman Finn, Donald): liaison from TRILL asking for
code points from the Connectivity Fault Management protocol, Ethernet
OAM, as was done with ITU a few years back. It allocates the blocks of
code points to the IETF with the understanding that they will be
assigned by IANA based on IETF Standards Actions and TRILL will be an
early user of some values. Expected to pass.

- Status 9/15/14 (Dan Romascanu): New Non-WG Mailing List: Lime -- Layer
Independent OAM Management in Multi-Layer Environment (LIME) discussion
list -  https://www.ietf.org/mailman/listinfo/lime. Working on a
charter, may request a BOF at IETF-91

- Status 1/20/15 (Dan): while most of the TRILL OAM work progresses, the
LIME WG was formed and its charter explicitly calls for coordination
with other SDOs including the IEEE

- Status 6/15/15 (Dan): TRILL - MIB work waiting for expert review, YANG
document in WG; LIME - no WG I-Ds yet

- August 2015: call for adoption of draft-tissa-lime-yang-oam-model-06
as LIME WG document in LIME, announcement sent to the ieee-ietf list, now
http://datatracker.ietf.org/doc/draft-ietf-lime-yang-oam-model/

- Individual submission to follow:
http://datatracker.ietf.org/doc/draft-zhuang-lime-yang-oam-model-applicability/
(applicability document)

- draft-ietf-trill-oam-mib-11.txt approved by the IESG

19.2. Relevant Documents

https://datatracker.ietf.org/doc/draft-ietf-trill-oam-req - published as
RFC 6905

http://www.ieee802.org/1/files/public/docs2012/liaison-tissa-oam-ieee-
trill-0912-v02.pptx

https://datatracker.ietf.org/doc/draft-ietf-trill-oam-framework/ -
published as RFC 7174

https://datatracker.ietf.org/doc/draft-tissa-trill-oam-fm/ published as
RFC 7455

http://datatracker.ietf.org/wg/trill/charter/

http://ieee802.org/1/files/public/docs2014/new-senevirathne-trill-oam-
liaison-0114-v01.pptx

http://datatracker.ietf.org/doc/draft-ietf-trill-yang-oam/

http://datatracker.ietf.org/doc/draft-ietf-trill-oam-mib/

https://datatracker.ietf.org/liaison/1302/

http://datatracker.ietf.org/wg/lime/charter/

http://datatracker.ietf.org/doc/draft-ietf-lime-yang-oam-model/

http://datatracker.ietf.org/doc/draft-zhuang-lime-yang-oam-model-applicability/

19.3. Owners - Alia Atlas, Benoit Claise, Norm Finn

19.4. Action Items
Follow the TRILL OAM documents progress in the WG and send them for
review to IEEE 802.1 when they reach milestones (WGLC, IETF LC)

This work item will remain open to monitor the status, as well as other
more OAM-related I-Ds in the TRILL Working Group that should be reviewed
by IEEE 802.1.

TRILL and LIME documents to be communicated for review when relevant to
the IEEE 802 (at LC)

-------------------------------------------------------------------------

20. Area Name - use of TRILL as an alternative path selection protocol
for use in 802.11 mesh networks

20.1. Description - CLOSED

-------------------------------------------------------------------------

21. 6tisch

21.1. Description:
Enable communication and cross-review between the 6tisch WG and IEEE 802
 - In IEEE 802.15: (Bob): Go to the 802.15 website and look for L2R
under public docs.  The group formed in March with a goal to spend 6
months to end up at a project point.

- Status 9/22 - 6tisch charter in external review, on IESG agenda for
9/26, external review message distributed

- Status 9/30/13 (Ted): WG was chartered

- Presentation by Pascal Thubert at the IEEE 802 plenary - https://
mentor.ieee.org/802.15/dcn/13/15-13-0685-00-wng0-6tisch-802-1-for-a-new-
ipv6-multilink-subnet.pptx

- Status 6/18/14: Bob Heile updated that they have set up a group in
802.15 that would be the companion to the IETF 6TISCH. There has been a
lot of cross-participation. Pat Kinney mentioned that they were
participating with the weekly calls and a number of are planning to
attend IETF 90.

- Status 9/14 (Bob Heile): IEEE 802.15.4 has formed an Interest group
for 6TiSCH, the 6t IG. The group met at the IEEE with good feedback on
the IETF WG work.

- Status 12/15: Mail from Michael Richardson asking about the need to
establish a formal liaison between 6tisch and IEEE 802.15.4

- Discussions at IETF 94 about planned par on IEEE 802.15 LLC. Charlie Perkins
made presentation with INTAREA.

- September 2015, status from Pascal Thubert: -6TiSCH is working on
rechartering to integrate dynamic scheduling, that is dynamic allocation of
time slots between peer routers to adapt to IP flows. This involves activity in
the 6top layer and protocol elements over the wire(less).

- 802.15.4 is forming a group to work on LLC. Ultimately the 6top layer and
related protocol elements should belong there; so there will be a need for
splitting responsibilities and transfer.

- Request for a 6lowpan Ethertype  Dan suggest on email to the IESG to request
for an "early allocation" for IPv6 with 6lowpan header compression work

- IEEE 802.15.4 approved (December 2015)

- January 2016: IEEE 802.15.12 Upper Layer Interface (ULI) Project
Authorization Request (PAR) approved by the 801.15 WG, will be discussed for
approval by 802 and EC at the March IEEE 802 plenary; comments welcome at
stds-802-15-llc@listserv.ieee.org - January 2016: 6TiSCH is pursuing its effort
to recharter, including std work on the 6top sublayer. 6Top may ultimately fall
beneath the 15.12 boundary and if so we?ll need to preserve the APIs and the
air interface

21.2. Relevant Documents
- Mail list https://www.ietf.org/mailman/listinfo/6tsch
- https://datatracker.ietf.org/wg/6tisch/charter/
- https://datatracker.ietf.org/doc/draft-ietf-6tisch-architecture/
- https://datatracker.ietf.org/doc/draft-ietf-6tisch-minimal/
- https://datatracker.ietf.org/doc/draft-ietf-6tisch-terminology/
- http://datatracker.ietf.org/doc/draft-ietf-6tisch-coap/
- http://datatracker.ietf.org/doc/draft-ietf-6tisch-6top-interface/
- http://datatracker.ietf.org/doc/rfc7554/
- https://www.ietf.org/proceedings/94/slides/slides-94-6lo-14.pdf
-
https://mentor.ieee.org/802.15/dcn/15/15-15-0760-06-0llc-802-15-12-par-draft.docx

21.3. Owners: Brian Haberman, Bob Heile

21.4. Action Items
- follow the activities in the IETF and IEEE 802.15, share information
informally until activities are chartered

- Follow the activities; send relevant documents from the 6tisch WG as
they reach Last Call stages.

- Discuss establishing a formal liaison at the 1/15 meeting - to discuss
if still needed in the 6/18 virtual meeting - Discussed, no need. ITEM
CLOSED

- Follow new IEEE 802.15 PAR on LLC. Will be sent for review to the IETF

-------------------------------------------------------------------------

22. CAPWAP extensions in OPSAWG

22.1. Description:
- Extensions to the CAPWAP protocol are being defined in the IETF OPSAWG.
The OPSAWG will send the documents that relate to IEEE 802.11 technology
to the IEEE 802.11 WG for expert review.

- Status 1/27/14 (Benoit Claise) - there are two relevant drafts in
Working Group Last Call.  He sent out via email an updated description
of this item, to be added to the next iteration of the shared work items
list.  Dan Romascanu will edit the shared work items list accordingly.

- Status 9/23/14 (Dorothy Stanley): Liaison requests have been made from
the opsawg to IEEE 802.11 for review and comment on each of these
documents. The IEEE 802.11 responded with the liaisons below. There are
no open liaison requests from opsawg to IEEE 802.11 at this time.

- Status 1/20/15 (Dan): 2 out of 3 documents were approved by the IESG and
are now in RFC Editor Queue

- Status 6/15/15 (Dan): one WG document pending (in AD is watching state)
http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/; one
individual submission http://datatracker.ietf.org/doc/draft-you-
opsawg-capwap-separation-for-mp/.

- Status 6/18/15 (Benoit): RFC 7494, IEEE 802.11 Medium Access Control
(MAC) Profile for Control and Provisioning of Wireless Access Points
(CAPWAP), has been published. A second document on the OPSAWG CAPWAP
tunnel is nearly ready for Working Group Last Call; he will let 802.11
know when that is done.

- Status 9/29/15 (Benoit): draft-ietf-opsawg-capwap-alt-tunnel (Alternate
Tunnel Encapsulation for Data Frames in CAPWAP) will merge with
draft-you-opsawg-capwap-separation-for-mp (CAPWAP Control and Data Channel
Separation for Multi-provider Scenario)

22.2. Relevant Documents
- http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-extension/
- http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac -
RFC 7494
- http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/ -
approved
- https://datatracker.ietf.org/liaison/1312/
- https://mentor.ieee.org/802.11/dcn/14/11-14-0913-01-0000-liaison-
response-opsawg-capwap-extension.docx
- https://mentor.ieee.org/802.11/dcn/14/11-14-0684-01-0000-capwap-
hybridmac-liaison-response.docx
- Tunnel encapsulation response: slide 5 in https://mentor.ieee.org/
802.11/dcn/14/11-14-0500-00-0000-may-2014-liaison-to-ietf-report.pptx
- http://datatracker.ietf.org/doc/draft-you-opsawg-capwap-separation-
for-mp/
- http://www.rfc-editor.org/rfc/rfc7494.txt

22.3. Owners: Benoit Claise and Dorothy Stanley

22.4. Action Items
- Benoit to fill in the DESCRIPTION DONE
- Benoit to ensure that OPSAWG chairs send documents at Last Call to
IEEE 802.11
- Dorothy Stanley to channel requests for reviews and responses between
the OPSAWG and IEEE 802.11

-------------------------------------------------------------------------

23. Area Name - naming in layer 2 networks

23.1. Description

CLOSED

-------------------------------------------------------------------------

24. Area Name - coordination between the IETF and IEEE 802 on Pervasive
Monitoring
24.1. Description
The IETF has reached consensus in RFC7258 that pervasive monitoring
ought be treated as with other threats in the development of IETF
protocols. The IEEE 802 started an IEEE 802 Executive Committee (EC)
Privacy Recommendation SG which will study privacy issues related to
IEEE 802 technologies and consider the need for a recommended practice
applicable to IEEE 802 protocols. Given that IETF protocols often run
over IEEE protocols, their privacy properties are intertwined. It would
therefore be useful if both organizations consider the privacy issues
related to usages of combinations of their protocols. For example,
consideration of how MAC addresses may impinge on the privacy properties
of higher layer protocols seems like an obvious area to examine. This
work item could identify how IEEE and IETF protocols together can make
privacy better or worse and feed into the normal development processes
of both organizations.

- A PAR and CSD for Privacy Recommendation EC Study Group - Recommended
Practice, Privacy Considerations for IEERE 802 Technologies was
submitted and sent for review to the IETF

- July 2015: The Privacy Recommendation PAR and CSD were approved
yesterday at the 802 Executive Committee closing meeting. They will now
be forwarded to NesCom for final approval

- September 2015: Privacy Recommendation now within scope of IEEE 802.1
Security TF as IEEE 802.1E

24.2. Relevant Documents
http://www.ieee802.org/PrivRecsg/index.html
https://mentor.ieee.org/privecsg/dcn/15/privecsg-15-0004-03-0000-privacy-recommendation-par-csd-proposal.pptx
https://mentor.ieee.org/privecsg/dcn/15/privecsg-15-0006-01-ecsg-privacy-recommendation-par-proposal.pdf
https://mentor.ieee.org/privecsg/dcn/15/privecsg-15-0004-04-0000-privacy-recommendation-par-csd-proposal.pptx
https://mentor.ieee.org/privecsg/dcn/15/privecsg-15-0030-00-ecsg-privacy-ec-sg-par-proposal.pdf
https://mentor.ieee.org/privecsg/dcn/15/privecsg-15-0029-01-0000-privacy-ec-sg-csd-proposal.docx
http://www.ieee802.org/1/pages/802e.html

24.3. Owners: Stephen Farrell, Juan Carlos Zuniga

24.4. Action Items

-------------------------------------------------------------------------

25. Area Name - Layer2/Layer 3 Interaction for Time-Sensitive Traffic

25.1. Description

The Deterministic Networking (DetNet) Working Group focuses on
deterministic data paths that operate over Layer 2 bridged and Layer 3
routed segments, where such paths can provide bounds on latency, loss,
and packet delay variation (jitter), and high reliability. The Working
Group addresses Layer 3 aspects in support of applications requiring
deterministic networking. The Working Group collaborates with IEEE802.1
Time Sensitive Networking (TSN), which is responsible for Layer 2
operations, to define a common architecture for both Layer 2 and Layer
3. Example applications for deterministic networks include professional
and home audio/video, multimedia in transportation, engine control
systems, and other general industrial and vehicular applications being
considered by the IEEE 802.1 TSN Task Group.

- July 2015: BoF held at IETF 93. Chartering decision now with the IESG

- September 2015: DetNet WG chartered

- 6TiSCH is establishing requirements for detnet:
https://tools.ietf.org/html/draft-thubert-6tisch-4detnet-01

- November 2015: Detnet WG hold its first meeting at IETF 94

- January 2016: use case I-D adopted as WG document, data plance I-D in
preparation

25.2. Relevant Documents
- https://www.ietf.org/mailman/listinfo/detnet
- http://trac.tools.ietf.org/bof/trac/wiki/DetNet
- https://tools.ietf.org/html/draft-gunther-detnet-proaudio-req
- https://tools.ietf.org/html/draft-wetterwald-detnet-utilities-reqs
- https://tools.ietf.org/html/draft-korhonen-detnet-telreq
- https://tools.ietf.org/html/draft-thubert-6tisch-4detnet
- https://tools.ietf.org/html/draft-finn-detnet-problem-statement
- https://tools.ietf.org/html/draft-finn-detnet-architecture
- http://datatracker.ietf.org/wg/detnet/charter/
- https://datatracker.ietf.org/doc/draft-ietf-detnet-use-cases/

25.3. Owners: Deborah Brungard, Norm Finn

25.4. Action Items

26. Area Name - IS-IS extensions for IEEE 802.1Qca
26.1. Description
- The IEEE 802.1 Qca has two normative dependencies on IETF IS-IS
documents. Communication and coordination needs to take place in order
to avoid delays in the approval and publication of IEEE 802.1Qca

- Update 6/11 from Janos Farkas - draft-ietf-isis-pcr, which has been
adopted by the IS-IS WG. Based on it, early allocation of the IS-IS sub-
TLV code points has been imitated. Waiting for confirmation on that. It
is needed next week in order to be able to add the code point values to
the next 802.1Qca draft, otherwise the approval of the 802.1Qca spec
will be delayed by 4 months.

- Update November 2015: IEEE 802.1Qca passed Sponsor Ballot. Two ISIS IDs need
to run accelerated track to provide the normative references to IEEE 802.1Qca
at publication

- January 2016: draft-ietf-isis-pcr has been approved by IESG with Notes;
draft-draft-ietf-isis-te-metric-extensions, draft-ietf-rtgwg-mrt-frr-algorithm,
draft-rtgwg-mrt-frr-architecture are scheduled for the Feb. 4 IESG telechat;

26.2. Relevant Documents
https://datatracker.ietf.org/doc/draft-ietf-isis-pcr/
https://datatracker.ietf.org/doc/draft-ietf-isis-te-metric-extensions/
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-mrt-frr-algorithm/
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-mrt-frr-architecture/

26.3. Owners - Glen Parsons, Alia Atlas
26.4. Action Items
- Follow-up and expedite the approval process of the IETF documents

27. Area Name - development of YANG models in the IEEE 802
27.1. Description
- Following the IESG statement in 2014 and the IETF YANG tutorial at the
July 2014 IEEE 802 plenary, the IEEE 802.1 started to discuss the
introduction of YANG modules, which may result soon in a IEEE 802.1
project. Other IEEE 802 WGs may follow the same path. The IETF and IEEE
will work to support the formation of YANG expertise in the IEEE 802.

- Update 6/15 (Dan): PAR and CSD proposals for two projects were
submitted: 802.1Qcl Amendment, YANG Data Model (for IEEE 802.1Q);
802.1Xck Amendment, YANG Data Model (for IEEE 802.1X)

- Update July 2015: PAR and CSD approved by EC, sent to NesComm

- Update July 15: use of GitHub for all YANG modules (including IEEE 802)
discussed by Glenn Parsons with Benoit Claise and YANG doctors at IETF
93; Glenn also discussed the authoring of an I-D (RFC to be) to request
URN space for the IEEE as per RFC 3406

- IETF draft for IEEE URN, by Mahesh

- Update September 2015: Two projects approved in IEEE 802.1: 802.1Qcp -
Bridges and Bridged Networks Amendment: YANG Data Model, and 802.1Xck -
Port-Based Network Access Control Amendment: YANG Data Model

- Update November 2015: Design Team in place for design of YANG modules for
IEEE 802.3

- Update January 2016: considering a CFI at March 2016 plenary in Macau, but
the actual work in developing YANG code has already been started as DT ? the
main problem right now is the lack of review and feedback

27.2. Relevant Documents
http://www.ieee802.org/802_tutorials/2014-07/Tutorial_Berman_1407.pdf
http://www.ieee802.org/1/files/public/docs2015/new-802-mahesh-yang-0115-v01.pdf
http://www.ieee802.org/1/files/public/docs2015/cl-draft-1Q-YANG-par-0615-v02.pdf
http://www.ieee802.org/1/files/public/docs2015/cl-draft-Qcl-csd-0615-v1.docx
http://www.ieee802.org/1/files/public/docs2015/ck-draft-1X-YANG-par-0615-v02.pdf
http://www.ieee802.org/1/files/public/docs2015/ck-draft-Xck-csd-0615-v1.docx
https://mentor.ieee.org/802.15/dcn/15/15-15-0324-00-0000-p802-15-3-revision-par-detail-draft.pdf
https://mentor.ieee.org/802.15/dcn/15/15-15-0332-00-0000-15-3r1-draft-csd.docx
http://www.ieee802.org/1/pages/802.1cp.html
http://www.ieee802.org/1/pages/802.1ck.html
https://github.com/8023YangDesignTeam/EthernetYang

27.3. Owners - Benoit Claise, Marc Holness
27.4. Action Items

28. Area Name - Multicast on IEEE 802 wireless networks

28.1. Description
-  Discussions in homenet on IP multicast on 802.11 showed a certain level of
lack of information and communication. Wifi multicast is not very reliable, and
a lot of packets are lost.  The control plane for IPv4 is not very sensitive to
multicast packet loss - it's used for setup but not for general data transfer. 
However for IPv6, the protocols use multicast much more, and they give up if
several packets are lost in a row.  Delay isn't so important anymore.  Homenet
wanted to use IS-IS which is L2-multicast-based, and that just wouldn't work
over Wifi.

- Unicast packets get retried at the 802.11 layer, but multicast does not
(because there is no acknowledgement).   802.11aa includes GCR, groupcast with
retries, and that may improve matters.  Both unicast and multicast can be
delayed by power-saving mechanisms.  Multicast can be delayed for everyone if
even a single receiver goes into power-save sleep (for up to 500ms).  AP
manufacturers could choose to transmit the multicasts as unicasts.

January 2016: Dorothy Stanley and  Charlie Perkins will present an IEEE 802
Wireless Tutorial on April 3 at IETF 95 - information available at . Please
update the tutorial page at
http://www.ietf.org/meeting/95/tutorials/ieee-802-wireless.html

28.2. Relevant Documents
https://tools.ietf.org/html/draft-vyncke-6man-mcast-not-efficient
https://tools.ietf.org/html/draft-thubert-6lo-backbone-router
https://www.ietf.org/proceedings/94/slides/slides-94-intarea-1.pdf
http://www.ietf.org/meeting/95/tutorials/ieee-802-wireless.html

28.3. Owners: Mikael Abrahamsson and Dorothy Stanley

28.4. Action Items
EDU Tutorial at IETF 95 prepared by Adrian Stephens and Charlie Perkins

29. Area Name
29.1. Description
29.2. Relevant Documents
29.3. Owners
29.4. Action Items