LSR Working Group R. Gandhi, Ed. Internet-Draft Cisco Systems, Inc. Intended status: Standards Track 18 July 2026 Expires: 19 January 2027 IS-IS, OSPF, BGP-LS, and BGP Extensions for Signaling STAMP Parameters draft-gandhi-lsr-stamp-00 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 describes the extensions to IS-IS, OSPF, BGP-LS, and BGP protocols for signaling STAMP reflector parameters in a network. The STAMP reflector parameters can be used by the 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 January 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 Gandhi Expires 19 January 2027 [Page 1] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 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 . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. IS-IS Extensions . . . . . . . . . . . . . . . . . . . . . . 4 4.1. IS-IS STAMP Reflector Sub-TLV . . . . . . . . . . . . . . 4 4.2. IS-IS Prefix Advertisement Extension . . . . . . . . . . 5 5. OSPFv2 Extensions . . . . . . . . . . . . . . . . . . . . . . 5 5.1. OSPFv2 STAMP Reflector Sub-TLV . . . . . . . . . . . . . 5 5.2. OSPFv2 Prefix Advertisement Extension . . . . . . . . . . 6 6. OSPFv3 Extensions . . . . . . . . . . . . . . . . . . . . . . 6 6.1. OSPFv3 STAMP Reflector Sub-TLV . . . . . . . . . . . . . 7 6.2. OSPFv3 Prefix Advertisement Extension . . . . . . . . . . 8 7. BGP-LS Extensions . . . . . . . . . . . . . . . . . . . . . . 8 7.1. BGP-LS STAMP Reflector TLV . . . . . . . . . . . . . . . 8 7.2. BGP-LS NLRI and Attribute Extension . . . . . . . . . . . 9 8. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . 9 8.1. BGP STAMP Reflector TLV . . . . . . . . . . . . . . . . . 9 8.2. BGP Path Attributes Extension . . . . . . . . . . . . . . 10 9. Operational Considerations . . . . . . . . . . . . . . . . . 10 10. Security Considerations . . . . . . . . . . . . . . . . . . . 10 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 11.1. IS-IS Prefix Advertisement sub-TLV . . . . . . . . . . . 10 11.2. OSPFv2 Prefix Advertisement sub-TLV . . . . . . . . . . 11 11.3. OSPFv3 Prefix Advertisement sub-TLV . . . . . . . . . . 11 11.4. BGP-LS NLRI and Attribute TLV . . . . . . . . . . . . . 11 11.5. BGP Path Attribute TLV . . . . . . . . . . . . . . . . . 11 11.6. STAMP Reflector Flags Registry . . . . . . . . . . . . . 12 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 12.1. Normative References . . . . . . . . . . . . . . . . . . 12 12.2. Informative References . . . . . . . . . . . . . . . . . 13 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13 Gandhi Expires 19 January 2027 [Page 2] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 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. Due to the lack of control channel signaling, the Session-Sender cannot learn the STAMP parameters from the Session-Reflector. At the same time, introducing signaling per STAMP session results in additional scale challenges in the network. This document describes the extensions to IS-IS, OSPF, BGP-LS, and BGP protocols for signaling STAMP reflector parameters in a network. The STAMP reflector parameters can be used by the STAMP senders to set up appropriate performance measurement sessions for delay and packet loss metrics. 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. Abbreviations STAMP: Simple Two-Way Active Measurement Protocol TLV: Type-Length-Value 3. Overview In this document, IS-IS, OSPF, BGP-LS, and BGP protocol extensions are defined to signal the STAMP reflector parameters in a network. The signaled parameters are used by the STAMP senders to set up appropriate performance measurement sessions for delay and packet loss metrics. The following STAMP reflector parameters are signaled: * STAMP reflector IP address Gandhi Expires 19 January 2027 [Page 3] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 * STAMP reflector UDP port (default 862) * STAMP reflector Clock Sync Status * STAMP reflector Minimum Receive Interval: Packets arriving faster than the minimum interval will likely be dropped by the reflector due to an inability to support the packet rate. Even though the STAMP reflector is a property of the node and can be signaled as part of the node capability, in some cases it is advantageous to associate and advertise them with a 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 LSR. 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 parameters signaling for that prefix if it exists. The exact mechanism used to exchange STAMP parameters between protocol instances running on an Autonomous System Border Router is outside of the scope of this document. 4. IS-IS Extensions 4.1. IS-IS STAMP Reflector Sub-TLV The format of the sub-TLV for advertising STAMP reflector parameters is shown in Figure 1. 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 | Flags: CI | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . | IPv4 or IPv6 Reflector Address (4 or 16 octets) | . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reflector Min Receive Interval| Reflector UDP Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: IS-IS STAMP Reflector sub-TLV Type: 1-octet. Sub-TLV type for STAMP reflector. Gandhi Expires 19 January 2027 [Page 4] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 Length: 1-octet. The length of the value field in octets excluding the header. Flags: 2-octets. A bit field indicating various flags related to STAMP reflector. I: Set to 1 when the IP address is IPv6, otherwise the IP address is IPv4. C: Set to 1 to indicate the Clock status as In-Sync, otherwise the Clock status is Out-of-Sync. IPv4 or IPv6 reflector address: STAMP reflector target IP address. Reflector UDP Port: STAMP reflector UDP Port associated with the reflector address. Reflector Minimum Receive Interval: STAMP reflector minimum receive interval in milli-seconds. 4.2. IS-IS Prefix Advertisement Extension In this document, the IS-IS STAMP reflector extension is carried in IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability [RFC5305]. New STAMP 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 reflector addresses and the associated parameters from a node. 5. OSPFv2 Extensions 5.1. OSPFv2 STAMP Reflector Sub-TLV The format of the sub-TLV for advertising STAMP reflector parameters is shown in Figure 2. Gandhi Expires 19 January 2027 [Page 5] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 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 2 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags: C | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | IPv4 Reflector Address (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reflector Min Receive Interval| Reflector UDP Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2: OSPFv2 STAMP Reflector sub-TLV Type: 2-octets. Sub-TLV type for STAMP reflector. Length: 2-octets. The length of the value field in octets excluding the header. Flags: 2-octets. A bit field indicating various flags related to STAMP reflector. C: Set to 1 to indicate the Clock status as In-Sync, otherwise the Clock status is Out-of-Sync. IPv4 reflector address: STAMP reflector target IP address. Reflector UDP Port: STAMP reflector UDP Port associated with the reflector address. Reflector Minimum Receive Interval: STAMP reflector minimum receive interval in milli-seconds. 5.2. OSPFv2 Prefix Advertisement Extension In this document, the OSPFv2 STAMP 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). New STAMP reflector sub-TLV type is allocated for OSPFv2 (value TBA2 to be assigned by IANA). Multiple instances of this sub-TLV MAY be included to advertise multiple reflector addresses and the associated parameters from a node. 6. OSPFv3 Extensions Gandhi Expires 19 January 2027 [Page 6] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 6.1. OSPFv3 STAMP Reflector Sub-TLV The format of the sub-TLV for advertising STAMP reflector parameters 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags: CI | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . | IPv4 or IPv6 Reflector Address (4 or 16 octets) | . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reflector Min Receive Interval| Reflector UDP Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3: OSPFv3 STAMP Reflector sub-TLV Type: 2-octets. Sub-TLV type for STAMP reflector. Length: 2-octets. The length of the value field in octets excluding the header. Flags: 2-octets. A bit field indicating various flags related to STAMP reflector. C: Set to 1 to indicate the Clock status as In-Sync, otherwise the Clock status is Out-of-Sync. I: Set to 1 when the IP address is IPv6, otherwise the IP address is IPv4. IPv4 or IPv6 reflector address: STAMP reflector target IP address. Reflector UDP Port: STAMP reflector UDP Port associated with the reflector address. Reflector Minimum Receive Interval: STAMP reflector minimum receive interval in milli-seconds. Gandhi Expires 19 January 2027 [Page 7] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 6.2. OSPFv3 Prefix Advertisement Extension In this document, the OSPFv3 STAMP reflector extension is carried in prefix-related TLVs within OSPFv3 Extended-LSAs [RFC8362]. New STAMP reflector sub-TLV type is allocated for OSPFv3 (value TBA3 to be assigned by IANA). Multiple instances of this sub-TLV MAY be included to advertise multiple reflector addresses and the associated parameters from a node. 7. BGP-LS Extensions 7.1. BGP-LS STAMP Reflector TLV The format of the TLV for advertising STAMP reflector parameters 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags: CI | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . | IPv4 or IPv6 Reflector Address (4 or 16 octets) | . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reflector Min Receive Interval| Reflector UDP Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 4: BGP-LS STAMP Reflector TLV Type: 1-octet. TLV type for STAMP reflector. Length: 1-octet. The length of the value field in octets excluding the header. Flags: 2-octets. A bit field indicating various flags related to STAMP reflector. I: Set to 1 when the IP address is IPv6, otherwise the IP address is IPv4. C: Set to 1 to indicate the Clock status as In-Sync, otherwise the Clock status is Out-of-Sync. Gandhi Expires 19 January 2027 [Page 8] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 IPv4 or IPv6 reflector address: STAMP reflector target IP address. Reflector UDP Port: STAMP reflector UDP Port associated with the reflector address. Reflector Minimum Receive Interval: STAMP reflector minimum receive interval in milli-seconds. 7.2. BGP-LS NLRI and Attribute Extension In this document, the BGP-LS STAMP reflector extension is carried in BGP-LS NLRI and Attribute TLV [RFC9552]. New STAMP reflector TLV type is allocated for BGP-LS (value TBA4 to be assigned by IANA). Multiple instances of this TLV MAY be included to advertise multiple reflector addresses and the associated parameters from a node. 8. BGP Extensions 8.1. BGP STAMP Reflector TLV The format of the TLV for advertising STAMP reflector parameters 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags | Type | Length | CI | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . | IPv4 or IPv6 Reflector Address (4 or 16 octets) | . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reflector Min Receive Interval| Reflector UDP Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 5: BGP STAMP Reflector TLV Type: 1-octet. TLV type for STAMP reflector. Length: 1-octet. The length of the value field in octets excluding the header. Flags: 1-octet. A bit field indicating various flags related to STAMP reflector. I: Set to 1 when the IP address is IPv6, otherwise the IP address is IPv4. Gandhi Expires 19 January 2027 [Page 9] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 C: Set to 1 to indicate the Clock status as In-Sync, otherwise the Clock status is Out-of-Sync. IPv4 or IPv6 reflector address: STAMP reflector target IP address. Reflector UDP Port: STAMP reflector UDP Port associated with the reflector address. Reflector Minimum Receive Interval: STAMP reflector minimum receive interval in milli-seconds. 8.2. BGP Path Attributes Extension In this document, the BGP STAMP reflector extension is carried as a BGP Path Attribute TLV [RFC4271]. New STAMP reflector TLV type is allocated for BGP (value TBA5 to be assigned by IANA). Multiple instances of this TLV MAY be included to advertise multiple reflector addresses and the associated parameters from a node. 9. Operational Considerations The operational considerations specified in [RFC8762] apply to the extensions defined in this document. As STAMP reflector parameters are static in nature, no additional flooding churn is introduced by the extensions defined in this document. 10. Security Considerations The security considerations specified in [RFC8762], [RFC7684], and [RFC8362] apply to the extensions defined in this document. 11. IANA Considerations 11.1. IS-IS Prefix Advertisement sub-TLV IANA maintains the registry for the "IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability". IANA is requested to allocate the following sub-TLV. +=======+=================+===============+ | Value | Description | Reference | +=======+=================+===============+ | TBA1 | STAMP Reflector | This document | +-------+-----------------+---------------+ Table 1: IS-IS sub-TLV Type Gandhi Expires 19 January 2027 [Page 10] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 11.2. OSPFv2 Prefix Advertisement sub-TLV IANA maintains the registry for the "OSPFv2 Extended Prefix TLV Sub- TLVs". IANA is requested to allocate the following sub-TLV. +=======+=================+===============+ | Value | Description | Reference | +=======+=================+===============+ | TBA2 | STAMP Reflector | This document | +-------+-----------------+---------------+ Table 2: OSPFv2 sub-TLV Type 11.3. OSPFv3 Prefix Advertisement sub-TLV IANA maintains the registry for the "OSPFv3 Extended-LSA Sub-TLVs". IANA is requested to allocate the following sub-TLV. +=======+=================+===============+ | Value | Description | Reference | +=======+=================+===============+ | TBA3 | STAMP Reflector | This document | +-------+-----------------+---------------+ Table 3: OSPFv3 sub-TLV Type 11.4. BGP-LS NLRI and Attribute TLV IANA maintains the registry for the "BGP-LS NLRI and Attribute TLVs". IANA is requested to allocate the following TLV. +=======+=================+===============+ | Value | Description | Reference | +=======+=================+===============+ | TBA4 | STAMP Reflector | This document | +-------+-----------------+---------------+ Table 4: BGP-LS NLRI and Attribute TLV Type 11.5. BGP Path Attribute TLV IANA maintains the registry for the "BGP Path Attributes". IANA is requested to allocate the following TLV. Gandhi Expires 19 January 2027 [Page 11] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 +=======+=================+===============+ | Value | Description | Reference | +=======+=================+===============+ | TBA5 | STAMP Reflector | This document | +-------+-----------------+---------------+ Table 5: BGP Path Attribute TLV Type 11.6. STAMP Reflector Flags Registry IANA is requested to create a new registry called "STAMP Reflector Flags" under the "Interior Gateway Protocol (IGP) Parameters" registry group. The registry should track bit assignments for the STAMP Reflector Flags field of the STAMP Reflector sub-TLV. 12. References 12.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006, . [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic Engineering", RFC 5305, DOI 10.17487/RFC5305, October 2008, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [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, November 2015, . [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, April 2018, . Gandhi Expires 19 January 2027 [Page 12] Internet-Draft IS-IS, OSPF, BGP-LS, BGP for STAMP July 2026 [RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple Two-Way Active Measurement Protocol", RFC 8762, DOI 10.17487/RFC8762, March 2020, . [RFC9552] Talaulikar, K., Ed., "Distribution of Link-State and Traffic Engineering Information Using BGP", RFC 9552, DOI 10.17487/RFC9552, December 2023, . 12.2. Informative References Acknowledgments TBA. Author's Address Rakesh Gandhi (editor) Cisco Systems, Inc. Canada Email: rgandhi@cisco.com Gandhi Expires 19 January 2027 [Page 13]