References from RFC 5611
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 116 |
References Referenced by |
informatively references | ||
BCP 14 |
References Referenced by |
normatively references | ||
BCP 26 |
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3931 |
Layer Two Tunneling Protocol - Version 3 (L2TPv3)
References Referenced by |
Proposed Standard | normatively references | |
RFC 4446 |
IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)
References Referenced by |
Best Current Practice | informatively references | |
RFC 4553 |
Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 5086 |
Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN)
References Referenced by |
Informational | normatively references | Downref |
RFC 5087 |
Time Division Multiplexing over IP (TDMoIP)
References Referenced by |
Informational | informatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
RFC 5287 |
Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS Networks
References Referenced by |
Proposed Standard | informatively references | |
STD 1 |
References Referenced by |
Possible Reference |