References from rfc8300

This is an experimental product. 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.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
BCP 161 Guidelines for the Use of the "OAM" Acronym in the IETF
Refs Ref'd by
Best Current Practice informatively references
BCP 26 Guidelines for Writing an IANA Considerations Section in RFCs
Refs Ref'd by
Best Current Practice normatively references
BCP 72 Guidelines for Writing RFC Text on Security Considerations
Refs Ref'd by
Best Current Practice informatively references
BCP 82 Assigning Experimental and Testing Numbers Considered Useful
Refs Ref'd by
Best Current Practice informatively references
draft-brockners-proof-of-transit Proof of Transit
Refs Ref'd by
informatively references
draft-guichard-sfc-nsh-dc-allocation Network Service Header (NSH) MD Type 1: Context Header Allocation (Data Center)
Refs Ref'd by
informatively references
draft-ietf-nvo3-vxlan-gpe Generic Protocol Extension for VXLAN
Refs Ref'd by
Informational informatively references
draft-ietf-rtgwg-dt-encap Encapsulation Considerations
Refs Ref'd by
Informational informatively references
draft-ietf-sfc-control-plane Service Function Chaining (SFC) Control Plane Components & Requirements
Refs Ref'd by
Informational informatively references
draft-ietf-sfc-oam-framework Service Function Chaining (SFC) Operation, Administration and Maintenance (OAM) Framework
Refs Ref'd by
informatively references
draft-napper-sfc-nsh-broadband-allocation NSH Context Header Allocation -- Broadband
Refs Ref'd by
informatively references
draft-quinn-sfc-nsh Network Service Header
Refs Ref'd by
Possible Reference Possible Downref
draft-reddy-sfc-nsh-encrypt Authenticated and encrypted NSH service chains
Refs Ref'd by
informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2784 Generic Routing Encapsulation (GRE)
Refs Ref'd by
Proposed Standard informatively references
RFC 3552 Guidelines for Writing RFC Text on Security Considerations
Refs Ref'd by
Best Current Practice informatively references
RFC 3692 Assigning Experimental and Testing Numbers Considered Useful
Refs Ref'd by
Best Current Practice informatively references
RFC 6071 IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
Refs Ref'd by
Informational informatively references
RFC 6291 Guidelines for the Use of the "OAM" Acronym in the IETF
Refs Ref'd by
Best Current Practice informatively references
RFC 7325 MPLS Forwarding Compliance and Performance Requirements
Refs Ref'd by
Informational informatively references
RFC 7498 Problem Statement for Service Function Chaining
Refs Ref'd by
Informational informatively references
RFC 7665 Service Function Chaining (SFC) Architecture
Refs Ref'd by
Informational normatively references Downref
RFC 7676 IPv6 Support for Generic Routing Encapsulation (GRE)
Refs Ref'd by
Proposed Standard informatively references
RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
Refs Ref'd by
Best Current Practice normatively references
RFC 8165 Design Considerations for Metadata Insertion
Refs Ref'd by
Informational informatively references
RFC 8201 Path MTU Discovery for IP version 6
Refs Ref'd by
Internet Standard informatively references
STD 87 Path MTU Discovery for IP version 6
Refs Ref'd by
Internet Standard informatively references