RFC 1771: A Border Gateway Protocol 4 (BGP-4)

This document, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter-autonomous system routing…

Read RFC 1771 on the RFC Editor

Outgoing relationships (7 related RFCs)

Obsoletes — RFC 1654: A Border Gateway Protocol 4 (BGP-4)
Informative reference — RFC 1519: Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy
Informative reference — RFC 904: Exterior Gateway Protocol formal specification
Informative reference — RFC 1518: An Architecture for IP Address Allocation with CIDR
Informative reference — RFC 1092: EGP and policy based routing in the new NSFNET backbone
Informative reference — RFC 1772: Application of the Border Gateway Protocol in the Internet
Informative reference — RFC 1093: NSFNET routing architecture

Incoming relationships (33 related RFCs)

Obsoleted by, Informatively referenced by — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Normatively referenced by — RFC 3682: The Generalized TTL Security Mechanism (GTSM)
Normatively referenced by — RFC 4384: BGP Communities for Data Collection
Normatively referenced by — RFC 4264: BGP Wedgies
Normatively referenced by — RFC 4451: BGP MULTI_EXIT_DISC (MED) Considerations
Informatively referenced by — RFC 2328: OSPF Version 2
Informatively referenced by — RFC 4949: Internet Security Glossary, Version 2
Informatively referenced by — RFC 1997: BGP Communities Attribute
Informatively referenced by — RFC 2622: Routing Policy Specification Language (RPSL)
Informatively referenced by — RFC 4216: MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements
Informatively referenced by — RFC 2545: Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
Informatively referenced by — RFC 1772: Application of the Border Gateway Protocol in the Internet
Informatively referenced by — RFC 2101: IPv4 Address Behaviour Today
Informatively referenced by — RFC 3107: Carrying Label Information in BGP-4
Informatively referenced by — RFC 3964: Security Considerations for 6to4
Informatively referenced by — RFC 4110: A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)
Informatively referenced by — RFC 1863: A BGP/IDRP Route Server alternative to a full mesh routing
Informatively referenced by — RFC 1966: BGP Route Reflection An alternative to full mesh IBGP
Informatively referenced by — RFC 2283: Multiprotocol Extensions for BGP-4
Informatively referenced by — RFC 2764: A Framework for IP Based Virtual Private Networks
Informatively referenced by — RFC 4116: IPv4 Multihoming Practices and Limitations
Informatively referenced by — RFC 1965: Autonomous System Confederations for BGP
Informatively referenced by — RFC 1998: An Application of the BGP Community Attribute in Multi-home Routing
Informatively referenced by — RFC 2178: OSPF Version 2
Informatively referenced by — RFC 3037: LDP Applicability
Informatively referenced by — RFC 3913: Border Gateway Multicast Protocol (BGMP): Protocol Specification
Informatively referenced by — RFC 1773: Experience with the BGP-4 protocol
Informatively referenced by — RFC 1774: BGP-4 Protocol Analysis
Informatively referenced by — RFC 2791: Scalable Routing Design Principles
Informatively referenced by — RFC 3528: Mesh-enhanced Service Location Protocol (mSLP)
Informatively referenced by — RFC 5773: Analysis of Inter-Domain Routing Requirements and History
Informatively referenced by — RFC 2519: A Framework for Inter-Domain Route Aggregation
Informatively referenced by — RFC 4277: Experience with the BGP-4 Protocol