References from rfc8432
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.
| 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 | |
| draft-ietf-ccamp-alarm-module |
YANG Alarm Module Refs Ref'd by |
Proposed Standard | informatively references | |
| draft-ietf-ccamp-mw-yang |
A YANG Data Model for Microwave Radio Link Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2863 |
The Interfaces Group MIB Refs Ref'd by |
Draft Standard | informatively references | |
| RFC 3444 |
On the Difference between Information Models and Data Models Refs Ref'd by |
Informational | informatively references | |
| RFC 6241 |
Network Configuration Protocol (NETCONF) Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 7426 |
Software-Defined Networking (SDN): Layers and Architecture Terminology Refs Ref'd by |
Informational | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 8343 |
A YANG Data Model for Interface Management Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8344 |
A YANG Data Model for IP Management Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8348 |
A YANG Data Model for Hardware Management Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8349 |
A YANG Data Model for Routing Management (NMDA Version) Refs Ref'd by |
Proposed Standard | informatively references |