References from draft-atwood-pim-reserve-exp
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 | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
| BCP 82 |
Assigning Experimental and Testing Numbers Considered Useful
References Referenced by |
Best Current Practice | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3692 |
Assigning Experimental and Testing Numbers Considered Useful
References Referenced by |
Best Current Practice | informatively references | |
| RFC 4601 |
Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
| RFC 5384 |
The Protocol Independent Multicast (PIM) Join Attribute Format
References Referenced by |
Proposed Standard | normatively references |