References from draft-boro-opsawg-ntw-attachment-circuit
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 |
---|---|---|---|---|
draft-boro-opsawg-teas-attachment-circuit |
YANG Data Models for 'Attachment Circuits'-as-a-Service (ACaaS)
References Referenced by |
normatively references | ||
draft-boro-opsawg-teas-common-ac |
A Common YANG Data Model for Attachment Circuits
References Referenced by |
normatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | normatively references | |
RFC 6020 |
YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6241 |
Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6242 |
Using the NETCONF Protocol over Secure Shell (SSH)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6991 |
Common YANG Data Types
References Referenced by |
Proposed Standard | normatively references | |
RFC 7665 |
Service Function Chaining (SFC) Architecture
References Referenced by |
Informational | informatively references | |
RFC 8040 |
RESTCONF Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8177 |
YANG Data Model for Key Chains
References Referenced by |
Proposed Standard | normatively references | |
RFC 8294 |
Common YANG Data Types for the Routing Area
References Referenced by |
Proposed Standard | normatively references | |
RFC 8340 |
YANG Tree Diagrams
References Referenced by |
Best Current Practice | informatively references | |
RFC 8341 |
Network Configuration Access Control Model
References Referenced by |
Internet Standard | normatively references | |
RFC 8342 |
Network Management Datastore Architecture (NMDA)
References Referenced by |
Proposed Standard | normatively references | |
RFC 8343 |
A YANG Data Model for Interface Management
References Referenced by |
Proposed Standard | normatively references | |
RFC 8446 |
The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by |
Proposed Standard | normatively references | |
RFC 8695 |
A YANG Data Model for the Routing Information Protocol (RIP)
References Referenced by |
Proposed Standard | informatively references | |
RFC 8969 |
A Framework for Automating Service and Network Management with YANG
References Referenced by |
Informational | informatively references | |
RFC 9181 |
A Common YANG Data Model for Layer 2 and Layer 3 VPNs
References Referenced by |
Proposed Standard | normatively references | |
RFC 9182 |
A YANG Network Data Model for Layer 3 VPNs
References Referenced by |
Proposed Standard | normatively references | |
RFC 9291 |
A YANG Network Data Model for Layer 2 VPNs
References Referenced by |
Proposed Standard | normatively references | |
RFC 9408 |
A YANG Network Data Model for Service Attachment Points (SAPs)
References Referenced by |
Proposed Standard | normatively references |