References from draft-ietf-ccamp-transport-nbi-app-statement
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-ietf-ccamp-client-signal-yang |
A YANG Data Model for Transport Network Client Signals
References Referenced by |
informatively references | ||
| draft-ietf-ccamp-eth-client-te-topo-yang |
A YANG Data Model for Ethernet TE Topology
References Referenced by |
informatively references | ||
| draft-ietf-ccamp-otn-topo-yang |
A YANG Data Model for Optical Transport Network Topology
References Referenced by |
Proposed Standard | informatively references | |
| draft-ietf-ccamp-otn-tunnel-model |
OTN Tunnel YANG Model
References Referenced by |
informatively references | ||
| draft-ietf-teas-actn-yang |
Applicability of YANG models for Abstraction and Control of Traffic Engineered Networks
References Referenced by |
informatively references | ||
| draft-ietf-teas-yang-path-computation |
A YANG Data Model for requesting path computation
References Referenced by |
informatively references | ||
| draft-ietf-teas-yang-te |
A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces
References Referenced by |
informatively references | ||
| RFC 4427 |
Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)
References Referenced by |
Informational | informatively references | |
| RFC 4655 |
A Path Computation Element (PCE)-Based Architecture
References Referenced by |
Informational | informatively references | |
| RFC 5521 |
Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6241 |
Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6242 |
Using the NETCONF Protocol over Secure Shell (SSH)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6898 |
Link Management Protocol Behavior Negotiation and Configuration Modifications
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7926 |
Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
References Referenced by |
Best Current Practice | informatively references | |
| RFC 8040 |
RESTCONF Protocol
References Referenced by |
Proposed Standard | informatively references | |
| RFC 8309 |
Service Models Explained
References Referenced by |
Informational | informatively references | |
| RFC 8341 |
Network Configuration Access Control Model
References Referenced by |
Internet Standard | informatively references | |
| RFC 8345 |
A YANG Data Model for Network Topologies
References Referenced by |
Proposed Standard | informatively references | |
| RFC 8446 |
The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by |
Proposed Standard | informatively references | |
| RFC 8453 |
Framework for Abstraction and Control of TE Networks (ACTN)
References Referenced by |
Informational | informatively references | |
| RFC 8792 |
Handling Long Lines in Content of Internet-Drafts and RFCs
References Referenced by |
Informational | informatively references | |
| RFC 8795 |
YANG Data Model for Traffic Engineering (TE) Topologies
References Referenced by |
Proposed Standard | informatively references |