References from rfc8676

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
BCP 215 YANG Tree Diagrams
References Referenced by
Best Current Practice informatively references
draft-ietf-softwire-iftunnel A YANG Data Model for Tunnel Interface Types
References Referenced by
Proposed Standard normatively references
RFC 3688 The IETF XML Registry
References Referenced by
Best Current Practice normatively references
RFC 4213 Basic Transition Mechanisms for IPv6 Hosts and Routers
References Referenced by
Proposed Standard informatively 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 6333 Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
References Referenced by
Proposed Standard informatively references
RFC 6346 The Address plus Port (A+P) Approach to the IPv4 Address Shortage
References Referenced by
Experimental informatively references
RFC 6991 Common YANG Data Types
References Referenced by
Proposed Standard normatively references
RFC 7224 IANA Interface Type YANG Module
References Referenced by
Proposed Standard normatively references
RFC 7422 Deterministic Address Mapping to Reduce Logging in Carrier-Grade NAT Deployments
References Referenced by
Informational informatively references
RFC 7596 Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
References Referenced by
Proposed Standard normatively references
RFC 7597 Mapping of Address and Port with Encapsulation (MAP-E)
References Referenced by
Proposed Standard normatively references
RFC 7598 DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients
References Referenced by
Proposed Standard normatively references
RFC 7599 Mapping of Address and Port using Translation (MAP-T)
References Referenced by
Proposed Standard normatively references
RFC 7950 The YANG 1.1 Data Modeling Language
References Referenced by
Proposed Standard normatively references
RFC 8040 RESTCONF Protocol
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 informatively references
RFC 8343 A YANG Data Model for Interface Management
References Referenced by
Proposed Standard normatively references
RFC 8344 A YANG Data Model for IP Management
References Referenced by
Proposed Standard informatively references
RFC 8349 A YANG Data Model for Routing Management (NMDA Version)
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 8512 A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)
References Referenced by
Proposed Standard informatively references
RFC 8513 A YANG Data Model for Dual-Stack Lite (DS-Lite)
References Referenced by
Proposed Standard informatively references
STD 91 Network Configuration Access Control Model
References Referenced by
Internet Standard normatively references