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.

Reference type help

Document	Title	Status	Type
BCP 206	Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks References Referenced by	Best Current Practice	normatively references
draft-ietf-ccamp-client-signal-yang	A YANG Data Model for Transport Network Client Signals References Referenced by		normatively references
draft-ietf-ccamp-otn-topo-yang	A YANG Data Model for Optical Transport Network Topology References Referenced by		normatively references
draft-ietf-ccamp-otn-tunnel-model	OTN Tunnel YANG Model References Referenced by		normatively references
draft-ietf-netmod-artwork-folding	Handling Long Lines in Inclusions in Internet-Drafts and RFCs References Referenced by	Informational	informatively references
draft-ietf-teas-te-topo-and-tunnel-modeling	TE Topology and Tunnel Modeling for Transport Networks References Referenced by		informatively references
draft-ietf-teas-yang-path-computation	Yang model for requesting Path Computation References Referenced by		normatively references
draft-ietf-teas-yang-te	A YANG Data Model for Traffic Engineering Tunnels and Interfaces References Referenced by		normatively references
draft-ietf-teas-yang-te-topo	YANG Data Model for Traffic Engineering (TE) Topologies References Referenced by	Proposed Standard	normatively references
draft-ietf-teas-yang-te-types	Traffic Engineering Common YANG Types References Referenced by	Proposed Standard	informatively references
draft-zhang-teas-actn-yang	Applicability of YANG models for Abstraction and Control of Traffic Engineered Networks References Referenced by		informatively references
draft-zheng-ccamp-client-topo-yang	A YANG Data Model for Ethernet TE Topology References Referenced by		normatively references
RFC 4427	Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS) References Referenced by	Informational	normatively references
RFC 4655	A Path Computation Element (PCE)-Based Architecture References Referenced by	Informational	normatively 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	normatively references
RFC 8040	RESTCONF Protocol References Referenced by	Proposed Standard	informatively references
RFC 8294	Common YANG Data Types for the Routing Area 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	normatively 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	normatively references