Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP November 2026
Gandhi Expires 19 May 2027 [Page]
Workgroup:
LSR Working Group
Internet-Draft:
draft-gandhi-lsr-stamp-01
Published:
Intended Status:
Standards Track
Expires:
Author:
R. Gandhi, Ed.
Cisco Systems, Inc.

IS-IS, OSPF, BGP-LS, and BGP Extensions for Advertising STAMP Session-Reflectors

Abstract

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.

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.

▲

Table of Contents

1. Introduction

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 [RFC8762]. STAMP test packets are sent between a STAMP Session-Sender and a STAMP Session-Reflector to measure delay and packet loss along the path.

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.

2. Conventions Used in This Document

2.1. Requirements Language

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.

2.2. Terminology

This document uses terms defined in [RFC8762], specifically Session-Sender and Session-Reflector.

2.3. Abbreviations

Table 1: Abbreviations
Abbreviation Meaning Reference
STAMP Simple Two-Way Active Measurement Protocol [RFC8762]
TLV Type-Length-Value [RFC5305]

3. Overview

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.

The following STAMP Session-Reflector information is advertised to enable discovery:

* STAMP Session-Reflector IP address

* STAMP Session-Reflector UDP port number

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.

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.

4. Common STAMP Session-Reflector Entry

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.

  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)     |
  .                                                               .
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: STAMP Session-Reflector Entry

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.

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.

Reserved: 1 octet. Originators MUST set this field to zero; receivers MUST ignore it.

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 [RFC8762].

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.

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.

5. IS-IS Extensions

The IS-IS sub-TLV contains one STAMP Session-Reflector Entry as defined in Figure 1. Its format is shown in Figure 2.

  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)      |
  .                                                               .
  +---------------------------------------------------------------+
Figure 2: IS-IS STAMP Session-Reflector sub-TLV

Type: 1 octet. Sub-TLV type for STAMP Session-Reflector (TBA1).

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.

In this document, the IS-IS STAMP Session-Reflector extension is carried in IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability [RFC5305]. New STAMP Session-Reflector sub-TLV type is allocated for IS-IS (value TBA1 to be assigned by IANA).

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.

6. OSPFv2 Extensions

The OSPFv2 sub-TLV contains one STAMP Session-Reflector Entry as defined in Figure 1. Its format is shown in Figure 3.

  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)            |
  |                                                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: OSPFv2 STAMP Session-Reflector sub-TLV

Type: 2 octets. Sub-TLV type for STAMP Session-Reflector (TBA2).

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.

In this document, the OSPFv2 STAMP Session-Reflector extension is carried in OSPFv2 Extended Prefix TLV (Type 1) [RFC7684]. 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.

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.

7. OSPFv3 Extensions

The OSPFv3 sub-TLV contains one STAMP Session-Reflector Entry as defined in Figure 1. Its format is shown in Figure 4.

  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)      |
  .                                                               .
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: OSPFv3 STAMP Session-Reflector sub-TLV

Type: 2 octets. Sub-TLV type for STAMP Session-Reflector (TBA3).

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.

In this document, the OSPFv3 STAMP Session-Reflector extension is carried in prefix-related TLVs within OSPFv3 Extended-LSAs [RFC8362]. IANA is requested to allocate sub-TLV type TBA3 for the STAMP Session-Reflector sub-TLV.

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.

8. BGP-LS Extensions

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 Section 5.1 of [RFC9552]. The TLV contains one STAMP Session-Reflector Entry as defined in Figure 1. Its format is shown in Figure 5.

  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)      |
  .                                                               .
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: BGP-LS STAMP Session-Reflector TLV

Type: 2 octets. Prefix Attribute TLV type for STAMP Session-Reflector (TBA4).

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.

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 Section 5.1 of [RFC9552]. 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.

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.

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 Section 8.2.2 of [RFC9552]. 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.

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 Section 5.1 of [RFC9552].

9. BGP Extensions

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 Figure 1. The path-attribute header and value are shown in Figure 6. 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.

  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)      |
  .                                                               .
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: BGP STAMP Session-Reflector Path Attribute

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 [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.

Type Code: 1 octet. BGP Path Attribute type code TBA5.

Length: 1 or 2 octets, following the Extended Length flag in the Path Attribute Flags field, as specified in [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.

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 [RFC7606]. The instances are not concatenated.

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 [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.

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.

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.

A path-attribute value containing an entry that is malformed according to Section 4, 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 [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 [RFC7606]. Incorrect Optional or Transitive flag bits MUST also be handled as specified in [RFC7606].

IANA is requested to allocate Path Attribute type code TBA5 for the BGP STAMP Session-Reflector path attribute.

10. Operational Considerations

The operational considerations specified in [RFC8762] 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.

11. Security Considerations

The security considerations specified in [RFC8762], [RFC7684], and [RFC8362] apply to the extensions defined in this document.

12. IANA Considerations

12.1. IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability

IANA maintains the registry for the "IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability". IANA is requested to allocate the following sub-TLV.

Table 2: IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability
Value Description Reference
TBA1 STAMP Session-Reflector This document

12.2. OSPFv2 Extended Prefix TLV Sub-TLVs

IANA maintains the registry for the "OSPFv2 Extended Prefix TLV Sub-TLVs". IANA is requested to allocate the following sub-TLV.

Table 3: OSPFv2 Extended Prefix TLV Sub-TLVs
Value Description Reference
TBA2 STAMP Session-Reflector This document

12.3. OSPFv3 Extended-LSA Sub-TLVs

IANA maintains the registry for the "OSPFv3 Extended-LSA Sub-TLVs". IANA is requested to allocate the following sub-TLV.

Table 4: OSPFv3 Extended-LSA Sub-TLVs
Value Description Reference
TBA3 STAMP Session-Reflector This document

12.4. BGP-LS NLRI and Attribute TLVs

IANA maintains the registry for the "BGP-LS NLRI and Attribute TLVs". IANA is requested to allocate the following TLV.

Table 5: BGP-LS NLRI and Attribute TLVs
Value Description Reference
TBA4 STAMP Session-Reflector This document

12.5. BGP Path Attributes

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.

Table 6: BGP Path Attributes
Value Description Reference
TBA5 STAMP Session-Reflector This document

12.6. STAMP Session-Reflector Entry Flags

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.

Table 7: STAMP Session-Reflector Entry Flags
Bit Mask Description Reference
0 0x80 V: 0 for IPv4, 1 for IPv6 This document
1-7 0x7F Unassigned This document

13. References

13.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC4271]
Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, , <https://www.rfc-editor.org/info/rfc4271>.
[RFC7606]
Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. Patel, "Revised Error Handling for BGP UPDATE Messages", RFC 7606, DOI 10.17487/RFC7606, , <https://www.rfc-editor.org/info/rfc7606>.
[RFC5305]
Li, T. and H. Smit, "IS-IS Extensions for Traffic Engineering", RFC 5305, DOI 10.17487/RFC5305, , <https://www.rfc-editor.org/info/rfc5305>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
[RFC7684]
Psenak, P., Gredler, H., Shakir, R., Henderickx, W., Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute Advertisement", RFC 7684, DOI 10.17487/RFC7684, , <https://www.rfc-editor.org/info/rfc7684>.
[RFC8362]
Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and F. Baker, "OSPFv3 Link State Advertisement (LSA) Extensibility", RFC 8362, DOI 10.17487/RFC8362, , <https://www.rfc-editor.org/info/rfc8362>.
[RFC8762]
Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple Two-Way Active Measurement Protocol", RFC 8762, DOI 10.17487/RFC8762, , <https://www.rfc-editor.org/info/rfc8762>.
[RFC9552]
Talaulikar, K., Ed., "Distribution of Link-State and Traffic Engineering Information Using BGP", RFC 9552, DOI 10.17487/RFC9552, , <https://www.rfc-editor.org/info/rfc9552>.

13.2. Informative References

Acknowledgments

Thank you Aditya Dogra for reviewing this document and providing many useful comments.

Author's Address

Rakesh Gandhi (editor)
Cisco Systems, Inc.
Canada