Skip to main content

References to draft-ietf-hubmib-etherif-mib-v3

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
RFC 3621
As rfc3635
Power Ethernet MIB
References Referenced by
Proposed Standard normatively references
RFC 3636
As rfc3635
Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
References Referenced by
Proposed Standard normatively references
RFC 3637
As rfc3635
Definitions of Managed Objects for the Ethernet WAN Interface Sublayer
References Referenced by
Proposed Standard normatively references
RFC 3638
As rfc3635
Applicability Statement for Reclassification of RFC 1643 to Historic Status
References Referenced by
Informational normatively references
RFC 4836
As rfc3635
Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
References Referenced by
Proposed Standard normatively references
RFC 4837
As rfc3635
Managed Objects of Ethernet Passive Optical Networks (EPON)
References Referenced by
Proposed Standard normatively references
RFC 5066
As rfc3635
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
References Referenced by
Proposed Standard normatively references
RFC 5603
As rfc3635
Ethernet Pseudowire (PW) Management Information Base (MIB)
References Referenced by
Proposed Standard normatively references
RFC 4441
As rfc3635
The IEEE 802/IETF Relationship
References Referenced by
Informational informatively references
RFC 4878
As rfc3635
Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces
References Referenced by
Proposed Standard informatively references
RFC 6767
As rfc3635
Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIB
References Referenced by
Proposed Standard informatively references
RFC 7448
As rfc3635
MIB Transfer from the IETF to the IEEE 802.3 WG
References Referenced by
Informational informatively references
RFC 8892
As rfc3635
Guidelines and Registration Procedures for Interface Types and Tunnel Types
References Referenced by
Proposed Standard informatively references
RFC 3796
As rfc3635
Survey of IPv4 Addresses in Currently Deployed IETF Operations & Management Area Standards Track and Experimental Documents
References Referenced by
Informational Possible Reference
RFC 7224
As rfc3635
IANA Interface Type YANG Module
References Referenced by
Proposed Standard Possible Reference