RFC4456 · BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents a serious scaling problem that has been well documented with several alternatives proposed. This document describes the use and design of a method known as "route reflection" to alleviate the need for "full mesh" Internal BGP (IBGP). This document obsoletes RFC 2796 and RFC 1966. [STANDARDS-TRACK]
IETF · RFCОфициальная английская аннотация
The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents a serious scaling problem that has been well documented with several alternatives proposed. This document describes the use and design of a method known as "route reflection" to alleviate the need for "full mesh" Internal BGP (IBGP). This document obsoletes RFC 2796 and RFC 1966. [STANDARDS-TRACK]
{
"id": "RFC4456",
"number": 4456,
"title_en": "BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents a serious scaling problem that has been well documented with several alternatives proposed. This document describes the use and design of a method known as \"route reflection\" to alleviate the need for \"full mesh\" Internal BGP (IBGP). This document obsoletes RFC 2796 and RFC 1966. [STANDARDS-TRACK]",
"authors": [
"T. Bates",
"E. Chen",
"R. Chandra"
],
"organizations": [],
"publication_date": "2006-04-01",
"current_status": "DRAFT STANDARD",
"current_status_ru": "Проект стандарта (устаревшая стадия)",
"publication_status": "DRAFT STANDARD",
"publication_status_ru": "Проект стандарта (устаревшая стадия)",
"lifecycle": "active",
"lifecycle_ru": "Действующий",
"stream": "IETF",
"stream_ru": "IETF",
"area": "rtg",
"area_ru": "Маршрутизация",
"working_group": "idr",
"source_draft": "draft-ietf-idr-rfc2796bis-02",
"page_count": 12,
"doi": "10.17487/RFC4456",
"keywords": [
"BGP-RR",
"Border",
"Gateway",
"Protocol",
"autonomous",
"system"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [
"RFC1966",
"RFC2796"
],
"obsoleted_by": [],
"updates": [],
"updated_by": [
"RFC7606"
],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc4456/",
"html": "https://www.rfc-editor.org/rfc/rfc4456.html",
"txt": "https://www.rfc-editor.org/rfc/rfc4456.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc4456/"
}
}