References from draft-brockners-ippm-ioam-geneve
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 165 |
References Referenced by |
normatively 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-nvo3-geneve |
Geneve: Generic Network Virtualization Encapsulation
References Referenced by |
Proposed Standard | normatively references | |
draft-weis-ippm-ioam-eth |
EtherType Protocol Identification of In-situ OAM Data
References Referenced by |
normatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2784 |
Generic Routing Encapsulation (GRE)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3232 |
Assigned Numbers: RFC 1700 is Replaced by an On-line Database
References Referenced by |
Informational | normatively references | |
RFC 7605 |
Recommendations on Using Assigned Transport Port Numbers
References Referenced by |
Best Current Practice | normatively references |