References from draft-ioamteam-ippm-ioam-direct-export
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
BCP 14 |
References Referenced by |
normatively references | ||
BCP 26 |
References Referenced by |
informatively references | ||
draft-ietf-ippm-ioam-data |
Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)
References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-sfc-ioam-nsh |
Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data
References Referenced by |
Proposed Standard | informatively references | |
draft-ioametal-ippm-6man-ioam-ipv6-options |
In-situ OAM IPv6 Options
References Referenced by |
informatively references | ||
draft-mizrahi-ippm-ioam-flags |
In-situ OAM Flags
References Referenced by |
normatively references | ||
draft-song-ippm-postcard-based-telemetry |
On-Path Telemetry using Packet Marking to Trigger Dedicated OAM Packets
References Referenced by |
normatively references | ||
draft-spiegel-ippm-ioam-rawexport |
In-situ OAM raw data export with IPFIX
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 7799 |
Active and Passive Metrics and Methods (with Hybrid Types In-Between)
References Referenced by |
Informational | informatively references | |
RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references |