References from rfc5601

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 116	IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3) Refs Ref'd by	Best Current Practice	normatively references
BCP 14	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
BCP 26	Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by	Best Current Practice	informatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	Possible Reference
RFC 2558	Definitions of Managed Objects for the SONET/SDH Interface Type Refs Ref'd by	Proposed Standard	Possible Reference
RFC 2578	Structure of Management Information Version 2 (SMIv2) Refs Ref'd by	Internet Standard	normatively references
RFC 2579	Textual Conventions for SMIv2 Refs Ref'd by	Internet Standard	normatively references
RFC 2580	Conformance Statements for SMIv2 Refs Ref'd by	Internet Standard	normatively references
RFC 2863	The Interfaces Group MIB Refs Ref'd by	Draft Standard	normatively references
RFC 3410	Introduction and Applicability Statements for Internet-Standard Management Framework Refs Ref'd by	Informational	informatively references
RFC 3411	An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks Refs Ref'd by	Internet Standard	normatively references
RFC 3413	Simple Network Management Protocol (SNMP) Applications Refs Ref'd by	Internet Standard	normatively references
RFC 3593	Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals Refs Ref'd by	Draft Standard	normatively references
RFC 3705	High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals Refs Ref'd by	Proposed Standard	normatively references
RFC 3916	Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3) Refs Ref'd by	Informational	informatively references
RFC 3931	Layer Two Tunneling Protocol - Version 3 (L2TPv3) Refs Ref'd by	Proposed Standard	normatively references
RFC 3985	Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture Refs Ref'd by	Informational	informatively references
RFC 4001	Textual Conventions for Internet Network Addresses Refs Ref'd by	Proposed Standard	normatively references
RFC 4446	IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3) Refs Ref'd by	Best Current Practice	normatively references
RFC 4447	Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP) Refs Ref'd by	Proposed Standard	normatively references
RFC 4623	Pseudowire Emulation Edge-to-Edge (PWE3) Fragmentation and Reassembly Refs Ref'd by	Proposed Standard	normatively references
RFC 4720	Pseudowire Emulation Edge-to-Edge (PWE3) Frame Check Sequence Retention Refs Ref'd by	Proposed Standard	normatively references
RFC 4863	Wildcard Pseudowire Type Refs Ref'd by	Proposed Standard	normatively references
RFC 5226	Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by	Best Current Practice	informatively references
RFC 5542	Definitions of Textual Conventions for Pseudowire (PW) Management Refs Ref'd by	Proposed Standard	normatively references
RFC 5602	Pseudowire (PW) over MPLS PSN Management Information Base (MIB) Refs Ref'd by	Proposed Standard	informatively references
STD 1	Internet Official Protocol Standards Refs Ref'd by	Historic	Possible Reference	Possible Downref
STD 58	Conformance Statements for SMIv2 Refs Ref'd by	Internet Standard	normatively references
STD 62	Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) Refs Ref'd by	Internet Standard	normatively references