Skip to content

RFC 9487 - Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)

Field Value
Title Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)
Authors T. Graf, B. Claise, P. Francois
Date November 2023
Status Informational
Link datatracker.ietf.org/doc/rfc9487

Summary

RFC 9487 defines new IPFIX (IP Flow Information Export) Information Elements for exporting SRv6-related data from network nodes to collectors. As SRv6 deployments grow, operators need visibility into how SRv6 traffic is forwarded -- which SIDs are being used, what segment lists packets carry, and how traffic maps to SR Policies. This RFC provides the telemetry building blocks to answer those questions.

The document specifies 11 new IPFIX Information Elements that capture the essential SRv6 forwarding state observed at a metering point. These elements cover the active SID in the IPv6 destination address, the full segment list from the SRH, the Segments Left value, Section Tag, and flags. Together, they enable a collector to reconstruct the SRv6 forwarding path a packet is following.

These IPFIX elements are essential for SRv6 network operations, enabling use cases such as traffic engineering validation (confirming packets follow the intended SR Policy), SLA monitoring (measuring per-path latency and loss), capacity planning (understanding per-SID traffic volumes), and troubleshooting (identifying packets with unexpected segment lists).

Key Sections

Section Topic Description
3 Use Cases Traffic engineering verification, SLA monitoring, troubleshooting
4 New IPFIX Information Elements Definition of 11 SRv6-specific IEs
5 Encoding How SRv6 SIDs and segment lists are encoded in IPFIX records
6 Export Scenarios Where in the network SRv6 IPFIX export is most useful

New IPFIX Information Elements

IE Name IE ID Type Description
srhFlags 502 unsigned8 Flags field from the SRH
srhTag 503 unsigned16 Tag field from the SRH
srhSegmentIPv6 504 ipv6Address An individual SRv6 SID from the segment list
srhActiveSegmentIPv6 505 ipv6Address The currently active SID (from IPv6 DA)
srhSegmentIPv6BasicList 506 basicList Ordered list of all SRv6 SIDs in the SRH
srhSegmentsIPv6Left 507 unsigned8 Segments Left value from the SRH
srhIPv6Section 508 unsigned8 Section of the SRH being reported
srhIPv6ActiveSegmentType 509 unsigned8 Type of the active segment (e.g., transit, endpoint)
srhSegmentIPv6ListSection 510 basicList Section of the segment list for large SRHs
srhSegmentsIPv6SectionLeft 511 unsigned8 Segments Left relative to the reported section
srhIPv6SRHLength 512 unsigned16 Total length of the SRH in bytes

Export Use Cases

Use Case Key IEs Used Benefit
TE Verification srhSegmentIPv6BasicList, srhActiveSegmentIPv6 Confirm packets follow the programmed SR Policy path
SLA Monitoring srhActiveSegmentIPv6 + timestamps Measure per-path latency and jitter
Capacity Planning srhSegmentIPv6 + byte/packet counters Understand traffic volumes per SID and segment list
Troubleshooting srhFlags, srhSegmentsIPv6Left, full segment list Identify unexpected forwarding behavior or misrouted packets
Accounting srhActiveSegmentIPv6 + flow counters Per-service or per-tenant traffic accounting

IPFIX Export Points in an SRv6 Network

Export Point What is Visible Typical Use
Headend (ingress) Full SRH with complete segment list Verify SR Policy is applied correctly
Transit node IPv6 DA (active SID); SRH if configured to inspect Monitor per-SID traffic load
Endpoint (egress) Final SID processing, decapsulated inner packet End-to-end path validation

Common Pitfalls

  • Not all hardware supports deep SRH inspection for IPFIX export. Transit routers often only see the IPv6 destination address (active SID) and cannot export the full segment list without SRH parsing support.
  • The srhSegmentIPv6BasicList IE uses the IPFIX basicList structured data type (RFC 6313). Collectors must support structured data to parse this field correctly.
  • Large segment lists may exceed IPFIX template or record size limits. The srhSegmentIPv6ListSection and srhIPv6Section IEs provide a mechanism for sectioned export, but collector support varies.
  • SRv6 compressed SIDs (uSID, RFC 9800) appear as standard 128-bit IPv6 addresses in IPFIX. The collector needs additional context (the GIB prefix and C-SID length) to decompose containers into individual micro-SIDs.
  • IPFIX sampling configuration significantly affects telemetry accuracy for SRv6. Low sampling rates may miss short-lived or low-volume SRv6 flows entirely.
  • RFC 8754 - IPv6 Segment Routing Header (SRH)
  • RFC 8986 - SRv6 Network Programming
  • RFC 9259 - Operations, Administration, and Maintenance in SRv6

References

  1. RFC 9487 - Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)
  2. RFC 7011 - Specification of the IP Flow Information Export (IPFIX) Protocol
  3. RFC 6313 - Export of Structured Data in IPFIX
  4. RFC 8754 - IPv6 Segment Routing Header (SRH)