<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
<!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC4271 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4271.xml">
<!ENTITY RFC7606 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7606.xml">
<!ENTITY RFC5305 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5305.xml">
<!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
<!ENTITY RFC7684 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7684.xml">
<!ENTITY RFC8362 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8362.xml">
<!ENTITY RFC8762 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8762.xml">
<!ENTITY RFC9552 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9552.xml">
]>
<rfc submissionType="IETF" docName="draft-gandhi-lsr-stamp-01" category="std" ipr="trust200902" consensus="true">
    <!-- Generated by id2xml 1.5.0 on 2020-02-06T01:41:26Z -->
    <?rfc compact="yes"?>
    <?rfc text-list-symbols="oo*+-"?>
    <?rfc subcompact="no"?>
    <?rfc sortrefs="no"?>
    <?rfc symrefs="yes"?>
    <?rfc strict="yes"?>
    <?rfc toc="yes"?>
    <front>
        <title abbrev="IS-IS, OSPF, BGP-LS, BGP for STAMP"> IS-IS, OSPF, BGP-LS, and BGP Extensions for Advertising STAMP Session-Reflectors</title>
    <seriesInfo name="Internet-Draft" value="draft-gandhi-lsr-stamp-01"/>    

    <author fullname="Rakesh Gandhi" initials="R." role="editor" surname="Gandhi">
    <organization>Cisco Systems, Inc.</organization>
    <address>
    <postal><street>Canada</street>
    </postal>
        <email>rgandhi@cisco.com</email>
    </address>
    </author>

    <date year="2026"/>
    <workgroup>LSR Working Group</workgroup>
    <abstract>
   <t>
   The Simple Two-Way Active Measurement Protocol (STAMP), as defined in
   RFC 8762, can be utilized for active measurement without relying on a control channel to pre-signal session parameters.  
   This document defines extensions to IS-IS, OSPF, BGP-LS, and BGP to advertise information for discovering STAMP Session-Reflectors in a network.
   The advertised information can be used by STAMP senders to set up appropriate performance measurement sessions for delay and packet loss metrics.
    </t>
    <t>
    </t>
    </abstract>
    </front>

    <middle>

   <section title="Introduction" anchor="sect-1">
   <t>
   The Simple Two-Way Active Measurement Protocol (STAMP) is designed to
   measure various performance metrics in IP networks without relying on
   a control channel to pre-signal session parameters, as specified in
   <xref target="RFC8762" format="default"/>.  
   STAMP test packets are sent between a STAMP Session-Sender and
   a STAMP Session-Reflector to measure delay and packet loss along the path.
   </t>

   <t>
   This document defines extensions to IS-IS, OSPF, BGP-LS, and BGP to advertise information for discovering STAMP Session-Reflectors in a network.
   The advertised information can be used by STAMP senders to set up appropriate STAMP-Test sessions for delay and packet loss metrics.
   Signaling STAMP Session-Reflector parameters between the Session-Sender and the
   Session-Reflector is outside the scope of this document.
   </t>

   </section>

   <section title="Conventions Used in This Document" anchor="sect-2">
       
   <section title="Requirements Language" anchor="sect-2.1">

   <t>
   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  <xref target="RFC2119" format="default"/> <xref target="RFC8174" format="default"/>
   when, and only when, they appear in all capitals, as shown here.
   </t>

    </section>

    <section title="Terminology" anchor="sect-2.2">

    <t>
    This document uses terms defined in <xref target="RFC8762" format="default"/>,
    specifically Session-Sender and Session-Reflector.
    </t>

    </section>

    <section title="Abbreviations" anchor="sect-2.3">

    <table anchor="abbreviations" align="center">
      <name>Abbreviations</name>
      <thead>
        <tr>
          <th align="left">Abbreviation</th>
          <th align="left">Meaning</th>
          <th align="left">Reference</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td align="left">STAMP</td>
          <td align="left">Simple Two-Way Active Measurement Protocol</td>
          <td align="left"><xref target="RFC8762"/></td>
        </tr>
        <tr>
          <td align="left">TLV</td>
          <td align="left">Type-Length-Value</td>
          <td align="left"><xref target="RFC5305"/></td>
        </tr>
      </tbody>
    </table>

    </section>

    </section>

    <section title="Overview" anchor="sect-3">
    <t>
    In this document, IS-IS, OSPF, BGP-LS, and BGP protocol extensions are defined to advertise STAMP Session-Reflector information in a network.
    The advertised information is used by STAMP senders to set up appropriate performance measurement sessions for delay and packet loss metrics.
    </t>

    <t>
    The following STAMP Session-Reflector information is advertised to enable discovery:
    </t>
    <t>
    *  STAMP Session-Reflector IP address
    </t>
    <t>
    *  STAMP Session-Reflector UDP port number
    </t>
    <t>
    Although STAMP Session-Reflector information is a property of the node and can be advertised as part of the node capability,
    in some cases it is advantageous to associate the information with a prefix and advertise it with that prefix. In a multi-area network, routers may not know the identity of the prefix originator
    in a remote area or may not know the capabilities of such originator. 
    Similarly, in a multi-domain network, the identity of the prefix originator and its capabilities may not be known to the ingress node.
    </t>

    <t>
    For example, when re-advertising a prefix between two IS-IS protocol instances or re-advertising from
    another protocol to an IS-IS protocol instance, a router SHOULD preserve the STAMP Session-Reflector information advertised for
    that prefix if it exists.
    </t>

    </section>

    <section title="Common STAMP Session-Reflector Entry" anchor="stamp-reflector-entry-format">
    <t>
    Each protocol-specific container defined in this document carries exactly
    one protocol-independent STAMP Session-Reflector Entry.  Protocols that support
    multiple reflectors advertise them in multiple containers.  The entry
    format is shown below.
    Multi-octet fields are transmitted in network byte order (most significant
    octet first).  The enclosing container length delimits the entry.
    </t>

    <figure anchor="stamp-reflector-entry">
      <name>STAMP Session-Reflector Entry</name>
      <artwork name="" type="" align="left" alt=""><![CDATA[
  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 2
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |   Flags: V    |    Reserved   |   Reflector UDP Port Number   |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |        Reflector Address (4 octets for IPv4, 16 for IPv6)     |
  .                                                               .
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      ]]></artwork>
    </figure>

    <t>
    Entry length: 8 octets when V is 0 (IPv4) and 20 octets when V is 1
    (IPv6).  A receiver MUST discard the containing extension if the entry
    length does not match the length implied by V or the entry is truncated.
    </t>
    <t>
    Flags: 1 octet.  Bit 0 (mask 0x80) is V (0 for IPv4 and 1 for IPv6).
    Bit numbers are counted from the most significant bit of the first octet.
    Bits 1 through 7 are unassigned:
    originators MUST set them to zero, receivers MUST ignore them, and a node
    forwarding an unchanged entry SHOULD preserve them.
    </t>
    <t>
    Reserved: 1 octet.  Originators MUST set this field to zero; receivers
    MUST ignore it.
    </t>
    <t>
    Reflector UDP Port Number: 2 octets in network byte order.  Valid values are
    1 through 65535; zero is invalid.  The port MUST follow the allocation
    specification defined in <xref target="RFC8762" format="default"/>.
    </t>
    <t>
    Reflector Address: 4 octets when V is 0 (IPv4) and 16 octets when V is 1
    (IPv6).  The address is encoded as binary network-order address octets and
    MUST have unicast format.  Unspecified, multicast, IPv4 limited-broadcast,
    and broadcast addresses for the attached IPv4 subnet MUST NOT be advertised.
    IPv4-mapped IPv6 addresses MUST NOT be used.  An IPv6 link-local address is
    usable only when the routing context identifies its link unambiguously.  An
    IPv6 anycast address MAY be advertised if it is configured to receive STAMP
    packets.
    </t>
    <t>
    An originator MUST NOT advertise duplicate entries for the same reflector
    address in one advertisement.  Entries for the same address family and
    address that agree on all defined fields are equivalent; a receiver MAY
    ignore duplicates.  If entries for the same address family and address
    differ in any defined field, the address is conflicting and MUST NOT be
    selected from that advertisement.  Multiple entries for different reflector addresses are
    allowed when the protocol-specific encoding permits multiple containers.
    A protocol encoding that permits only one container can advertise only
    one reflector address in that container.
    </t>

    </section>

    <section title="IS-IS Extensions" anchor="sect-4">

    <t>
    The IS-IS sub-TLV contains one STAMP Session-Reflector Entry as defined in
    <xref target="stamp-reflector-entry"/>.  Its format is shown in
    <xref target="isis-stamp"/>.
    </t>

    <figure anchor="isis-stamp">
      <name>IS-IS STAMP Session-Reflector sub-TLV</name>
      <artwork name="" type="" align="left" alt=""><![CDATA[
  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 2
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |    Type       |    Length     |                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +
  |           STAMP Session-Reflector Entry (8 or 20 octets)      |
  .                                                               .
  +---------------------------------------------------------------+
      ]]></artwork>
    </figure>

    <t>
    Type: 1 octet.  Sub-TLV type for STAMP Session-Reflector (TBA1).
    </t>
    <t>
    Length: 1 octet.  The length of the sub-TLV value, excluding the Type and
    Length fields.  It MUST equal the length of the complete STAMP Session-Reflector
    Entry in the value.  Currently defined IPv4 and IPv6 entries have lengths
    8 and 20, respectively.  The value MUST NOT contain trailing octets.
    </t>

    <t>
    In this document, the IS-IS STAMP Session-Reflector extension is carried in IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability <xref target="RFC5305" format="default"/>.
    New STAMP Session-Reflector sub-TLV type is allocated for IS-IS (value TBA1 to be assigned by IANA).
    </t>

    <t>
    Multiple instances of this sub-TLV MAY be included to advertise multiple
    STAMP Session-Reflector entries for a node.  Each instance MUST contain exactly one
    STAMP Session-Reflector Entry.
    </t>

    </section>

    <section title="OSPFv2 Extensions" anchor="sect-5">

    <t>
    The OSPFv2 sub-TLV contains one STAMP Session-Reflector Entry as defined in
    <xref target="stamp-reflector-entry"/>.  Its format is shown in
    <xref target="ospfv2-stamp"/>.
    </t>
 
   <figure anchor="ospfv2-stamp">
        <name>OSPFv2 STAMP Session-Reflector sub-TLV </name>
  <artwork name="" type="" align="left" alt=""><![CDATA[
  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 2
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |            Type               |            Length             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |           STAMP Session-Reflector Entry (8 octets)            |
  |                                                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     ]]></artwork>
    </figure>

    <t>
    Type: 2 octets.  Sub-TLV type for STAMP Session-Reflector (TBA2).
    </t>
    <t>
    Length: 2 octets.  It is the length of the sub-TLV value, excluding the
    Type and Length fields, and MUST equal the length of the complete STAMP
    Session-Reflector Entry in the value.  An OSPFv2 originator MUST use V=0 (IPv4)
    and a value length of 8 octets.  V=1 (IPv6) is not supported by OSPFv2; a
    receiver MUST skip such an entry using the sub-TLV Length.  The sub-TLV
    value MUST NOT contain trailing octets.
    </t>

    <t>
    In this document, the OSPFv2 STAMP Session-Reflector extension is carried in OSPFv2 Extended Prefix TLV (Type 1) <xref target="RFC7684" format="default"/>.
    The Extended Prefix TLV allows specification of additional attributes associated with OSPFv2 prefixes (for example Sub-TLV 2 used for Prefix-SID).
    IANA is requested to allocate sub-TLV type TBA2 for the STAMP Session-Reflector sub-TLV.
    </t>

    <t>
    Multiple instances of this sub-TLV MAY be included to advertise multiple
    STAMP Session-Reflector entries for a node.  Each instance MUST contain exactly one
    STAMP Session-Reflector Entry.
    </t>

    </section>

    <section title="OSPFv3 Extensions" anchor="sect-6">

    <t>
    The OSPFv3 sub-TLV contains one STAMP Session-Reflector Entry as defined in
    <xref target="stamp-reflector-entry"/>.  Its format is shown in
    <xref target="ospfv3-stamp"/>.
    </t>
 
   <figure anchor="ospfv3-stamp">
        <name>OSPFv3 STAMP Session-Reflector sub-TLV </name>
  <artwork name="" type="" align="left" alt=""><![CDATA[
  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 2
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |            Type               |            Length             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |           STAMP Session-Reflector Entry (8 or 20 octets)      |
  .                                                               .
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     ]]></artwork>
    </figure>

    <t>
    Type: 2 octets.  Sub-TLV type for STAMP Session-Reflector (TBA3).
    </t>
    <t>
    Length: 2 octets.  It is the length of the sub-TLV value, excluding the
    Type and Length fields, and MUST equal the length of the complete STAMP
    Session-Reflector Entry in the value.  Currently defined IPv4 and IPv6 entries
    have lengths 8 and 20, respectively, and the value MUST NOT contain
    trailing octets.
    </t>

    <t>
    In this document, the OSPFv3 STAMP Session-Reflector extension is carried in prefix-related TLVs 
    within OSPFv3 Extended-LSAs <xref target="RFC8362" format="default"/>.
    IANA is requested to allocate sub-TLV type TBA3 for the STAMP Session-Reflector sub-TLV.
    </t>

    <t>
    Multiple instances of this sub-TLV MAY be included to advertise multiple
    STAMP Session-Reflector entries for a node.  Each instance MUST contain exactly one
    STAMP Session-Reflector Entry.
    </t>

    </section>

    <section title="BGP-LS Extensions" anchor="sect-7">

    <t>
    The STAMP Session-Reflector TLV is a Prefix Attribute TLV in the BGP-LS Attribute
    (BGP Path Attribute code 29) associated with an IPv4 or IPv6 Topology
    Prefix NLRI (BGP-LS NLRI types 3 or 4), as specified in
    <xref target="RFC9552" section="5.1"/>.  The TLV contains one
    STAMP Session-Reflector Entry as defined in
    <xref target="stamp-reflector-entry"/>.  Its format is shown in
    <xref target="bgpls-stamp"/>.
    </t>

   <figure anchor="bgpls-stamp">
        <name>BGP-LS STAMP Session-Reflector TLV </name>
  <artwork name="" type="" align="left" alt=""><![CDATA[
  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 2
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |            Type               |            Length             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |           STAMP Session-Reflector Entry (8 or 20 octets)      |
  .                                                               .
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      ]]></artwork>
    </figure>

    <t>
    Type: 2 octets.  Prefix Attribute TLV type for STAMP Session-Reflector (TBA4).
    </t>
    <t>
    Length: 2 octets.  It is the length of the TLV value, excluding the Type
    and Length fields, and MUST equal the length of the complete STAMP
    Reflector Entry in the value.  Currently defined IPv4 and IPv6 entries
    have lengths 8 and 20, respectively.  The Type and Length fields
    are each 16 bits; the Length covers only the value, and no four-octet
    padding is added.  The TLV value MUST NOT contain trailing octets.
    </t>

    <t>
    The BGP-LS STAMP Session-Reflector TLV is carried as a Prefix Attribute TLV in the
    BGP-LS Attribute (Path Attribute code 29) associated with an IPv4 or IPv6
    Topology Prefix NLRI (NLRI type 3 or 4).  The BGP-LS Attribute and its
    Prefix Attribute TLVs are defined in
    <xref target="RFC9552" section="5.1"/>.  The IANA registry used for the
    TLV type allocation is named "BGP-LS NLRI and Attribute TLVs"; that
    registry name does not specify the TLV's placement.
    </t>
    <t>
    A BGP-LS Attribute MAY contain multiple instances of the STAMP Reflector
    Prefix Attribute TLV.  Each instance MUST contain exactly one complete
    STAMP Session-Reflector Entry.  Multiple TLV instances can advertise multiple
    reflectors for the same prefix.
    IANA is requested to allocate TLV type TBA4 for this Prefix Attribute TLV.
    </t>
    <t>
    If a BGP-LS TLV length is invalid or its value cannot be parsed as one
    complete entry, and the enclosing BGP UPDATE remains
    parseable, the receiver MUST apply Attribute Discard to the entire BGP-LS
    Attribute, rather than removing only the malformed TLV, as specified in
    <xref target="RFC9552" section="8.2.2"/>.  The receiver SHOULD log the
    error.  Semantic validation of STAMP Session-Reflector Entry contents is the
    responsibility of the consuming application, not the BGP-LS propagator.
    </t>
    <t>
    Unknown or unsupported TLVs MUST be preserved and propagated.  Their
    presence alone does not make the BGP-LS NLRI or Attribute malformed, as
    specified in <xref target="RFC9552" section="5.1"/>.
    </t>

    </section>

    <section title="BGP Extensions" anchor="sect-8">

    <t>
    The BGP STAMP Session-Reflector path attribute is a single optional transitive
    path attribute.  Its value contains exactly one STAMP
    Reflector Entry as defined in
    <xref target="stamp-reflector-entry"/>.  The path-attribute header and
    value are shown in <xref target="bgp-stamp"/>.  This attribute is
    applicable only to IPv4 unicast (AFI 1, SAFI 1) and IPv6 unicast (AFI 2,
    SAFI 1) routes, and applies to all such NLRI in the UPDATE.  A receiver
    MUST NOT interpret it for other AFI/SAFI combinations.
    </t>

   <figure anchor="bgp-stamp">
        <name>BGP STAMP Session-Reflector Path Attribute</name>
  <artwork name="" type="" align="left" alt=""><![CDATA[
  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 2
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |  Attr Flags   |   Type Code   |      Length (1 or 2 octets)   |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |           STAMP Session-Reflector Entry (8 or 20 octets)      |
  .                                                               .
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      ]]></artwork>
    </figure>

    <t>
    Attr Flags: 1 octet.  The flags from the BGP Path Attribute header; these
    are separate from the Flags field in a STAMP Session-Reflector Entry.  The Optional bit
    (0x80) and Transitive bit (0x40) MUST be set.  The Partial bit (0x20) MUST
    be clear when the attribute is originated; a BGP speaker that does not
    recognize the attribute MUST propagate it and set Partial as specified in
    <xref target="RFC4271"/>.  The Extended Length bit (0x10) MUST be set when
    the attribute value is longer than 255 octets and MUST be clear otherwise.
    The four low-order reserved bits MUST be zero when sent.
    </t>
    <t>
    Type Code: 1 octet.  BGP Path Attribute type code TBA5.
    </t>
    <t>
    Length: 1 or 2 octets, following the Extended Length flag in the Path
    Attribute Flags field, as specified in <xref target="RFC4271"/>.  It gives
    the number of octets in the complete attribute value.  It is 8 for an
    IPv4 entry and 20 for an IPv6 entry.
    </t>
    <t>
    The attribute value MUST contain exactly one complete entry and MUST NOT
    contain trailing octets.  Therefore, this extension advertises one
    reflector for each route to which the attribute applies.  An UPDATE MUST
    NOT contain more than one instance of this path attribute.  An originator
    MUST NOT use duplicate attributes as a repetition mechanism.  This
    ordinary attribute is not repeatable like
    MP_REACH_NLRI or MP_UNREACH_NLRI.  If a receiver encounters duplicate
    instances, it MUST retain the first and discard subsequent instances, as
    specified in <xref target="RFC7606"/>.  The instances are not
    concatenated.
    </t>

    <t>
    The attribute is optional and transitive, and is propagated with its route
    over iBGP and eBGP subject to normal BGP route propagation and export
    policy.  A BGP speaker that recognizes the attribute and propagates the
    route MUST preserve the attribute value.  A BGP speaker that does not
    recognize it MUST propagate the optional transitive attribute according
    to <xref target="RFC4271"/>.  A speaker originating or re-originating a
    route MUST include only an entry explicitly configured for that route and
    MUST set the Partial bit to zero.
    </t>
    <t>
    A speaker forming an aggregate route MUST NOT select an entry from one of
    the component routes.  It MAY attach an entry to the aggregate only when
    that entry is explicitly configured as valid for the aggregate route;
    otherwise, the attribute MUST be omitted.  The V flag in the entry
    identifies the reflector address family and is independent of the route's
    AFI.  Thus an IPv4 route may carry an IPv4 or IPv6 reflector address, and
    an IPv6 route may carry an IPv4 or IPv6 reflector address.
    </t>
    <t>
    This attribute MUST NOT affect BGP path selection or route installation.
    A STAMP application using the information SHOULD use the entry from the
    route selected for the destination prefix and MUST apply local policy,
    including any required trust and reachability checks.  The transitive
    attribute is information supplied by the route originator; its presence
    does not authenticate the originator or establish that a reflector is
    reachable or authorized for use.
    </t>
    <t>
    A path-attribute value containing an entry that is malformed according to
    <xref target="stamp-reflector-entry-format"/>, including a truncated
    entry or an entry length inconsistent with the V flag, is malformed.  If
    the BGP UPDATE remains parseable, the receiver
    MUST discard the entire BGP STAMP Session-Reflector path attribute and continue
    processing the UPDATE (Attribute Discard), as specified in
    <xref target="RFC7606"/>.
    The receiver SHOULD log the error.  This handling is safe because the
    attribute does not affect route selection or installation.  Errors in the
    enclosing BGP UPDATE or path-attribute framing MUST be handled as specified
    in <xref target="RFC7606"/>.  Incorrect Optional or Transitive flag bits
    MUST also be handled as specified in <xref target="RFC7606"/>.
    </t>
    <t>
    IANA is requested to allocate Path Attribute type code TBA5 for the BGP
    STAMP Session-Reflector path attribute.
    </t>

    </section>

    <section title="Operational Considerations" anchor="sect-9">
    <t>
    The operational considerations specified in <xref target="RFC8762" format="default"/> 
    apply to the extensions defined in this document.
    As the advertised STAMP
    Session-Reflector information is static in nature, no adverse flooding
    churn is introduced by the extensions defined in this document.
    </t>

    </section>

    <section title="Security Considerations" anchor="sect-10">
    <t>
    The security considerations specified in <xref target="RFC8762" format="default"/>, 
    <xref target="RFC7684" format="default"/>, and <xref target="RFC8362" format="default"/> 
    apply to the extensions defined in this document.
    </t>

    </section>

    <section title="IANA Considerations" anchor="sect-11">

    <section title="IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability" anchor="sect-11.1">
    <t>
    IANA maintains the registry for the "IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability".
    IANA is requested to allocate the following sub-TLV.
    </t>

    <table anchor="iana-tlv-type-tbl-is-is" align="center">
       <name>IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability</name>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="center">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">TBA1 </td>
            <td align="center">STAMP Session-Reflector</td>
            <td align="left">This document</td>
          </tr>
        </tbody>
    </table>
    </section>

    <section title="OSPFv2 Extended Prefix TLV Sub-TLVs" anchor="sect-11.2">
    <t>
    IANA maintains the registry for the "OSPFv2 Extended Prefix TLV Sub-TLVs".
    IANA is requested to allocate the following sub-TLV.
    </t>

    <table anchor="iana-tlv-type-tbl-ospfv2" align="center">
       <name>OSPFv2 Extended Prefix TLV Sub-TLVs</name>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="center">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">TBA2 </td>
            <td align="center">STAMP Session-Reflector</td>
            <td align="left">This document</td>
          </tr>
        </tbody>
    </table>
    </section>

    <section title="OSPFv3 Extended-LSA Sub-TLVs" anchor="sect-11.3">
    <t>
    IANA maintains the registry for the "OSPFv3 Extended-LSA Sub-TLVs".
    IANA is requested to allocate the following sub-TLV.
    </t>

    <table anchor="iana-tlv-type-tbl-ospfv3" align="center">
       <name>OSPFv3 Extended-LSA Sub-TLVs</name>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="center">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">TBA3 </td>
            <td align="center">STAMP Session-Reflector</td>
            <td align="left">This document</td>
          </tr>
        </tbody>
    </table>
    </section>

    <section title="BGP-LS NLRI and Attribute TLVs" anchor="sect-11.4">
    <t>
    IANA maintains the registry for the "BGP-LS NLRI and Attribute TLVs".
    IANA is requested to allocate the following TLV.
    </t>

       <table anchor="iana-tlv-type-tblbgpls" align="center">
       <name>BGP-LS NLRI and Attribute TLVs</name>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="center">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">TBA4 </td>
            <td align="center">STAMP Session-Reflector</td>
            <td align="left">This document</td>
          </tr>
        </tbody>
    </table>
    </section>

   <section title="BGP Path Attributes" anchor="sect-11.5">

    <t>
    IANA maintains the registry for the "BGP Path Attributes".
    IANA is requested to allocate a BGP Path Attribute type code for the STAMP
    Reflector attribute.
    </t>

       <table anchor="iana-tlv-type-tblbgp" align="center">
       <name>BGP Path Attributes</name>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="center">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">TBA5 </td>
            <td align="center">STAMP Session-Reflector</td>
            <td align="left">This document</td>
          </tr>
        </tbody>
    </table>

    </section>

    <section title="STAMP Session-Reflector Entry Flags" anchor="sect-11.6">

    <t>
    IANA is requested to create a registry called "STAMP Session-Reflector Entry Flags"
    to track bit assignments for the 8-bit Flags field in the STAMP Reflector
    Entry.  Bits are numbered from zero at the most significant bit.  The
    registration policy for unassigned bits is Standards Action.
    </t>

    <table anchor="iana-stamp-reflector-flags" align="center">
      <name>STAMP Session-Reflector Entry Flags</name>
      <thead>
        <tr>
          <th align="left">Bit</th>
          <th align="left">Mask</th>
          <th align="left">Description</th>
          <th align="left">Reference</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td align="left">0</td>
          <td align="left">0x80</td>
          <td align="left">V: 0 for IPv4, 1 for IPv6</td>
          <td align="left">This document</td>
        </tr>
        <tr>
          <td align="left">1-7</td>
          <td align="left">0x7F</td>
          <td align="left">Unassigned</td>
          <td align="left">This document</td>
        </tr>
      </tbody>
    </table>

    </section>

    </section>

    </middle>

    <back>
    <references title="Normative References">
    &RFC2119;
    &RFC4271;
    &RFC7606;
    &RFC5305;
    &RFC8174;
    &RFC7684;
    &RFC8362;
    &RFC8762;
    &RFC9552;

    </references>
    <references title="Informative References">

    </references>
    <section title="Acknowledgments" numbered="no" anchor="acknowledgments">
    <t>
    Thank you Aditya Dogra for reviewing this document and providing many useful comments.
    </t>

    </section>

    </back>

    </rfc>
