I-D Action: draft-dikshit-nmop-telemetry-identifier-scoping-00.txt
| Newsgroups | gmane.ietf.announce |
|---|---|
| Message-ID | <178777125994.745132.10880602798940338931@dt-datatracker-786f84c586-vck88> |
Internet-Draft draft-dikshit-nmop-telemetry-identifier-scoping-00.txt is now available. Title: Scoping and Comparability Requirements for Exported Network Telemetry Identifiers Author: Saumya Dikshit Name: draft-dikshit-nmop-telemetry-identifier-scoping-00.txt Pages: 2 Dates: 2026-08-26 Abstract: Several documents currently in progress across multiple IETF working groups define identifiers that are exported from a network element and consumed by a remote collector, controller, or receiver: a flow identifier, a path segment identifier, a per-peer or per-Route-Distinguisher counter, and a period or sequence number are examples already found in active work. In each case examined in this document, the identifier is defined without a stated scope of uniqueness, so the receiver cannot determine, from the exported value alone, whether two records observed at different times or from different sources describe the same object. This document catalogs six such instances found independently across five working groups, defines a short vocabulary for stating an identifier's scope of uniqueness, and sets out requirements for documents that define exported telemetry identifiers going forward. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-dikshit-nmop-telemetry-identifier-scoping/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-dikshit-nmop-telemetry-identifier-scoping-00 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ I-D-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]