When this was presented at IETF 126, Rakesh expressed two requirements not met by the existing version.
1. Support for advertisement of Active Measurement Protocol (AMP) parameters (e.g., TWAP UDP port). 2. Support for discovery of neighbors across IGP domains. In order to satisfy the first requirement, the Active Measurement Group (AMP) concept was introduced. The corresponding Group ID is now 16 bits. Each AMG supported by an IGP router is identified by a Group ID. Each AMG has an associated IP endpoint, AMP, and IP address family. IGP routers will discover measurement partners in common AMGs identified by Group ID and attempt to establish AMP sessions in the AMG. Additionally, unique non-default parameters may be associated with an AMP. For example, the UDP ports supported by STAMP may be associated with an AMG. AMGs and their Group IDs are configured within a single administrative domain. This is normally a single IGP domain unless inter-domain discovery is required (refer to Section 6). Each AMG will have an associated AMP and optionally non-default parameters associated with the AMG. The AMP and non-default parameters are not advertised in the IGPs as the protocol extensions specified herein are solely to discover the IP endpoints participating in the AMG. Assuring consistent configuration of the AMP and associated non- default AMP parameters is beyond the scope of this specification. Distinct AMGs are required for distinct AMPs and for distinct IP address families. It is understood that unique AMGs will also be required for unique permutations of asymmetric non-default parameters (e.g., different UDP ports for STAMP endpoints). However, this is not seen as the predominant use case. If the second requirement, discovery across IGP domains, is really a requirement. It is expected that IGP domains will still be under a single administrative domain and discovery can be accomplished using BGP-LS with a common AMG configuration. Thanks, Acee > On Sep 4, 2026, at 2:40 PM, [email protected] wrote: > > A new version of Internet-Draft draft-admnr-lsr-igp-measurement-group-03.txt > has been successfully submitted by Acee Lindem and posted to the > IETF repository. > > Name: draft-admnr-lsr-igp-measurement-group > Revision: 03 > Title: Advertising IGP Active Measurement Groups in Router Capabilities > Date: 2026-09-04 > Group: Individual Submission > Pages: 13 > URL: > https://www.ietf.org/archive/id/draft-admnr-lsr-igp-measurement-group-03.txt > Status: > https://datatracker.ietf.org/doc/draft-admnr-lsr-igp-measurement-group/ > HTML: > https://www.ietf.org/archive/id/draft-admnr-lsr-igp-measurement-group-03.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-admnr-lsr-igp-measurement-group > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-admnr-lsr-igp-measurement-group-03 > > Abstract: > > This document defines an IS-IS capability sub-TLV for advertising > measurement group membership for Active Measurement Protocols (AMPs) > such as TWAMP and STAMP. The mechanism allows IGP routers to > discover other routers participating in different measurement groups, > enabling automatic discovery of measurement endpoints throughout an > IS-IS routing domain. The solution uses a Group ID to identify > measurement group membership, where the same interface address (IPv4 > or IPv6) may be used for multiple measurement groups. > > > > The IETF Secretariat > >
_______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
