2019-10-16: Potential Areas for IETF/IEEE802 Coordination v31
slides-interim-2021-ietfieee-08-sessa-2019-10-16-potential-areas-for-ietfieee802-coordination-v31-00
| Meeting Slides | IETF-IEEE (ietfieee) IAB ASG | |
|---|---|---|
| Date and time | 2022-01-01 00:00 | |
| Title | 2019-10-16: Potential Areas for IETF/IEEE802 Coordination v31 | |
| State | Active | |
| Other versions | plain text | |
| Last updated | 2022-06-10 |
slides-interim-2021-ietfieee-08-sessa-2019-10-16-potential-areas-for-ietfieee802-coordination-v31-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 0.20 revised for the period between 1/28/16 and 6/7/16 0.21 revised for the period between 6/7/16 and 8/15/16 0.22 revised for the period between 8/16/16 and 1/30/17 0.23 revised for the period between 31-Jan-2017 and 10-Apr-2017 0.24 revised for the period between 11-Apr-2017 and 15-Jul-2017 0.25 revised for the period between 16-Jul-2017 and 16-Oct-2017 0.26 revised for the period between 17-Oct-2017 and 29-Mar-2018 0.27 revised for the period between 30-Mar-2018 and 29-Jun-2018 0.28 revised for the period between 30-Jun-2018 and 10-Nov-2018 0.29 revised for the period between 11-Nov-2018 and 10-Mar-2019 0.30 revised for the period between 11-Mar-2019 and 18-Jun-2019 0.31 revised for the period between 19-Jun-2019 and 18-Oct-2019 ------------------------------------------------------------------------- 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 IEEE 802.1CQ - Multicast and Local Address Assignment - approved after the November IEEE 802 Plenary Jan 2016: P802c D0.1 available and discussed at the January 2016 interim June 2016: P802c D0.2 - TF ballot, comment resolution at the May 2016 interim meeting June 2016: initial version of a new PAR proposal for a Link-local Registration Protocol circulated on the WG mail list June 2016: WG ballot for P802c/D1.0 July 2016: submission of rfc7042bis I-D Aug. 2016: second WG ballot for P802c/D1. Dec. 2016: P802c is approved. Jan. 2017: There may be some interest in using DHCP to assign MAC addresses. Jul. 2017: It seems like it would be straightforward to assign MAC addresses with DHCPv4. So far, an author for that has not been found. Oct. 2017: Shooting for an Internet-Draft on using DHCP to assign MAC addresses in November or December. Mar. 2018: draft-bvtm-dhc-mac-assign shared with IEEE 802.1. Mar. 2018: The work within 802.1 has been moved to the OmniRAN task group. May 2018: Bernie Volz to give presentation on using DHCPv6 to assign dynamic MAC address to the 802.1 OmniRAN TG on 21 May 2018. Nov. 2018: draft-ietf-6lo-rfc6775-update is approved; it will be RFC 8505. draft-ietf-6lo-ap-nd-08 is a companion; and it si close to WGLC. It protects the registered addresses against snooping, traffic injection, and attraction, using elliptic curve crypto without a PKI. Nov. 2018: 6LoWPAN (for RFC 6282) needs the MAC and IP addresses aligned for optimal compression. Highly desirable for the Local MAC to be used in the IPv6 address. Apr. 2019: DHC WG adopts draft-ietf-dhc-mac-assign-00 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/ https://datatracker.ietf.org/doc/draft-eastlake-rfc7042bis/ https://datatracker.ietf.org/doc/draft-ietf-dhc-mac-assign/ http://standards.ieee.org/develop/regauth/tut/eui.pdf http://www.ieee802.org/1/pages/802c.html http://www.ieee802.org/1/files/public/docs2015/dcb-thaler-1CQ-csd-local-address-prot-1015-v0.pdf http://www.ieee802.org/1/files/private/802-c-drafts/d0/802c-d0-2.zip https://mentor.ieee.org/omniran/dcn/18/omniran-18-0044-00-CQ00-link-layer-addresses-assignment-mechanism-for-dhcpv6.pptx https://1.ieee802.org/dcb/p802-1cq-multicast-and-local-address-assignment/ 5.3. Owners - Glenn Parsons, Max Riegel, Roger Marks, Suresh Krishnan 5.4. Action Items - Coordinate draft-ietf-dhc-mac-assign when it becomes stable - Coordinate IEEE 802.1CQ when it becomes stable ------------------------------------------------------------------------- 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 - 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 - IEEE 802.15.12 approved by IEEE 802 - March 2015: P802.15.9 (C/LM) Recommended Practice for Transport of Key Management Protocol (KMP) Datagrams was approved as a new standard by the IEEE-SA Standards Board - June 2016: The development of the 6P protocol is going on well at 6TiSCH and an ETSI plugtest should be run on July 15-16 right before the IETF. Thanks to IEEE cross participation the WG received recommendations on how to do the signaling. How / when to handoff to .12 has not been discussed yet. The expectation would be that an RFC will be within a year from now, and that 802.12 will be ready to take over by then. - July 2016: ETSI plugtest - August 2016: draft-ietf-6lo-ethertype-request-01 approved for publication - Jan. 2016: Pascal Thubert reported that work on the draft is progressing. Pat Kinney reported that from the 802.15.12 side, it will include things like 6lowpan and 6tsich. They have finished the architecture and are now working on over-the-air interfaces. - Jun. 2017: draft-ietf-6tisch-minimal was published as RFC 8180. - Jul. 2017: ETSI is organizing an 6TiSCH PlugTest prior to the IETF 99. - Feb. 2018: IETF WG sent draft-ietf-6tisch-6top-protocol-09 to the IESG for publication. This document defines 6P, a MAC-layer protocol, for negotiating time slots; 6P messages are carried as payload of an IEEE 802.15.4 Payload Information Element (IE) using one of the "IEEE Std 802.15.4 IETF IE subtype IDs". - Apr. 2018: IESG Ballot on draft-ietf-6tisch-6top-protocol; some DISCUSS positions to resolve. - Jun. 2018: IESG Ballot on draft-ietf-6tisch-6top-protocol; one DISCUSS position to resolve remains. - Nov. 2018: The 6tisch WG work is largely complete. Expect the architecture to be approved by the end of 2018. May recharter if id there is a new 802.11 MAC or PHY to accomodate. - Nov. 2018: There is a publication request for draft-bi-savi-wlan. It is related to RFC 8505. The SAVI draft represents a personal view of what to do when RFC 8505 does not exist; allows wireless to scale. The 802.11 association model is preferable to snooping, and RFC 8505 represents that association at layer 3. - Jun. 2019: draft-ietf-6tisch-architecture-20 in IETF Last Call. - Oct. 2019: draft-ietf-6tisch-architecture-26 is close to approval. 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-tsch/ -- RFC 7554 - https://datatracker.ietf.org/doc/draft-ietf-6tisch-minimal/ -- RFC 8180 - https://datatracker.ietf.org/doc/draft-ietf-6tisch-minimal-security/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-terminology/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-6top-protocol/ -- RFC 8480 - https://datatracker.ietf.org/doc/draft-ietf-6tisch-dtsecurity-zerotouch-join/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-enrollment-enhanced-beacon/ - https://www.ietf.org/proceedings/94/slides/slides-94-6lo-14.pdf - https://mentor.ieee.org/802.15/dcn/15/15-15-0760-07-0llc-802-15-12-par-draft.pdf - https://datatracker.ietf.org/doc/draft-bi-savi-wlan/ 21.3. Owners: Suresh Krishnan, Bob Heile 21.4. Action Items - follow the activities in the IETF and IEEE 802.15, share information informally until points of coordination are identified ------------------------------------------------------------------------- 24. 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 802E - May 2016: Draft 04 of IEEE 802E available - Mar 2017: Draft 07 of IEEE 802E available - Mar. 2018: Work is beginning on an Informational RFC that tells about the MAC randomization experiments at IETF and IEEE 802 meetings. - Nov. 2018: Expect to share a draft of 802E at the end of 2018. - Feb. 2019: IEEE 802E is in WG Letter Ballot; comments to be resolved at the plenary meeting in March 2019. - July 2019: IEEE 802E/D1.4 is in WG Letter Ballot. Anyone that wants to review it can get the password from Russ or Dorothy. - Oct. 2019: IEEE 802E/D1.6 is in WG Recirculation Ballot. Expect Sponsor ballot in late November or early December. Anyone that wants to review it can get the password from Russ or Dorothy. 24.2. Relevant Documents http://www.ieee802.org/1/pages/802e.html http://www.ieee802.org/1/files/private/802-e-drafts/ 24.3. Owners: Roman Danyliw, Juan Carlos Zuniga, Jerome Henry 24.4. Action Items - send information about to IETF on IEEE 802E when the document is stable ------------------------------------------------------------------------- 25. Layer 2/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 plane I-D in preparation - April 2016: Problem statement I-D adopted as WG item - August 2016: draft-finn-detnet-architecture and draft-dt-detnet-dp-alt candidates for WG adoption - Jan. 2017 - Jouni Korhonen reported that the design team hopes to have a first cut of the data plane draft available within the next couple of weeks. - Jul. 2017 - a bunch of documents have been approved or published in IEEE 802 over the past few months, including many extensions to the IEEE 802.1Q bridging specification. - Oct. 2017 - 802.1 is working on data plane and control plane, but DetNet is only working on data plane (recharter needed work on control plane) - Jun. 2018 - David Black has been assigned as the transport advisor to the IETF DetNet WG. - Jun. 2018 - draft-ietf-detnet-problem-statement finished WG Last Call. - Nov. 2018 - IETF Last Call has finished for: -- https://datatracker.ietf.org/doc/draft-ietf-detnet-use-cases/ -- https://datatracker.ietf.org/doc/draft-ietf-detnet-problem-statement/ -- https://datatracker.ietf.org/doc/draft-ietf-detnet-architecture/ The Last Call comments are being resolved. - Nov.2018 - Progress on reservation related documents in 802.1 WG: -- 802.1CS, Link-local Registration Protocol, is in TG ballot -- 802.1Qdd, Resource Allocation Protocol, has an approved PAR -- 802.1DC, Quality of Service Provision by Network Systems, describes the QoS solutions specified in 802.1Q, is in TG ballot -- 802.1CBdb, FRER Extended Stream Identification Functions -- 802.1CB specifies reliability that is also used in DetNet -- 802.1Qcr, Bridges and Bridged Networks Amendment: Asynchronous Traffic Shaping, a new solution to bounded low latency without time synchronization, is in WG ballot. - Nov. 2018: Joint workshop in Bangkok on 10 Nov 2018. - Feb. 2019: draft-ietf-detnet-architecture has finished IETF Last Call. Send comments to Deborah now if still have comments. IESG Evaluation is underway. - May 2019: draft-ietf-detnet-architecture in RFC Editor queue. - Oct. 2019: draft-ietf-detnet-data-plane-framework-02 in WG Last Call. 25.2. Relevant Documents - https://www.ietf.org/mailman/listinfo/detnet - http://trac.tools.ietf.org/bof/trac/wiki/DetNet - http://datatracker.ietf.org/wg/detnet/charter/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-use-cases/ -- RFC 8557 - https://datatracker.ietf.org/doc/draft-ietf-detnet-problem-statement/ -- RFC 8578 - https://datatracker.ietf.org/doc/draft-ietf-detnet-architecture/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-dp-sol-ip/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-dp-sol-mpls/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-flow-information-model/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-yang/ 25.3. Owners: Deborah Brungard, Norm Finn 25.4. Action Items - Ensure that relevant documents are circulated between IEEE 802.1 and DetNet at balloting and Last Call milestones ------------------------------------------------------------------------- 27. 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. - June 2015: PAR and CSD proposals for two projects were submitted: 802.1Qcl Amendment, YANG Data Model (for IEEE 802.1Q); and 802.1Xck Amendment, YANG Data Model (for IEEE 802.1X) - July 2015: PAR and CSD approved by EC, sent to NesComm - July 2015: 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 - 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 - November 2015: Design Team in place for design of YANG modules for IEEE 802.3 - 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 - March 2016: study group formed for YANG modules in IEEE 802.3 - March, May 2016: new drafts for YANG modules in IEEE 802.1, P802.3Qcp in TG ballot - March, May 2016: issue with VLAN modelling in IEEE YANG models in netmod WG; teleconference and face2face discussions at May interim - liaison sent by the IETF OPS AD to IEEE 802.1, discussed at the IEEE 802.1 Plenary - January 2017: Robert Wilton updated the group on the 802.3 Ethernet Interface YANG Task Force (802.3cf) and RMON MIB (RFC 3635). The slides are available at <https://www.iab.org/wp-content/IAB-uploads/2013/01/wilton_8023cf_ethernet_interface_statistics.pdf>. Robert Wilton asked if there are concerns about the current approach. The group suggested that he checks with Benoit Claise and the chairs of the NETMOD and CCAMP WGs to for additional feedback. - March 2017: At the Hackathon a tool was produced for the YANG model catalog. The tool shows the dependencies among modules and keeps the metadata. Benoit expressed concern that too many YANG models are proprietary. Yan Zhuang volunteered to help with for 802.3 YANG modules. Still need volunteer for 802.1. - May 2017: Thanks to Marc Holness, all IEEE 802.1 YANG modules validate correctly. The IEEE 802 YANG modules are now in the YANG catalog <https://www.yangcatalog.org/>. - Jun. 2017: Some YANG data models associated with IEEE 802 PAR have errors. See http://www.claise.be/IEEEStandardYANGPageCompilation.html - Oct. 2017: IEEE 802 created YANGsters mail list. - Oct. 2017: There is a desire for a YANG module for EtherTypes, but the IEEE RAC considers this to be standards work, so it belongs in IEEE 802.1. - Oct. 2017: Please see Network Management Datastore Architecture (NMDA), draft-ietf-netmod-revised-datastores - Nov. 2017: A short presentation on YANG EtherType module: http://www.ieee802.org/1/files/public/docs2017/yang-mholness-YANG-ethertype-1117-v01.pdf - Jan. 2018: IESG approved draft-ietf-netmod-revised-datastores - Feb. 2018: IEEE RAC would like suggestions about the best way to handle friendly EtherType names in a YANG module - Jun. 2018: YANG modules for 802.1Q have been approved as 802-1Qcp. - Nov. 2018: Operations for yangcatalog.org will transition to the IETF Secretariat in early 2019 - Nov. 2018: IETF is considering a change to the NetMod module. The goal is to simplify the interface, but they want to make sure that the changes will not break any other activities. Please check. - Nov. 2018: YANG projects in 802.1 WG: -- 802.1Qcw: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing; in TG ballot -- 802.1Qcx: YANG Data Model for Connectivity Fault Management; in WG ballot -- 802.1ABcu: LLDP YANG Data Model; now have Editor's draft -- 802.1CBcv: FRER YANG Data Model and Management Information Base Module; PAR approved, no draft yet - Feb. 2019: Format of IEEE YANG module repository is now aligned with the one used by IETF. - Jun. 2019: Identified the missing metadata; should be gathered by July 2019 and added to the yangcatalog.org before IETF 105. - Oct. 2019: A PAR has been developed for IEEE 802F that will specify a procedure to generate YANG modules that contain the full EtherType information, including a compact human-readable name, found in the IEEE Registration Authority EtherType public listing. 27.2. Relevant Documents Coordination group for IEEE YANG: - web page: https://1.ieee802.org/yangsters/ - mail list: https://1.ieee802.org/yangsters/yangsters-mail-list-information/ - mail list: https://listserv.ieee.org/cgi-bin/wa?A0=stds-802-3-yang 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 https://datatracker.ietf.org/doc/draft-wilton-netmod-intf-vlan-yang/ https://datatracker.ietf.org/doc/draft-ietf-netmod-intf-ext-yang/ https://datatracker.ietf.org/doc/draft-ietf-netmod-revised-datastores/ http://www.ieee802.org/1/files/private/cp-drafts/d2/802-1Qcp-d2-2.pdf http://www.ieee802.org/1/files/private/ck-drafts/d1/802-1Xck-d1-0.pdf https://www.iab.org/wp-content/IAB-uploads/2013/01/wilton_8023cf_ethernet_interface_statistics.pdf http://www.ieee802.org/1/files/public/docs2019/802f-draft-PAR-0919-v01.pdf 27.3. Owners - Benoit Claise, Marc Holness, Scott Mansfield 27.4. Action Items - IEEE YANG modules are in the yangcatalog.org, but they need more metadata - Coordinate on VLANs YANG models - There is a desire for the IEEE RAC to produce a YANG module for EtherTypes ------------------------------------------------------------------------- 30. Intelligent Transportation Systems (ITS) 30.1. Description Vehicle-to-Vehicle Communications (V2V) and Vehicle-to-Infrastructure (V2I) communications may involve IEEE 802.11-OCB (Outside the Context of a Basic Service Set) in the Dedicated short-range communications (DSRC) spectrum. The IPWAVE WG will specify the use of IPv6 over IEEE 802.11-OCB in a way that is compatible with the existing IEEE 1609 specifications. - Sep. 2017: WG Last Call on draft-ietf-ipwave-ipv6-over-80211ocb; encourage review and comment from IEEE 802.11 folks - Feb. 2018: IETF IPWAVE WG is resolving comments from WG Last Call. - Mar. 2018: IEEE 802.11 is just starting work on Next Gen V2X. It will update the PHY to be more like 802.11n or 802.11ac. Expect the first meeting of the task group in May 2018. - Nov. 2018: One open issue on draft-ietf-ipwave-ipv6-over-80211ocb about neighbor discovery; hopefully it will be resolved by end of 2018. - Jan. 2019: IEEE 802.11bd will specify Next Gen V2X in a manner that is backward compatible with 802.11p. - Jun. 2019: draft-ietf-ipwave-ipv6-over-80211ocb in IETF Last Call. - Jun. 2019: IEEE 802.11bd is active and making good progress. - Oct. 2019: draft-ietf-ipwave-ipv6-over-80211ocb in RFC Editor queue. - Oct. 2019: IEEE 802.11 for next generation V2X communication is expected - Oct. 2019: Work is starting to formally specify the interface between IEEE 802.11 and IEEE 1609. 30.2. Relevant Documents - Mail list: its@ietf.org - Mail archive: https://mailarchive.ietf.org/arch/search/?email_list=its - https://datatracker.ietf.org/doc/draft-ietf-ipwave-ipv6-over-80211ocb - https://mentor.ieee.org/802.11/dcn/18/11-18-0513-02-0wng-802-11-for-next-generation-v2x-communication.pptx - https://mentor.ieee.org/802.11/dcn/19/11-19-1670-00-0000-ieee-1609-wg-liaison-report.pptx 30.3. Owners: Suresh Krishnan, Dorothy Stanley, Russ Housley 30.4. Action Items - CLOSE when draft-ietf-ipwave-ipv6-over-80211ocb becomes RFC ------------------------------------------------------------------------- 31. LPWAN 31.1. Description: IEEE 802.15.4w is was one of the technologies chosen to be supported in the IETF LPWAN work. IEEE 802.15.4w-related overview information is needed in addition to the material that is already in RFC 8376, which might need to be updated. - Nov. 2018: Recharter of LPWAN is underway to focus on IEEE 802.15.4, which is a shift from the previous direction to focus on WiSUN first. - Feb. 2019: Expect WG Letter ballot on IEEE 802.15.4w coming out of the March 2019 plenary meeting. 31.2. Relevant Documents - Mail list: https://www.ietf.org/mailman/listinfo/lp-wan - Mail archive: https://mailarchive.ietf.org/arch/search/?email_list=lp-wan - Also, a non-WG list of interest: https://www.ietf.org/mailman/listinfo/paw - https://www.rfc-editor.org/rfc/rfc8376.txt - http://grouper.ieee.org/groups/802/15/pub/TG4w.html - https://datatracker.ietf.org/doc/draft-authors-lpwan-schc-802154/ 31.3. Owners: Suresh Krishnan, Pascal Thubert, Dorothy Stanley, Bob Heile 31.4. Action Items - Exchange information regularly regarding the status of 802.15.4w ------------------------------------------------------------------------- 32. Source Address Validation for Wireless LAN 32.1. Description A document for SAVI (Source Address Validation Improvements) was sent out for review, and a reviewer brought up some issues that may be of relevance to IEEE 802.11. - Apr. 2019: 6LO WG sent draft-ietf-6lo-ap-nd-12 to IESG; expect IETF Last Call soon - Oct. 2019: draft-ietf-6lo-ap-nd-12 ready for IETF Last Call; review by IEEE 802.11 is highly desirable 32.2. Relevant Documents - https://datatracker.ietf.org/doc/draft-bi-savi-wlan - https://datatracker.ietf.org/doc/draft-ietf-6lo-ap-nd 32.3. Owners: Suresh Krishnan, Dorothy Stanley 32.4. Action Items Request IEEE 802.11 review of draft-ietf-6lo-ap-nd-12 ------------------------------------------------------------------------- 33. Capability Discovery 33.1. Description IETF LSVR is developing Layer 3 Discovery and Liveness (L3DL), and IEEE 802.1 is talking about version 2 of the Link Layer Discovery Protocol (LLDPv2). The protocols are aimed at similar needs. - Jun. 2019: 802.1ABdh (Support for Multiframe Protocol Data Units) PAR should be approved in July 2019 at the plenary meeting 33.2. Relevant Documents - Mail list: https://www.ietf.org/mailman/listinfo/lsvr - Mail archive: https://mailarchive.ietf.org/arch/browse/lsvr - http://www.ieee802.org/1/files/public/docs2019/new-congdon-lldpv2-consideration-0119-v01.pdf - http://www.ieee802.org/1/files/public/docs2019/dh-draft-PAR-0519-v01.pdf - https://datatracker.ietf.org/doc/draft-ietf-lsvr-l3dl 33.3. Owners: Alvaro Retana, Janos Farkas 33.4. Action Items Keep each other (LSVR and TSN) informed of progress, changes, etc. ------------------------------------------------------------------------- NEXT POTENTIAL AREAS FOR IETF/IEEE802 COORDINATION ------------------------------------------------------------------------- ------------------------------------------------------------------------- 34. Area Name 34.1. Description 34.2. Relevant Documents 34.3. Owners 34.4. Action Items ------------------------------------------------------------------------- 35. Area Name 35.1. Description 35.2. Relevant Documents 35.3. Owners 35.4. Action Items ------------------------------------------------------------------------- CLOSED POTENTIAL AREAS FOR IETF/IEEE802 COORDINATION ------------------------------------------------------------------------- ------------------------------------------------------------------------- 1. IETF TRILL Fine-grained labeling and IEEE 802.1 tags -- CLOSED ------------------------------------------------------------------------- 2. IETF BFD and IEEE 802.1AX -- CLOSED Documents: - https://www.rfc-editor.org/rfc/rfc7130.txt ------------------------------------------------------------------------- 3. IETF NVO3 and IEEE 802.1 DCB -- CLOSED Documents: - IEEE 802.1Qcy was published on 4 June 2019 -- https://ieeexplore.ieee.org/document/8728296 ------------------------------------------------------------------------- 4. IETF awareness of IEEE 802.1Q-2011 -- CLOSED ------------------------------------------------------------------------- 6. IETF EMU and IEEE 802.1X, 802.11 and 802.16 security based on EAP -- CLOSED ------------------------------------------------------------------------- 7. IETF Ethernet MIB, ADSL MIB and IEEE 802.3 -- CLOSED Documents: - https://www.rfc-editor.org/rfc/rfc7124.txt - https://www.rfc-editor.org/rfc/rfc7448.txt ------------------------------------------------------------------------- 8. IETF 6LOWPAN and IEEE 802.15 -- CLOSED ------------------------------------------------------------------------- 9. IETF PAWS WG and 802.11, 802.19, 802.22 -- CLOSED Documents: - https://www.rfc-editor.org/rfc/rfc7545.txt ------------------------------------------------------------------------- 10. IETF IPPM and LMAP, and IEEE 802.16 Metrology Study Group -- CLOSED ------------------------------------------------------------------------- 11. IETF and IEEE 802.1 OmniRAN TG -- CLOSED Documents: - https://standards.ieee.org/content/ieee-standards/en/standard/802_1CF-2019.html ------------------------------------------------------------------------- 12. IETF HOKEY and IEEE 802.21 -- CLOSED ------------------------------------------------------------------------- 13. IETF MIF and IEEE 802.21 -- CLOSED ------------------------------------------------------------------------- 14. IETF IPFIX Information Elements for Data Link monitoring -- CLOSED Documents: - https://www.rfc-editor.org/rfc/rfc7133.txt ------------------------------------------------------------------------- 15. IETF RADIUS attributes for IEEE 802 networks -- CLOSED Documents: - https://www.rfc-editor.org/rfc/rfc7268.txt ------------------------------------------------------------------------- 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 -- CLOSED Documents: - https://www.rfc-editor.org/rfc/rfc6905.txt - https://www.rfc-editor.org/rfc/rfc7174.txt - https://www.rfc-editor.org/rfc/rfc7455.txt - https://www.rfc-editor.org/rfc/rfc7784.txt ------------------------------------------------------------------------- 20. Area Name - use of TRILL as an alternative path selection protocol for use in 802.11 mesh networks -- CLOSED ------------------------------------------------------------------------- 22. CAPWAP extensions in OPSAWG -- CLOSED Documents: - http://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-extension - expired - http://www.rfc-editor.org/rfc/rfc7494.txt - http://www.rfc-editor.org/rfc/rfc8350.txt ------------------------------------------------------------------------- 23. Area Name - naming in layer 2 networks -- CLOSED ------------------------------------------------------------------------- 26. Area Name - IS-IS extensions for IEEE 802.1Qca - CLOSED ------------------------------------------------------------------------- 28. Area Name - Multicast on IEEE 802 wireless networks -- CLOSED Tutorial materials used at IETF 97 are available at: - https://www.youtube.com/watch?v=H5nskJAV00I&list=PLC86T-6ZTP5gtLuoSjpTGO_mS5Ly2pfIS&index=128 - https://www.ietf.org/proceedings/97/slides/slides-97-edu-80215-projects-summary-overview-00.pptx - https://www.ietf.org/proceedings/97/slides/slides-97-edu-sessg-ieee-802-wireless-tutorial-00.ppt ------------------------------------------------------------------------- 29. Area Name - Opportunistic Wireless Encryption (OWE) -- CLOSED Documents: - https://www.rfc-editor.org/rfc/rfc8110.txt - https://datatracker.ietf.org/liaison/1486/ -------------------------------------------------------------------------