Skip to main content

References from draft-ietf-alto-oam-yang

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 Downref
draft-ietf-alto-new-transport The ALTO Transport Information Publication Service
References Referenced by
Proposed Standard informatively references
draft-ietf-netconf-http-client-server YANG Groupings for HTTP Clients and HTTP Servers
References Referenced by
Proposed Standard normatively references
draft-ietf-netconf-netconf-client-server NETCONF Client and Server Models
References Referenced by
Proposed Standard normatively references
draft-ietf-netconf-restconf-client-server RESTCONF Client and Server Models
References Referenced by
Proposed Standard normatively references
draft-ietf-netconf-tcp-client-server YANG Groupings for TCP Clients and TCP Servers
References Referenced by
Proposed Standard normatively references
draft-ietf-netconf-tls-client-server YANG Groupings for TLS Clients and TLS Servers
References Referenced by
Proposed Standard normatively references
draft-ietf-netconf-trust-anchors A YANG Data Model for a Truststore
References Referenced by
Proposed Standard 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 5424 The Syslog Protocol
References Referenced by
Proposed Standard 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 6291 Guidelines for the Use of the "OAM" Acronym in the IETF
References Referenced by
Best Current Practice informatively references
RFC 6991 Common YANG Data Types
References Referenced by
Proposed Standard normatively references
RFC 7285 Application-Layer Traffic Optimization (ALTO) Protocol
References Referenced by
Proposed Standard normatively references
RFC 7286 Application-Layer Traffic Optimization (ALTO) Server Discovery
References Referenced by
Proposed Standard normatively references
RFC 7921 An Architecture for the Interface to the Routing System
References Referenced by
Informational informatively references
RFC 7971 Application-Layer Traffic Optimization (ALTO) Deployment Considerations
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 8189 Multi-Cost Application-Layer Traffic Optimization (ALTO)
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 8346 A YANG Data Model for Layer 3 Topologies
References Referenced by
Proposed Standard informatively references
RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by
Proposed Standard normatively references
RFC 8641 Subscription to YANG Notifications for Datastore Updates
References Referenced by
Proposed Standard informatively references
RFC 8686 Application-Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery
References Referenced by
Proposed Standard normatively references
RFC 8895 Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
References Referenced by
Proposed Standard normatively references
RFC 8896 Application-Layer Traffic Optimization (ALTO) Cost Calendar
References Referenced by
Proposed Standard normatively references
RFC 9240 An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property Maps
References Referenced by
Proposed Standard normatively references
RFC 9241 Content Delivery Network Interconnection (CDNI) Footprint and Capabilities Advertisement Using Application-Layer Traffic Optimization (ALTO)
References Referenced by
Proposed Standard normatively references
RFC 9274 A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol
References Referenced by
Proposed Standard normatively references
RFC 9275 An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector
References Referenced by
Experimental normatively references Downref
RFC 9439 Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics
References Referenced by
Proposed Standard normatively references