



BESS Workgroup                                                  X. Zhang
Internet-Draft                                              China Mobile
Intended status: Standards Track                             C. Lin, Ed.
Expires: 23 April 2026                              New H3C Technologies
                                                         20 October 2025


                         OAM for EVPN over SRv6
                     draft-zl-bess-evpn-srv6-oam-00

Abstract

   RFC 9489 describes Operation, Administration, and Maintenance (OAM)
   mechanisms for detecting data plane failures using Label Switched
   Path (LSP) Ping in MPLS-based Ethernet VPN (EVPN) networks.  However,
   there is no effective OAM mechanism for detecting data plane failures
   in SRv6-based EVPN networks.  This document proposals OAM mechanisms
   for SRv6-based EVPN networks.

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 23 April 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.











Zhang & Lin               Expires 23 April 2026                 [Page 1]

Internet-Draft                EVPN SRv6 OAM                 October 2025


   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Encapsulation of OAM Ping Packets . . . . . . . . . . . . . .   3
     3.1.  Format with Two-Layer Ethernet Header . . . . . . . . . .   3
     3.2.  Format with One-Layer Ethernet Header . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   [RFC9489] describes Operation, Administration, and Maintenance (OAM)
   mechanisms for detecting data plane failures using Label Switched
   Path (LSP) Ping [RFC8029] in MPLS networks deploying Ethernet VPN
   (EVPN).

   Segment Routing over IPv6 (SRv6) network is a new programmable
   network architecture based on IPv6 [RFC8402].  It carries path
   instructions through native IPv6 headers which is followed by the
   Segment Routing Header (SRH) to implement software-defined traffic
   scheduling and service chain processing [RFC8986].

   The SRv6 network also could deploy EVPN, which is applied to
   scenarios such as enterprise private lines, data center
   interconnection, and 5G bearer networks.  However, there is no
   effective OAM mechanism for detecting data plane failures in
   SRv6-based EVPN networks.

   This document defines procedures to detect data plane failures based
   on LSP Ping in SRv6-based EVPN networks.








Zhang & Lin               Expires 23 April 2026                 [Page 2]

Internet-Draft                EVPN SRv6 OAM                 October 2025


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.

3.  Encapsulation of OAM Ping Packets

   This section defines two Encapsulation Formats using the MPLS Echo
   Request packet for OAM Ping Packets in SRv6 networks deploying EVPN.
   The OAM Ping procedure is similar to that described in [RFC9489].

3.1.  Format with Two-Layer Ethernet Header

   This section defines an encapsulation format including two-layer
   Ethernet Header, as illustrated in Figure 1.

                 +---------------------------------------+
                 |       External Ethernet Header        |
                 +---------------------------------------+
                 |       External IPv6 Header            |
                 +---------------------------------------+
                 |       Segment Routing Header          |
                 +---------------------------------------+
                 |       Internal Ethernet Header        |
                 +---------------------------------------+
                 |       Internal IPv6 Header            |
                 +---------------------------------------+
                 |       UDP Header                      |
                 +---------------------------------------+
                 |       MPLS Echo Request/Reply         |
                 +---------------------------------------+

                   Figure 1: Two-Layer Ethernet Format

   The External Ethernet Header: as defined in Section 3 of [RFC2464],
   encapsulates the Destination and Source MAC addresses of intermediate
   forwarding devices.

   The External IPv6 Header: as defined in Section 3 of [RFC8200],
   mainly encapsulates the Destination and Source IPv6 addresses of
   intermediate forwarding devices.

   The Segment Routing Header: as defined in Section 2 of [RFC8754],
   primarily encapsulates the forwarding path information via a segment
   list in SRv6 network.



Zhang & Lin               Expires 23 April 2026                 [Page 3]

Internet-Draft                EVPN SRv6 OAM                 October 2025


   The Internal Ethernet Header: as defined in Section 3 of [RFC2464],
   encapsulates the Destination MAC address using a Virtual MAC address.

   The Internal IPv6 Header: as defined in Section 3 of [RFC8200],
   mainly encapsulates the Destination IPv6 address using Loopback
   address.

   The UDP Header: as defined in [RFC768], mainly encapsulates the
   Destination and Source Port.  The Destination Port MUST be set to
   3503 (assigned by IANA for MPLS echo requests).

   The MPLS Echo Request/Reply: as defined in Section 3 of [RFC8029],
   encapsulates the core information of OAM Ping Packet.  The
   information contained in this field is consistent with Section 4 of
   [RFC9489].

3.2.  Format with One-Layer Ethernet Header

   This section defines an encapsulation format including one-layer
   Ethernet Header, as illustrated in Figure 2.

                 +---------------------------------------+
                 |       Ethernet Header                 |
                 +---------------------------------------+
                 |       IPv6 Header                     |
                 +---------------------------------------+
                 |       Segment Routing Header          |
                 +---------------------------------------+
                 |       UDP Header                      |
                 +---------------------------------------+
                 |       MPLS Echo Request/Reply         |
                 +---------------------------------------+

                    Figure 2: One-Layer Ethernet Format

   The Ethernet Header: as defined in Section 3 of [RFC2464],
   encapsulates the Destination and Source MAC addresses of intermediate
   forwarding devices.

   The IPv6 Header: as defined in Section 3 of [RFC8200], mainly
   encapsulates the Destination and Source IPv6 addresses of
   intermediate forwarding devices.

   The Segment Routing Header: as defined in Section 2 of [RFC8754],
   primarily encapsulates the forwarding path information via a segment
   list in SRv6 network.





Zhang & Lin               Expires 23 April 2026                 [Page 4]

Internet-Draft                EVPN SRv6 OAM                 October 2025


   The UDP Header: as defined in [RFC768], mainly encapsulates the
   Destination and Source Port.  The Destination Port MUST be set to
   3503 (assigned by IANA for MPLS echo requests).

   The MPLS Echo Request/Reply: as defined in Section 3 of [RFC8029],
   encapsulates the core information of OAM Ping Packet.  The
   information contained in this field is consistent with Section 4 of
   [RFC9489].

4.  Security Considerations

   TBD

5.  IANA Considerations

   This document does not require an IANA allocation.

6.  References

6.1.  Normative References

   [RFC768]   Postel, J., "User Datagram Protocol", STD 6, RFC 768,
              DOI 10.17487/RFC0768, August 1980,
              <https://www.rfc-editor.org/info/rfc768>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC2464]  Crawford, M., "Transmission of IPv6 Packets over Ethernet
              Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998,
              <https://www.rfc-editor.org/info/rfc2464>.

   [RFC8029]  Kompella, K., Swallow, G., Pignataro, C., Ed., Kumar, N.,
              Aldrin, S., and M. Chen, "Detecting Multiprotocol Label
              Switched (MPLS) Data-Plane Failures", RFC 8029,
              DOI 10.17487/RFC8029, March 2017,
              <https://www.rfc-editor.org/info/rfc8029>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC8200]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
              (IPv6) Specification", STD 86, RFC 8200,
              DOI 10.17487/RFC8200, July 2017,
              <https://www.rfc-editor.org/info/rfc8200>.



Zhang & Lin               Expires 23 April 2026                 [Page 5]

Internet-Draft                EVPN SRv6 OAM                 October 2025


   [RFC8402]  Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
              Decraene, B., Litkowski, S., and R. Shakir, "Segment
              Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,
              July 2018, <https://www.rfc-editor.org/info/rfc8402>.

   [RFC8754]  Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J.,
              Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header
              (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020,
              <https://www.rfc-editor.org/info/rfc8754>.

   [RFC8986]  Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer,
              D., Matsushima, S., and Z. Li, "Segment Routing over IPv6
              (SRv6) Network Programming", RFC 8986,
              DOI 10.17487/RFC8986, February 2021,
              <https://www.rfc-editor.org/info/rfc8986>.

   [RFC9489]  Jain, P., Sajassi, A., Salam, S., Boutros, S., and G.
              Mirsky, "Label Switched Path (LSP) Ping Mechanisms for
              EVPN and Provider Backbone Bridging EVPN (PBB-EVPN)",
              RFC 9489, DOI 10.17487/RFC9489, November 2023,
              <https://www.rfc-editor.org/info/rfc9489>.

Authors' Addresses

   Xiaoqiu Zhang
   China Mobile
   China
   Email: zhangxiaoqiu@chinamobile.com


   Changwang Lin (editor)
   New H3C Technologies
   China
   Email: linchangwang.04414@h3c.com

















Zhang & Lin               Expires 23 April 2026                 [Page 6]
