Potential areas for IETF/IEEE802-Coordination v38
slides-interim-2022-ietfieee-01-sessa-potential-areas-for-ietfieee802-coordination-v38-00
| Meeting Slides | IETF-IEEE (ietfieee) IAB ASG | |
|---|---|---|
| Date and time | 2022-02-24 17:00 | |
| Title | Potential areas for IETF/IEEE802-Coordination v38 | |
| State | Active | |
| Other versions | plain text | |
| Last updated | 2022-06-10 |
slides-interim-2022-ietfieee-01-sessa-potential-areas-for-ietfieee802-coordination-v38-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 0.32 revised for the period between 19-Oct-2019 and 25-Feb-2020 0.33 revised for the period between 25-Feb-2020 and 15-Jun-2020 0.34 revised for the period between 16-Jun-2020 and 27-Oct-2020 0.35 revised for the period between 28-Oct-2020 and 17-Feb-2021 0.36 revised for the period between 18-Feb-2021 and 24-Jun-2021 0.37 revised for the period between 25-Jun-2021 and 25-Oct-2021 0.38 revised for the period between 26-Oct-2021 and 02-Mar-2022 ------------------------------------------------------------------------- 5. Enabling use of Local Addresses for virtualization and IoT (was: Effect of virtualization on IEEE 802 architecture) 5.1. Description At the 25 July 2012 face-to-face 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 IEEE 802. - Apr 2013: 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 2013. - Sep 2013: draft-ieee-rac-oui-restructuring-01.txt submitted - Jan 2014: Right now that would just be a RAC document - Jul 2014: Pat Thaler and Don Pannell gave presentations on regarding concerns about potential global address consumption by IoT devices and feasibility 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 - Sep 2014: 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. - Nov 2014: 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. - Nov 2014: IEEE 802.1 approved the formation of the IEEE 802.1 Local Address Study Group (LASG) - Jan 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. - Mar 2015: Approval of the P802c project - Jun 2015: Ralph Droms will monitor this and see if it will be of interest to the IETF. - Sep 2015: working on PAR on protocols for local address acquisition - Nov 2015: IEEE 802.1CQ (Multicast and Local Address Assignment) was approved after the November IEEE 802 Plenary - Jan 2016: P802c D0.1 available and discussed at the January 2016 interim - Jun 2016: P802c D0.2 - TF ballot, comment resolution at the May 2016 interim meeting - Jun 2016: initial version of a new PAR proposal for a Link-local Registration Protocol circulated on the WG mail list - Jun 2016: WG ballot for P802c/D1.0 - Jul 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 TG. - 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 is 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. - Oct 2019: DHC WG Last Call for draft-ietf-dhc-mac-assign-01 and draft-ietf-dhc-slap-quadrant-01. - Jan 2020: Successful DHC WG Last Call for draft-ietf-dhc-mac-assign-01. - Jun 2020: Desire to make sure the MAC addresses come from a pool assigned to the company operating the service. Authors seem agreeable. - Oct 2020: TG Letter Ballot on IEEE 802.1CQ is leading to significant technical changes as part of comment resolution. - Nov 2020: PAR for 802.11bh approved for "Enhanced service with randomized MAC addresses". It may define new mechanisms for identifiers, given MAC address randomization, without decreasing user privacy. - Nov 2020: PAR for 802.11bi approved for "Enhanced service with Data Privacy Protection". It will specify new mechanisms to improve user privacy for the 802.11 MAC specification. - Nov 2020: draft-ietf-6lo-ap-nd has been published as RFC 8928. - Dec 2020: draft-ietf-dhc-mac-assign has been published as RFC 8947. - Jun 2021: Expect Task Group letter ballot for IEEE 802.1CQ in July 2021. - Oct 2021: Task Group letter ballot closed and comments have been resolved. During Nov 2021, will seek approval to for liaison of IEEE 802.1CQ to INTAREA. Also, will brief the document to INTAREA at IETF 112. - Feb 2022: Getting close to a stable draft document; expected August 2022. 5.2. Relevant Documents 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 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/wg/detnet https://www.rfc-editor.org/rfc/rfc8505.txt https://www.rfc-editor.org/rfc/rfc8558.txt https://www.rfc-editor.org/rfc/rfc8928.txt https://www.rfc-editor.org/rfc/rfc8929.txt https://www.rfc-editor.org/rfc/rfc8947.txt 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 IEEE 802.1CQ ------------------------------------------------------------------------- 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 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. - Jul 2015: BoF held at IETF 93. Chartering decision now with the IESG - Sep 2015: DetNet WG chartered - 6TiSCH is establishing requirements for detnet: https://tools.ietf.org/html/draft-thubert-6tisch-4detnet-01 - Nov 2015: Detnet WG hold its first meeting at IETF 94 - Jan 2016: use case I-D adopted as WG document, data plane I-D in preparation - Apr 2016: Problem statement I-D adopted as WG item - Aug 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. - Jan 2020: IEEE Std 802.1AS-2020 has been published, which includes the generalized Precision Time Protocol (gPTP) profile of the IEEE Std 1588-2019 Precision Time Protocol. - Jan 2020: IEEE Std 802.1AX-2020 Link Aggregation has been published. - Jun 2020: draft-ietf-detnet-data-plane-framework is approved for publication. - Jun 2020: draft-ietf-detnet-ip is under IESG review; scheduled for telechat 25 June 2020. - Jul 2020: IETF DetNet was rechartered in include controller plane. - Aug 2020: IEEE Std 802.1CMde-2020 TSN for Fronthaul amendment has been published to extend the base standard with enhancements to fronthaul profiles, add support for a new fronthaul interface, and new synchronization, and syntonization standards. - Oct 2020: IEEE Std 802.1Qcr-2020 Asynchronous Traffic Shaping (ATS) has been published. This amendment specifies synchronous traffic shaping over full-duplex links with constant data rates. - Feb 2021: With the RFC Editor; expect to be published soon: -- draft-ietf-detnet-flow-information-model -- draft-ietf-detnet-ip-over-mpls -- draft-ietf-detnet-mpls-over-udp-ip - Feb 2021: With IESG for final review and approval: -- draft-ietf-detnet-ip-over-tsn -- draft-ietf-detnet-mpls-over-tsn -- draft-ietf-detnet-tsn-vpn-over-mpls -- draft-ietf-detnet-security - Feb 2021: draft-ietf-detnet-bounded-latency is in WG Last Call. - Feb 2021: The new P802.1DP project has been just started to specify TSN profiles for aerospace onboard Ethernet networks. - Feb 2021: IEEE SA ballot is about start on the P802.1Qcz Congestion Isolation project. - Jun 2021: P802.1Qcz is stalled behind the update of the base P802.1Q. - Oct 2021: P802.1Q is still blocking P802.1Qcz. P802.1Q is in IEEE SA ballot, so it should get published in 2022. - Nov 2021: draft-ietf-detnet-yang has been sent to the IESG for review and approval. - Dec 2021: IEEE Std 802.1BA-2021 has been published. - Feb 2022: EEE Std 802.1CBcv-2021 has been published. - Feb 2022: draft-ietf-detnet-bounded-latency has been sent to the IESG for review and approval. - Feb 2022: 802.1ABcu, 802.1ABdh, and 802.1CBdb have been approved; they are with the IEEE SA Editor. 25.2. Relevant Documents - https://1.ieee802.org/tsn/ - https://www.ieee802.org/1/files/public/docs2021/admin-tsn-summary-0221-v01.pdf - https://1.ieee802.org/tsn/802-1dc/ - https://1.ieee802.org/tsn/802-1df/ - https://1.ieee802.org/tsn/802-1dg/ - https://1.ieee802.org/tsn/802-1dp/ - https://1.ieee802.org/tsn/802-1asdm/ - https://1.ieee802.org/tsn/802-1asdn/ - https://1.ieee802.org/tsn/802-1qdq/ - https://1.ieee802.org/tsn/802-1asds/ - https://1.ieee802.org/tsn/iec-ieee-60802/ - https://www.ietf.org/mailman/listinfo/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/ -- RFC 8655 - https://datatracker.ietf.org/doc/draft-ietf-detnet-flow-information-model/ -- RFC 9016 - https://datatracker.ietf.org/doc/draft-ietf-detnet-data-plane-framework/ -- RFC 8938 - https://datatracker.ietf.org/doc/draft-ietf-detnet-ip/ -- RFC 8939 - https://datatracker.ietf.org/doc/draft-ietf-detnet-mpls/ -- RFC 8964 - https://datatracker.ietf.org/doc/draft-ietf-detnet-flow-information-model/ -- RFC 9016 - https://datatracker.ietf.org/doc/draft-ietf-detnet-ip-over-tsn/ -- RFC 9023 - https://datatracker.ietf.org/doc/draft-ietf-detnet-tsn-vpn-over-mpls/ -- RFC 9024 - https://datatracker.ietf.org/doc/draft-ietf-detnet-ip-over-mpls/ -- RFC 9056 - https://datatracker.ietf.org/doc/draft-ietf-detnet-mpls-over-udp-ip/ -- RFC 9025 - https://datatracker.ietf.org/doc/draft-ietf-detnet-mpls-over-tsn/ -- RFC 9037 - https://datatracker.ietf.org/doc/draft-ietf-detnet-bounded-latency/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-controller-plane-framework/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-oam-framework/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-ip-oam/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-mpls-oam/ - https://datatracker.ietf.org/doc/draft-ietf-detnet-security/ -- RFC 9055 - https://datatracker.ietf.org/doc/draft-ietf-detnet-yang/ 25.3. Owners - John Scudder, Norm Finn, Janos Farkas 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 resulted 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. - Jun 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) - Jul 2015: PAR and CSD approved by EC, sent to NesComm - Jul 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 - Sep 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 - Nov 2015: Design Team in place for design of YANG modules for IEEE 802.3 - Jan 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 - Mar 2016: study group formed for YANG modules in IEEE 802.3 - Mar-May 2016: new drafts for YANG modules in IEEE 802.1, P802.3Qcp in TG ballot - Mar-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 - Jan 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 the URL below. 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. -- https://www.iab.org/wp-content/IAB-uploads/2013/01/wilton_8023cf_ethernet_interface_statistics.pdf - Mar 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: -- 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. - Feb 2020: IEEE 802f PAR was approved, and work has started. - Jun 2020: IEEE 802 YANG modules and IETF YANG modules are using different string formats to represent MAC Addresses; need to figure out a why forward that will allow exact match string comparison. - Jul 2020: draft-ietf-i2rs-yang-l2-network-topology is now with the IESG; some specific questions were asked of IEEE 802.1 for coordination. - Jul 2020: IEEE Std 802.1Qcx-2020 YANG for Connectivity Fault Management (CFM) has been published. - Aug 2020: Comments on draft-ietf-i2rs-yang-l2-network-topology were provided by IEEE YANGsters: -- Initial Review: https://mailarchive.ietf.org/arch/msg/i2rs/NtnhmhouhLbSv6nU2xX_wFw0to8/ -- Response: https://mailarchive.ietf.org/arch/msg/i2rs/KC_HtT0F0o-be7izK0VCgSo1oWk/ -- Further Reply: https://mailarchive.ietf.org/arch/msg/i2rs/YJC9pbOXmmWe82N2G5HnDSXQBWE/ - Oct 2020: Metadata for all IEEE 802 YANG modules has been entered at yangcatalog.org - Feb 2021: The YANG projects for LLDP (P802.1ABcu), FRER (P802.1CBcv), and an initial set of TSN features (P802.1Qcw) are at WG ballot. - Feb 2021: The P802f project to specify YANG data model for EtherTypes including compact and human-readable names is at TG ballot. - Apr 2021: IEEE SA letter ballot group is forming for P802.1ABcu. - Jun 2021: IEEE SA letter ballot group for P802.1ABcu in underway. - Jun 2021: Expect P802.1ABcv and P802.1ABcw to move to IEEE SA letter ballot after the July 2021 plenary meeting. - Jun 2021: Expect WG letter ballot for Ethertype YANG document after the July 2021 plenary meeting. - Oct 2021: P802f specifies YANG data model for EtherTypes is in WG ballot. Suggest briefing to NETMOD about P802f at IETF 112. - Feb 2022: P802f is in WG Ballot; will share with NETMOD after ballot. - Feb 2022: P802f will be folded into 802-Rev as that project move forward. 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/ https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topology/ 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 https://1.ieee802.org/tsn/802f/ https://1.ieee802.org/tsn/802-1qcw/ https://1.ieee802.org/tsn/802-1asdn/ 27.3. Owners - Rob Wilton, Scott Mansfield 27.4. Action Items - Desire for IEEE802.1AX YANG model; currently no project to work on it. - Common string formats to represent MAC Addresses in YANG modules. - Security coordination needed for draft-ietf-netconf-keystore. ------------------------------------------------------------------------- 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 - Feb 2020: PAR is approved, but an editor has not been identified. - Jun 2020: draft-ietf-lsvr-l3dl is in WG Last Call, but it will not be forwarded to the IESG until the draft-ietf-lsvr-l3dl-signing document is ready too. - Oct 2020: TG Letter Ballot just closed on LLDPv2, and comment resolution to begin in Nov. 2020. - Dec 2020: The IEEE 802.1CS-2020 Link-local Registration Protocol (LRP) specification is approved. - Feb 2021: P802.1CBdb is at WG ballot, which specifies extended stream identification functions. - Feb 2021: P802.1ABdh is at WG ballot, which specifies support for multi-frame LLDPDUs. - Feb 2021: P802.1Qdd is at TG ballot. The Resource Allocation Protocol (RAP) project specifies the first application of 802.1CS LRP for distributed resource reservation. - Feb 2021: P802.1Qdj is at TG ballot; it covers Configuration Enhancements for Time-Sensitive Networking. - Feb 2021: P802.1CQ is at TG ballot; it specifies locally-unique assignment of 48-bit and 64-bit addresses in IEEE 802 networks. - Feb 2021: P802.1Qcj (auto-attach) is at WG ballot. - Feb 2021: draft-ietf-lsvr-l3dl and draft-ietf-lsvr-l3dl-signing are in LSVR WG Last Call. - Feb 2021: IEEE 802.1 is adding "Support for Multiframe Protocol Data Units" to LLDP. (See https://1.ieee802.org/tsn/802-1abdh/) - Jun 2021: IEEE SA letter ballot group for LLDPv2. - Oct 2021: IEEE SA letter ballot passed for LLDPv2. Will go to REVCOM in December 2021. - Feb 2022: draft-ietf-lsvr-l3dl and draft-ietf-lsvr-l3dl-signing completed LSVR WG Last Call, but the advancement is on hold so that the LSVR WG can focus on the main LSVR specification. Once that is done, L3DL will be added to the LSVR WG charter and progressed. - Feb 2022: LLDPv2 standard (802.1ABdh) has been approved; it is awaiting publication. 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://standards.ieee.org/ieee/802.1ABdh/7667/ - https://datatracker.ietf.org/doc/draft-ietf-lsvr-l3dl - https://datatracker.ietf.org/doc/draft-ietf-lsvr-l3dl-signing 33.3. Owners - Alvaro Retana, Janos Farkas 33.4. Action Items Keep LSVR and IEEE 802.1 TSN TG informed of progress, changes, etc. ------------------------------------------------------------------------- 34. Reliable and Available Wireless (RAW) 34.1. Description RAW provides for high reliability and availability for IP connectivity over a wireless medium. The wireless medium presents challenges to achieve deterministic properties such as low packet error rate, bounded consecutive losses, and bounded latency. RAW extends the DetNet WG concepts to provide for high reliability and availability for an IP network utilizing scheduled wireless segments and other media, such as IEEE Std. 802.15.4 timeslotted channel hopping (TSCH), 3GPP 5G ultra-reliable low latency communications (URLLC), IEEE 802.11ax/be, and LDACS. RAW will stay abstract to the radio layers underneath, addressing the Layer 3 aspects in support of applications requiring high reliability and availability. - Feb 2020: IETF RAW WG Chartered. - Jun 2021: draft-ietf-raw-ldacs passed to IESG by RAW WG. - Oct 2021: The intent of P802.15.12 was to augment 802.15.4, but that PAR will be withdrawn. Instead, P802.15.14 and P802.15.15 will each include some of those augmentations. - Jan 2022: Sent draft-ietf-raw-ldacs to the IESG for approval. - Feb 2022: PAR for P802.15.12 is being withdrawn. 34.2. Relevant Documents - https://datatracker.ietf.org/wg/raw/about/ - https://datatracker.ietf.org/doc/draft-ietf-raw-technologies/ - https://datatracker.ietf.org/doc/draft-ietf-raw-architecture/ - https://datatracker.ietf.org/doc/draft-ietf-raw-framework/ - https://datatracker.ietf.org/doc/draft-ietf-raw-industrial-requirements/ - https://datatracker.ietf.org/doc/draft-ietf-raw-use-cases/ - https://datatracker.ietf.org/doc/draft-ietf-raw-oam-support/ - https://datatracker.ietf.org/doc/draft-ietf-raw-ldacs/ 34.3. Owners - John Scudder, Dorothy Stanley 34.4. Action Items - Seeking reviewers in 802.11 for RAW documents. ------------------------------------------------------------------------- 35. MAC Address Device Identification for Network and Application Services (MADINAS) 35.1. Description The IETF MADINAS Working Group will examine the effect of Randomized and Changing MAC addresses (RCM) schemes on network and application services in several scenarios identified as relevant. The MADINAS WG will also evaluate various identifiers (beyond the MAC address) that can be used by the network to provide services, as well as scenarios where personal device identity is not required. For scenarios where personal device identity stability is desirable, the MADINAS WG will recommend protocols that can be used to protect the request and exchange of identifiers between the client and the service provider. For scenarios where privacy is paramount, the MADINAS WG will recommend best practices to ensure that the privacy achieved with RCM is not compromised by the communication of other identifiers. The MADINAS WG will examine other IETF work that may be applicable. - Oct 2021: First MADINAS WG meeting will be IETF 112 - Feb 2022: draft-henry-madinas-framework has been adopted by the WG; expect draft-ietf-madinas-framework to be posted soon. 35.2. Relevant Documents - Mailing List: https://www.ietf.org/mailman/listinfo/Madinas - https://datatracker.ietf.org/doc/draft-ietf-madinas-use-cases/ - https://datatracker.ietf.org/doc/draft-ietf-madinas-mac-address-randomization/ - https://datatracker.ietf.org/doc/draft-henry-madinas-framework/ 35.3. Owners - Eric Vyncke, Glenn Parsons, Dorothy Stanley 35.4. Action Items - Coordinate MADINAS with P801.1, P802.11bh, and P802.11bi ------------------------------------------------------------------------- ------------------------------------------------------------------------- NEXT POTENTIAL AREAS FOR IETF/IEEE802 COORDINATION ------------------------------------------------------------------------- ------------------------------------------------------------------------- 36. Area Name 36.1. Description 36.2. Relevant Documents 36.3. Owners 36.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 ------------------------------------------------------------------------- 21. 6tisch -- CLOSED Documents (all Internet-Drafts are in RFC Editor queue at time of closing): - https://datatracker.ietf.org/doc/draft-ietf-6tisch-architecture/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-enrollment-enhanced-beacon/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-minimal-security/ - https://datatracker.ietf.org/doc/draft-ietf-6tisch-msf/ - https://www.rfc-editor.org/rfc/rfc7554.txt - https://www.rfc-editor.org/rfc/rfc8180.txt - https://www.rfc-editor.org/rfc/rfc8480.txt ------------------------------------------------------------------------- 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 ------------------------------------------------------------------------- 24. Coordination between the IETF and IEEE 802 on Pervasive Monitoring -- CLOSED Documents: https://standards.ieee.org/standard/802E-2020.html ------------------------------------------------------------------------- 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/ ------------------------------------------------------------------------- 30. Intelligent Transportation Systems (ITS) -- CLOSED Documents: - https://www.rfc-editor.org/rfc/rfc8691.txt ------------------------------------------------------------------------- 31. LPWAN -- CLOSED Documents: - https://standards.ieee.org/standard/802_15_4w-2020.html ------------------------------------------------------------------------- 32. Source Address Validation for Wireless LAN -- CLOSED Documents: - https://www.rfc-editor.org/rfc/rfc8928.txt -------------------------------------------------------------------------