Skip to main content

References from draft-ietf-idr-bgp-model

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-deprecate-as-set-confed-set Deprecation of AS_SET and AS_CONFED_SET in BGP
References Referenced by
informatively references
draft-ietf-tcpm-yang-tcp A YANG Model for Transmission Control Protocol (TCP) Configuration and State
References Referenced by
Proposed Standard normatively references
RFC 1997 BGP Communities Attribute
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 2385 Protection of BGP Sessions via the TCP MD5 Signature Option
References Referenced by
Proposed Standard informatively references
RFC 2439 BGP Route Flap Damping
References Referenced by
Proposed Standard normatively references
RFC 2622 Routing Policy Specification Language (RPSL)
References Referenced by
Proposed Standard informatively references
RFC 2918 Route Refresh Capability for BGP-4
References Referenced by
Proposed Standard normatively references
RFC 3688 The IETF XML Registry
References Referenced by
Best Current Practice normatively references
RFC 3765 NOPEER Community for Border Gateway Protocol (BGP) Route Scope Control
References Referenced by
Informational informatively references
RFC 4271 A Border Gateway Protocol 4 (BGP-4)
References Referenced by
Draft Standard normatively references
RFC 4360 BGP Extended Communities Attribute
References Referenced by
Proposed Standard normatively references
RFC 4364 BGP/MPLS IP Virtual Private Networks (VPNs)
References Referenced by
Proposed Standard normatively references
RFC 4451 BGP MULTI_EXIT_DISC (MED) Considerations
References Referenced by
Informational informatively references
RFC 4456 BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
References Referenced by
Draft Standard normatively references
RFC 4659 BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN
References Referenced by
Proposed Standard normatively references
RFC 4724 Graceful Restart Mechanism for BGP
References Referenced by
Proposed Standard normatively references
RFC 4760 Multiprotocol Extensions for BGP-4
References Referenced by
Draft Standard normatively references
RFC 4761 Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling
References Referenced by
Proposed Standard normatively references
RFC 5065 Autonomous System Confederations for BGP
References Referenced by
Draft Standard normatively references
RFC 5082 The Generalized TTL Security Mechanism (GTSM)
References Referenced by
Proposed Standard informatively references
RFC 5398 Autonomous System (AS) Number Reservation for Documentation Use
References Referenced by
Informational informatively references
RFC 5701 IPv6 Address Specific BGP Extended Community Attribute
References Referenced by
Proposed Standard normatively references
RFC 5880 Bidirectional Forwarding Detection (BFD)
References Referenced by
Proposed Standard normatively references
RFC 5881 Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)
References Referenced by
Proposed Standard normatively references
RFC 5883 Bidirectional Forwarding Detection (BFD) for Multihop Paths
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 6514 BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
References Referenced by
Proposed Standard normatively references
RFC 6793 BGP Support for Four-Octet Autonomous System (AS) Number Space
References Referenced by
Proposed Standard normatively references
RFC 6811 BGP Prefix Origin Validation
References Referenced by
Proposed Standard normatively references
RFC 6991 Common YANG Data Types
References Referenced by
Proposed Standard normatively references
RFC 7454 BGP Operations and Security
References Referenced by
Best Current Practice informatively references
RFC 7607 Codification of AS 0 Processing
References Referenced by
Proposed Standard normatively references
RFC 7911 Advertisement of Multiple Paths in BGP
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 8092 BGP Large Communities Attribute
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 8277 Using BGP to Bind MPLS Labels to Address Prefixes
References Referenced by
Proposed Standard normatively 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 8349 A YANG Data Model for Routing Management (NMDA Version)
References Referenced by
Proposed Standard normatively references
RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by
Proposed Standard normatively references
RFC 8528 YANG Schema Mount
References Referenced by
Proposed Standard normatively references
RFC 8529 YANG Data Model for Network Instances
References Referenced by
Proposed Standard normatively references
RFC 9067 A YANG Data Model for Routing Policy
References Referenced by
Proposed Standard normatively references
RFC 9293 Transmission Control Protocol (TCP)
References Referenced by
Internet Standard normatively references
RFC 9314 YANG Data Model for Bidirectional Forwarding Detection (BFD)
References Referenced by
Proposed Standard normatively references