References from draft-chen-idr-bier-te-path
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 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| draft-ietf-bier-te-arch |
Tree Engineering for Bit Index Explicit Replication (BIER-TE)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
| RFC 5575 |
Dissemination of Flow Specification Rules
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6514 |
BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8279 |
Multicast Using Bit Index Explicit Replication (BIER)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8296 |
Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9012 |
The BGP Tunnel Encapsulation Attribute
References Referenced by |
Proposed Standard | normatively references |