RFC 6769: Simple Virtual Aggregation (S-VA)
In plain English — editorial summary, not part of the RFC
All BGP routers in the Default-Free Zone (DFZ) are required to carry all routes in the Default-Free Routing Table (DFRT). This document describes a technique, Simple Virtual Aggregation (S-VA), that allows some BGP routers not to install all of those routes into the Forwarding Information Base (FIB). Some routers in an Autonomous System (AS) announce an aggregate (the VA prefix) in addition to the routes they already announce. This enables other routers not to install the routes covered by the VA prefix into the FIB as long as those routes have the same next-hop as the VA prefix. The VA prefixes that are announced within an AS are not announced to any other AS. The described functionality is of very low operational complexity, as it proposes a confined BGP speaker solution without any dependency on network-wide configuration or requirement for any form of intra-domain tunneling. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6769
- Published
- October 2012
- Authors
- R. Raszuk; J. Heitz; A. Lo; L. Zhang; X. Xu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6768ATM-Based xDSL Bonded Interfaces MIBCurrent
February 2013
- RFC 6767Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIBCurrent
February 2013
- RFC 6766xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIBCurrent
February 2013
- RFC 6765xDSL Multi-Pair Bonding (G.Bond) MIBCurrent
February 2013
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 6198Requirements for the Graceful Shutdown of BGP SessionsCurrent
April 2011
- RFC 7854BGP Monitoring Protocol (BMP)Updated
June 2016
- RFC 7908Problem Definition and Classification of BGP Route LeaksCurrent
June 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?