OPSAWG T. Graf Internet-Draft Swisscom Intended status: Standards Track H. Zheng Expires: 19 May 2027 Huawei Technologies 15 November 2026 Export of Gigabit Passive Optical Network Encapsulation Method in IP Flow Information Export (IPFIX) draft-ietf-opsawg-ipfix-gpon-gem-04 Abstract This document introduces new IP Flow Information Export (IPFIX) Information Elements to identify a set of G-PON Encapsulation Method entities in the Passive Optical Transport of the Optical Distribution Network. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 19 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Graf & Zheng Expires 19 May 2027 [Page 1] Internet-Draft IPFIX Export G-PON GEM November 2026 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. New IPFIX G-PON GEM Elements . . . . . . . . . . . . . . . . 5 4. Sample Use Cases . . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 5.1. New IPFIX G-PON GEM Information Elements . . . . . . . . 6 5.1.1. ingressGponGemPti . . . . . . . . . . . . . . . . . . 6 5.1.2. egressGponGemPti . . . . . . . . . . . . . . . . . . 7 5.1.3. ingressGponGemPortId . . . . . . . . . . . . . . . . 7 5.1.4. egressGponGemPortId . . . . . . . . . . . . . . . . . 8 5.1.5. IPFIX G-PON Encapsulation Method PTI Subregistry . . 8 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 10 7.1. Huawei MA5800T-X17 . . . . . . . . . . . . . . . . . . . 10 8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 9.1. Normative References . . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . 11 Appendix A. IPFIX Encoding Examples . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 1. Introduction The G-PON Encapsulation Method (GEM) data plane header defined in Section 8.3.1 of [itu-g984-3] and XG-PON Encapsulation Method (XGEM) data plane header defined in Section 9.1.2 of [itu-g9804-2] facilitate the framing, error control, encryption keying, payload type identification and payload separation in the Optical Distribution Network. It is being used in the Optical Distribution Network between the Optical Line Termination (OLT) at the network operator and the Optical Network Unit (ONU), Optical Network Terminal (ONT) at the end user in the passive optical transport within the broadband access domain. IPFIX is widely applied in the broadband access domain to gain visibility into the forwarding and data plane. However, that visibility is today constrained to the Ethernet, IP and application transport properties of the data plane. This document specifies four IPFIX Information Elements (IEs) to facilitate visibility in the GEM and XGEM data plane. Figure 1 shows the GEM frame, the GEM header and its properties. Graf & Zheng Expires 19 May 2027 [Page 2] Internet-Draft IPFIX Export G-PON GEM November 2026 GEM Frame |<------------------------------------------------------>| | | +--------------+-----------------------------------------+ | GEM Header | GEM Payload | +--------------+-----------------------------------------+ / | / --------------\ / --------------\ / -----------\ v v +----------------+----------------+---------+------------------+ | PLI | Port-ID | PTI | HEC | | (12-bits) | (12-bits) | (3-bits)| (13-bits) | +----------------+----------------+---------+------------------+ Figure 1: G.984.3 GEM header and frame structure Figure 2 shows the XGEM frame, the XGEM header and its properties. XGEM Frame |<------------------------------------------------------>| | | +--------------+-----------------------------------------+ | XGEM Header | XGEM Payload | +--------------+-----------------------------------------+ / | / --------------\ / --------------\ / ---------------\ v v +----------+----------+-------------+----------+--------+----------+ | PLI | Key index| XGEM Port-ID| Options | LF | HEC | | (14-bits)| (2-bits) | (16-bits) | (18-bits)| (1-bit)| (13-bits)| +----------+----------+-------------+----------+--------+----------+ Figure 2: G.9804.2 XGEM header and frame structure These IEs are used to export the GEM the Port-ID and with XGEM the Port-ID and PTI to enable the distinction between user service and user and OAM application frames. Some examples are provided in Appendix A. Graf & Zheng Expires 19 May 2027 [Page 3] Internet-Draft IPFIX Export G-PON GEM November 2026 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. This document makes use of the terms defined in [RFC7011], [itu-g984-3], and [itu-g9804-1]. The following terms are used as defined in [RFC7011]: * IPFIX * IPFIX Information Elements * Template * Template Record * Options Template * Options Template Record * Data Record * Data Set The following terms are used as defined in [itu-g9804-1]: * Optical Access Network (OAN) * Optical Distribution Network (ODN) * Optical Line Termination (OLT) * Optical Network Terminal (ONT) * Optical Network Unit (ONU) * Gigabit-capable Passive Optical Network (G-PON) * 10-Gigabit Passive Optical Network (XG-PON) * 10-Gigabit-capable PON encapsulation method (XGEM) port The following terms are used as defined in [itu-g984-3]: Graf & Zheng Expires 19 May 2027 [Page 4] Internet-Draft IPFIX Export G-PON GEM November 2026 * G-PON Encapsulation Method (GEM) * GEM Port 3. New IPFIX G-PON GEM Elements This section specifies the new IPFIX G-PON GEM IEs. ingressGponGemPti 3-bit GEM PTI content type field defined in Section 8.3.1 of [itu-g984-3] associated with ingress interface. The values are encoded in decimal as described in Figure 1 in the 3 least significant bits of the IE. egressGponGemPti 3-bit GEM PTI content type field defined in Section 8.3.1 of [itu-g984-3] associated with egress interface. The values are encoded in decimal as described in Figure 1 in the 3 least significant bits of the IE. ingressGponGemPortId 12-bit GEM Port-ID field defined in Section 8.3.1 of [itu-g984-3] and 16-bit XGEM Port-ID field in Section 9.1.2 of [itu-g9804-2] associated with ingress interface. For 12-bit GEM Port-ID, the values are encoded in the 12 least significant bits of the IE. egressGponGemPortId 12-bit GEM Port-ID field defined in Section 8.3.1 of [itu-g984-3] and 16-bit XGEM Port-ID field in Section 9.1.2 of [itu-g9804-2] associated with egress interface. For 12-bit GEM Port-ID, the values are encoded in the 12 least significant bits of the IE. 4. Sample Use Cases The IPFIX IEs ingressGponGemPti (TBD1), egressGponGemPti (TBD2), ingressGponGemPortId (TBD3), egressGponGemPortId (TBD4), sourceMacAddress (56), destinationMacAddress (80), ingressInterface (10), egressInterface (14) and forwardingStatus (89) [RFC7270] [IANA-IPFIX], and some existing counter information from [IANA-IPFIX] provide answers to the following questions (among others): * How many user or OAM data fragments are forwarded or dropped to which ONU on which egress interface and GEM Port-ID? * If dropped, for which reasons? Graf & Zheng Expires 19 May 2027 [Page 5] Internet-Draft IPFIX Export G-PON GEM November 2026 The received ONU frames on an OLT are mapped and forwarded depending on GEM Port-ID to a dot1qVlanId (243) and dot1qPriority (244) upstream to the provider network. 5. IANA Considerations Note to the RFC-Editor: * Please replace TBD1 - TBD4 with the values allocated by IANA * Please replace the [RFC-to-be] with the RFC number assigned to this document 5.1. New IPFIX G-PON GEM Information Elements This document requests IANA to add new IEs to the "IPFIX Information Elements" registry [RFC7012] available at [IANA-IPFIX]. Table 1 lists the new G-PON GEM IEs: +-------+--------------------------------+ |Element| Name | | ID | | +-------+--------------------------------+ | TBD1 | ingressGponGemPti | | | | +-------+--------------------------------+ | TBD2 | egressGponGemPti | | | | +-------+--------------------------------+ | TBD3 | ingressGponGemPortId | | | | +-------+--------------------------------+ | TBD4 | egressGponGemPortId | | | | +-------+--------------------------------+ Table 1: New G-PON GEM IEs in the "IPFIX Information Elements" Registry 5.1.1. ingressGponGemPti Name: ingressGponGemPti ElementID: TBD1 Description: Values for this Information Element are listed in the "IPFIX G-PON Encapsulation Method PTI" subregistry, see [IANA-IPFIX]. Graf & Zheng Expires 19 May 2027 [Page 6] Internet-Draft IPFIX Export G-PON GEM November 2026 Abstract Data Type: unsigned8 Data Type Semantics: identifier Range: The valid range is 0-7. Additional Information: See the assigned types in [IPFIX G-PON Encapsulation Method PTI Subregistry] associated with ingress interface. The values are encoded in decimal as described in Figure 1 in the 3 least significant bits of the IE. Note to IANA: Please replace [IPFIX G-PON Encapsulation Method PTI] with the URL of the IANA subregistry. Reference: [RFC-to-be] 5.1.2. egressGponGemPti Name: egressGponGemPti ElementID: TBD2 Description: Values for this Information Element are listed in the "IPFIX G-PON Encapsulation Method PTI" subregistry, see [IANA-IPFIX]. Abstract Data Type: unsigned8 Data Type Semantics: identifier Range: The valid range is 0-7. Additional Information: See the assigned types in [IPFIX G-PON Encapsulation Method PTI Subregistry] associated with egress interface. The values are encoded in decimal as described in Figure 1 in the 3 least significant bits of the IE. Note to IANA: Please replace [IPFIX G-PON Encapsulation Method PTI Subregistry] with the URL of the IANA subregistry. Reference: [RFC-to-be] 5.1.3. ingressGponGemPortId Name: ingressGponGemPortId ElementID: TBD3 Graf & Zheng Expires 19 May 2027 [Page 7] Internet-Draft IPFIX Export G-PON GEM November 2026 Description: The 12-bit GEM Port-ID field defined in Section 8.3.1 of [itu-g984-3] and 16-bit XGEM Port-ID field in Section 9.1.2 of [itu-g9804-2] associated with an ingress interface. Abstract Data Type: unsigned16 Data Type Semantics: identifier Additional Information: For GEM Port-ID, the values are encoded in the 12 least significant bits of the IE. Reference: [RFC-to-be] 5.1.4. egressGponGemPortId Name: egressGponGemPortId ElementID: TBD4 Description: The 12-bit GEM Port-ID field defined in Section 8.3.1 of [itu-g984-3] and 16-bit XGEM Port-ID field in Section 9.1.2 [itu-g9804-2] associated with an egress interface. Abstract Data Type: unsigned16 Data Type Semantics: identifier Additional Information: For GEM Port-ID, the values are encoded in the 12 least significant bits of the IE. Reference: [RFC-to-be] 5.1.5. IPFIX G-PON Encapsulation Method PTI Subregistry This document requests IANA to create a new subregistry called "IPFIX G-PON Encapsulation Method PTI" under the "IPFIX Information Elements" registry [RFC7012] available at [IANA-IPFIX]. The allocation policy of this new subregistry is Expert Review (Section 4.5 of [RFC8126]). Graf & Zheng Expires 19 May 2027 [Page 8] Internet-Draft IPFIX Export G-PON GEM November 2026 The designated experts for this registry should be familiar with the G-PON Encapsulation Method. The guidelines that are being followed by the designated experts for the IPFIX registry should be followed for this subregistry. In particular, criteria that should be applied by the designated experts include to monitor the G-PON Encapsulation Method related activities at ITU-T and mirror the GEM PTI content type fields into this registry. Hence, keeping both registries in sync. Initial values in the registry are defined in Table 2 and reflect the 3-bit GEM PTI content type field defined in Section 8.3.1 of [itu-g984-3]. The registry cannot be extended. Only "Reserved" values can be updated in future. +-------+--------------------------------------------+-------------+ | Value | GEM PTI Content Type Meaning | Reference | +-------+--------------------------------------------+-------------+ | 0 | User data fragment, not the end of a frame | [RFC-to-be] | +-------+--------------------------------------------+-------------+ | 1 | User data fragment, end of a frame | [RFC-to-be] | +-------+--------------------------------------------+-------------+ | 2 | Reserved | [RFC-to-be] | +-------+--------------------------------------------+-------------+ | 3 | Reserved | [RFC-to-be] | +-------+--------------------------------------------+-------------+ | 4 | GEM OAM, not the end of a frame | [RFC-to-be] | +-------+--------------------------------------------+-------------+ | 5 | GEM OAM, end of a frame | [RFC-to-be] | +-------+--------------------------------------------+-------------+ | 6 | Reserved | [RFC-to-be] | +-------+--------------------------------------------+-------------+ | 7 | Reserved | [RFC-to-be] | +-------+--------------------------------------------+-------------+ Table 2: "IPFIX G-PON Encapsulation Method PTI" Subregistry Figure 1 6. Acknowledgements The authors would like to thank Paul Aitken, Nuno André and the AI agent Claude for their review and valuable comments, and Xiao Chen, Jian Ping Zhang, Jiale Li and Chongfeng Xie for the implementation and validation. Graf & Zheng Expires 19 May 2027 [Page 9] Internet-Draft IPFIX Export G-PON GEM November 2026 7. Implementation Status Note to the RFC-Editor: Please remove this section before publishing. 7.1. Huawei MA5800T-X17 Huawei plans to implement the following IEs as part of a production implementation in the VRP based MA5800T-X17 OLT platform: * ingressGponGemPortId * egressGponGemPortId The implementation has been validated at IETF 125 hackathon. 8. Security Considerations There exists no extra security considerations regarding allocation of these new IPFIX IEs compared to [RFC7012]. The IEs described in this document export subscriber-identifying provider plane data metrics on how frames are being forwarded within an Optical Acces Network. Applications and operators using the IEs described in this document MUST evaluate the sensitivity of this information in their implementation context, and apply the data-at- rest storage guidance in Section 11.8 of [RFC7011] as appropriate. 9. References 9.1. Normative References [itu-g984-3] "G.984.3", ITU-T, International Telecommunication Union, January 2014, . [itu-g9804-1] "G.9804.1", ITU-T, International Telecommunication Union, November 2019, . [itu-g9804-2] "G.9804.2", ITU-T, International Telecommunication Union, September 2021, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . Graf & Zheng Expires 19 May 2027 [Page 10] Internet-Draft IPFIX Export G-PON GEM November 2026 [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information", STD 77, RFC 7011, DOI 10.17487/RFC7011, September 2013, . [RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model for IP Flow Information Export (IPFIX)", RFC 7012, DOI 10.17487/RFC7012, September 2013, . [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . 9.2. Informative References [IANA-IPFIX] "IANA, IP Flow Information Export (IPFIX) Entities", . [RFC7270] Yourtchenko, A., Aitken, P., and B. Claise, "Cisco- Specific Information Elements Reused in IP Flow Information Export (IPFIX)", RFC 7270, DOI 10.17487/RFC7270, June 2014, . Appendix A. IPFIX Encoding Examples This appendix represents an encoding for the newly introduced IEs, for the example values in Table 3. The encoding uses the following IEs, respectively: ingressGponGemPti, egressGponGemPti, ingressGponGemPortId, egressGponGemPortId, sourceMacAddress, and destinationMacAddress. Graf & Zheng Expires 19 May 2027 [Page 11] Internet-Draft IPFIX Export G-PON GEM November 2026 +-------+------+-------+------+-------------------+-------------------+ |Ingress|Egress|Ingress|Egress| Source | Destination | |GEM |GEM |GEM |GEM | Mac Address | Mac Address | |PTI |PTI |Port |Port | | | +-------+------+-------+------+-------------------+-------------------+ | 0 | 0 | 10 | 0 | 00:00:5E:00:53:01 | 00:00:5E:00:53:02 | +-------+------+-------+------+-------------------+-------------------+ Table 3: Two Ingress or Egress Observed GEM headers and Their Associated MAC Addresses With encoding in Figure 3, the examples in Table 3 are represented with the following IEs: “=>” is used to indicate which IE is mapped to a given information. * Ingress GEM PTI => ingressGponGemPti (TBD1) * Egress GEM PTI => egressGponGemPti (TBD2) * Ingress GEM Port => ingressGponGemPortId (TBD3) * Egress GEM Port => egressGponGemPortId (TBD4) * Source Mac Address => sourceMacAddress (56) * Destination Mac Address => destinationMacAddress (80) Graf & Zheng Expires 19 May 2027 [Page 12] Internet-Draft IPFIX Export G-PON GEM November 2026 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SET ID = 2 | Length = 32 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Template ID = 256 | Field Count = 6 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| ingressGponGemPti = TBD1 | Field Length = 1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| egressGponGemPti = TBD2 | Field Length = 1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| ingressGponGemPortId = TBD3 | Field Length = 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| egressGponGemPortId = TBD4 | Field Length = 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| sourceMacAddress = 56 | Field Length = 6 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| destinationMacAddress = 80 | Field Length = 6 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3: Template Record with Ingress and Egress GEM Port IDs and GEM PTIs and Source and Destination MAC Addresses In this example, the Template ID is 256, which will be used in the Data Record. The data set is represented as follows: Graf & Zheng Expires 19 May 2027 [Page 13] Internet-Draft IPFIX Export G-PON GEM November 2026 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SET ID = 256 | Length = 24 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ingressGpon | egressGpon | ingressGponGemPortId = [10] | | GemPti = [0] | GemPti = [0] | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | egressGponGemPortId = [0] | sourceMacAddress (Bytes 0-1) | | | = [00:00] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | sourceMacAddress (Bytes 2-5) = [5E:00:53:01] | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | destinationMacAddress (Bytes 0-3) = [00:00:5E:00] | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | destinationMacAddress | Padding | | (Bytes 4-5) = [53:02] | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 4: Data Record with Ingress and Egress GEM Port IDs and GEM PTIs and Source and Destination MAC Addresses Authors' Addresses Thomas Graf Swisscom Binzring 17 CH-8045 Zurich Switzerland Email: thomas.graf@swisscom.com Haomian Zheng Huawei Technologies H1, Huawei Xiliu Beipo Village, Songshan Lake Dongguan Guangdong, 523808 China Email: zhenghaomian@huawei.com Graf & Zheng Expires 19 May 2027 [Page 14]