<?xml version="1.0" encoding="UTF-8"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
     category="std"
     docName="draft-tantsura-bess-evpn-route-type-exp-use-00"
     ipr="trust200902"
     submissionType="IETF"
     updates="7432"
     xml:lang="en"
     version="3">
  <front>
    <title abbrev="EVPN Route Type Experimental">Reservation of EVPN Route Types for Experimental Use</title>
    <seriesInfo name="Internet-Draft" value="draft-tantsura-bess-evpn-route-type-exp-use-00"/>
    <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
      <organization>Nvidia</organization>
      <address>
        <email>jefftant.ietf@gmail.com</email>
      </address>
    </author>
    <author initials="K." surname="Talaulikar" fullname="Ketan Talaulikar">
      <organization>Cisco Systems, Inc.</organization>
      <address>
        <email>ketant@cisco.com</email>
      </address>
    </author>
    <date year="2026" month="March" day="20"/>
    <area>Routing</area>
    <workgroup>BESS</workgroup>
    <keyword>EVPN</keyword>
    <keyword>BGP</keyword>
    <keyword>IANA</keyword>
    <abstract>
      <t>This document reserves codepoints in the EVPN Route Type registry for experimental use to enable implementations to carry out development and test of new EVPN features. It updates RFC7432 to modify the registration policy for the EVPN Route Type registry.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" toc="default">
      <name>Introduction</name>
      <t>Ethernet VPN (EVPN) <xref target="RFC7432"/> uses BGP for the distribution of reachability and membership information. EVPN network layer reachability information (NLRI) is carried in BGP using the EVPN SAFI (70) and includes a one-octet Route Type field that identifies the type of EVPN route (e.g., Ethernet Auto-Discovery, MAC/IP Advertisement, Inclusive Multicast Ethernet Tag, etc.). The EVPN Route Type registry <xref target="IANA-EVPN-ROUTE"/> is maintained by IANA and was created by <xref target="RFC7432"/>.</t>
      <t>New EVPN route types are assigned through the "RFC Required" registration procedure. There is currently no reserved range in the EVPN Route Type registry for experimental use. Implementors and deployers who wish to experiment with new route types, without requesting an IANA assignment, have no designated codepoint space and risk conflicting with assignments via other specifications being developed in parallel.</t>
      <t>This document reserves codepoint space in the EVPN Route Type registry <xref target="IANA-EVPN"/> for experimental use. This approach aligns this registry with the practice of providing a clear, bounded space for experimental use to avoid conflicts and to discourage the practice of taking up codepoints without formal allocations in early development phases of implementations.</t>
      <t>This document updates <xref target="RFC7432"/> as it modifies the registration policy for the EVPN Route Type registry by carving out space for experimental use.</t>
    </section>
    <section anchor="iana-considerations" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>IANA is requested to modify the registration policy of the "EVPN Route Types" registry <xref target="IANA-EVPN-ROUTES"/> in the "Ethernet VPN (EVPN)" registry group <xref target="IANA-EVPN"/> by carving out the range of values 224 to 255 for Experimental Use <xref target="RFC8126"/>. The registration policy for the rest of the space from 0 to 223 remains RFC Required as defined in <xref target="RFC7432"/>.</t>
      <t>IANA is requested to add this document as a reference for this registry along with <xref target="RFC7432"/>. As specified in <xref target="RFC8126"/>, IANA is not required to maintain any record of allocations in the experimental codepoint space. <xref target="tbl-ranges"/> describes the entry in the registry for the experimental range.</t>
      <table anchor="tbl-ranges">
        <name>EVPN Route Type Registry Ranges</name>
        <thead>
          <tr>
            <td>Value</td>
            <td>Description</td>
            <td>Reference</td>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td>224-255</td>
            <td>Experimental Use (not assigned by IANA)</td>
            <td>This document</td>
          </tr>
        </tbody>
      </table>
    </section>
    <section anchor="security-considerations" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>Reserving a range of EVPN Route Types for experimental use does not introduce new security issues beyond those already present in EVPN <xref target="RFC7432"/>. Implementations that process EVPN NLRI with route types in the reserved range (224-255) should apply the same validation and policy controls as for other route types. Deployments using experimental route types should ensure that only trusted peers exchange such NLRI, and that the semantics of the route type are agreed upon within the deployment to avoid misinterpretation.</t>
    </section>
  </middle>
  <back>
    <references anchor="normative-references" title="Normative References">
      <reference anchor="RFC7432" target="https://www.rfc-editor.org/info/rfc7432" quoteTitle="true">
        <front>
          <title>BGP MPLS-Based Ethernet VPN</title>
          <author initials="A." surname="Sajassi" fullname="Ali Sajassi" role="editor"/>
          <author initials="R." surname="Aggarwal" fullname="Rahul Aggarwal" role="editor"/>
          <date month="February" year="2015"/>
        </front>
        <seriesInfo name="RFC" value="7432"/>
        <seriesInfo name="DOI" value="10.17487/RFC7432"/>
      </reference>
      <reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8126" quoteTitle="true">
        <front>
          <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
          <author initials="M." surname="Cotton" fullname="Michelle Cotton"/>
          <author initials="B." surname="Leiba" fullname="Barry Leiba"/>
          <author initials="T." surname="Narten" fullname="Thomas Narten"/>
          <date month="June" year="2017"/>
        </front>
        <seriesInfo name="BCP" value="26"/>
        <seriesInfo name="RFC" value="8126"/>
        <seriesInfo name="DOI" value="10.17487/RFC8126"/>
      </reference>
    </references>
    <references anchor="informative-references" title="Informative References">
      <reference anchor="IANA-EVPN" target="https://www.iana.org/assignments/evpn/">
        <front>
          <title>Ethernet VPN (EVPN)</title>
          <author>
            <organization>IANA</organization>
          </author>
        </front>
        <format target="https://www.iana.org/assignments/evpn/" type="HTML"/>
      </reference>
      <reference anchor="IANA-EVPN-ROUTE" target="https://www.iana.org/assignments/evpn/evpn.xhtml#route-types">
        <front>
          <title>Ethernet VPN (EVPN) - EVPN Route Types</title>
          <author>
            <organization>IANA</organization>
          </author>
        </front>
        <format target="https://www.iana.org/assignments/evpn/evpn.xhtml#route-types" type="HTML"/>
      </reference>
      <reference anchor="IANA-EVPN-ROUTES" target="https://www.iana.org/assignments/evpn/evpn.xhtml#route-types">
        <front>
          <title>EVPN Route Types</title>
          <author>
            <organization>IANA</organization>
          </author>
        </front>
        <format target="https://www.iana.org/assignments/evpn/evpn.xhtml#route-types" type="HTML"/>
      </reference>
      <reference anchor="RFC4760" target="https://www.rfc-editor.org/info/rfc4760" quoteTitle="true">
        <front>
          <title>Multiprotocol Extensions for BGP-4</title>
          <author initials="T." surname="Bates" fullname="Tony Bates"/>
          <author initials="R." surname="Chandra" fullname="Ravi Chandra"/>
          <author initials="D." surname="Katz" fullname="Dave Katz"/>
          <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter"/>
          <date month="January" year="2007"/>
        </front>
        <seriesInfo name="RFC" value="4760"/>
      </reference>
    </references>
  </back>
</rfc>
