
datatracker.ietf.org/doc/rfc4271
Preview meta tags from the datatracker.ietf.org website.
Linked Hostnames
10- 85 links todatatracker.ietf.org
- 6 links towww.ietf.org
- 6 links towww.rfc-editor.org
- 2 links togithub.com
- 2 links tomailarchive.ietf.org
- 1 link tostatus.ietf.org
- 1 link totrustee.ietf.org
- 1 link towww.iab.org
Thumbnail

Search Engine Appearance
https://datatracker.ietf.org/doc/rfc4271
RFC 4271: A Border Gateway Protocol 4 (BGP-4)
A Border Gateway Protocol 4 (BGP-4) (RFC 4271, January 2006)
Bing
RFC 4271: A Border Gateway Protocol 4 (BGP-4)
https://datatracker.ietf.org/doc/rfc4271
A Border Gateway Protocol 4 (BGP-4) (RFC 4271, January 2006)
DuckDuckGo

RFC 4271: A Border Gateway Protocol 4 (BGP-4)
A Border Gateway Protocol 4 (BGP-4) (RFC 4271, January 2006)
General Meta Tags
11- titleRFC 4271 - A Border Gateway Protocol 4 (BGP-4)
- charsetutf-8
- X-UA-CompatibleIE=edge
- viewportwidth=device-width, initial-scale=1
- article:sectionIETF - Internet Engineering Task Force
Open Graph Meta Tags
10- og:titleRFC 4271: A Border Gateway Protocol 4 (BGP-4)
- og:urlhttps://datatracker.ietf.org/doc/rfc4271/
- og:site_nameIETF Datatracker
- og:descriptionThis document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol. The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASes) that reachability information traverses. This information is sufficient for constructing a graph of AS connectivity for this reachability from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced. BGP-4 provides a set of mechanisms for supporting Classless Inter-Domain Routing (CIDR). These mechanisms include support for advertising a set of destinations as an IP prefix, and eliminating the concept of network "class" within BGP. BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of AS paths. This document obsoletes RFC 1771. [STANDARDS-TRACK]
- og:typearticle
Twitter Meta Tags
1- twitter:cardsummary_large_image
Link Tags
13- alternate/feed/document-changes/rfc4271/
- apple-touch-iconhttps://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-180.png
- canonicalhttps://datatracker.ietf.org/doc/rfc4271/
- iconhttps://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-32.png
- iconhttps://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-16.png
Emails
7- yakov%40juniper.net
- skh%40ndzh.com
- tony.li%40tony.li
- alex.zinin%40alcatel.com
- [email protected]?subject=Mail%20regarding%20rfc4271
Links
106- https://datatracker.ietf.org
- https://datatracker.ietf.org/accounts/create
- https://datatracker.ietf.org/accounts/login/?next=/doc/rfc4271
- https://datatracker.ietf.org/accounts/reset
- https://datatracker.ietf.org/accounts/settings