References from draft-bhatia-karp-pim-gap-analysis

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
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2328 OSPF Version 2
Refs Ref'd by
Internet Standard informatively references
RFC 4301 Security Architecture for the Internet Protocol
Refs Ref'd by
Proposed Standard informatively references
RFC 4302 IP Authentication Header
Refs Ref'd by
Proposed Standard informatively references
RFC 4303 IP Encapsulating Security Payload (ESP)
Refs Ref'd by
Proposed Standard informatively references
RFC 4306 Internet Key Exchange (IKEv2) Protocol
Refs Ref'd by
Proposed Standard informatively references
RFC 4601 Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)
Refs Ref'd by
Proposed Standard normatively references
RFC 4610 Anycast-RP Using Protocol Independent Multicast (PIM)
Refs Ref'd by
Proposed Standard informatively references
RFC 5796 Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local Messages
Refs Ref'd by
Proposed Standard normatively references
RFC 6518 Keying and Authentication for Routing Protocols (KARP) Design Guidelines
Refs Ref'd by
Informational informatively references
RFC 6862 Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements
Refs Ref'd by
Informational informatively references