Skip to main content

References from draft-ietf-opsawg-teas-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.

Reference type help

Document Title Status Type Downref
draft-ietf-idr-bgp-model YANG Model for Border Gateway Protocol (BGP-4)
References Referenced by
Proposed Standard informatively references
draft-ietf-netmod-rfc8407bis Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
References Referenced by
informatively references
draft-ietf-opsawg-ac-lxsm-lxnm-glue A YANG Data Model for Augmenting VPN Service and Network Models with Attachment Circuits
References Referenced by
Proposed Standard informatively references
draft-ietf-opsawg-ntw-attachment-circuit A Network YANG Data Model for Attachment Circuits
References Referenced by
Proposed Standard informatively references
draft-ietf-opsawg-teas-common-ac A Common YANG Data Model for Attachment Circuits
References Referenced by
Proposed Standard normatively references
draft-ietf-teas-ietf-network-slice-nbi-yang A YANG Data Model for the RFC 9543 Network Slice Service
References Referenced by
informatively references
draft-ramseyer-grow-peering-api Peering API
References Referenced by
informatively references
RFC 2080 RIPng for IPv6
References Referenced by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2453 RIP Version 2
References Referenced by
Internet Standard informatively references
RFC 3644 Policy Quality of Service (QoS) Information Model
References Referenced by
Proposed Standard informatively references
RFC 3688 The IETF XML Registry
References Referenced by
Best Current Practice normatively references
RFC 3849 IPv6 Address Prefix Reserved for Documentation
References Referenced by
Informational informatively references
RFC 4364 BGP/MPLS IP Virtual Private Networks (VPNs)
References Referenced by
Proposed Standard normatively references
RFC 4552 Authentication/Confidentiality for OSPFv3
References Referenced by
Proposed Standard normatively references
RFC 4577 OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)
References Referenced by
Proposed Standard normatively references
RFC 5398 Autonomous System (AS) Number Reservation for Documentation Use
References Referenced by
Informational informatively references
RFC 5709 OSPFv2 HMAC-SHA Cryptographic Authentication
References Referenced by
Proposed Standard normatively references
RFC 5737 IPv4 Address Blocks Reserved for Documentation
References Referenced by
Informational informatively references
RFC 5798 Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6
References Referenced by
Proposed Standard normatively references
RFC 5880 Bidirectional Forwarding Detection (BFD)
References Referenced by
Proposed Standard normatively references
RFC 5925 The TCP Authentication Option
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 6151 Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms
References Referenced by
Informational informatively 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 6565 OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol
References Referenced by
Proposed Standard normatively references
RFC 6952 Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide
References Referenced by
Informational informatively references
RFC 6991 Common YANG Data Types
References Referenced by
Proposed Standard normatively references
RFC 7166 Supporting Authentication Trailer for OSPFv3
References Referenced by
Proposed Standard normatively references
RFC 7474 Security Extension for OSPFv2 When Using Manual Key Management
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 8299 YANG Data Model for L3VPN Service Delivery
References Referenced by
Proposed Standard informatively 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 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 8466 A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
References Referenced by
Proposed Standard informatively references
RFC 8695 A YANG Data Model for the Routing Information Protocol (RIP)
References Referenced by
Proposed Standard informatively references
RFC 8921 Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)
References Referenced by
Informational 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
RFC 9543 A Framework for Network Slices in Networks Built from IETF Technologies
References Referenced by
Informational informatively references