Context updates in BGP
draft-djernaes-simple-context-update-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Djernaes | ||
| Last updated | 2006-10-16 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Currently BGP protocol can carry reachability information for multiple Address Families (AFI) and Subsequence Address Families (SAFI) using the Multiprotocol Extension[RFC2858], but it is limited to grouping of information based on the AFI/SAFI hierarchy. This document describes a mechanism to group and exchange prefix information based on properties other than just the AFI/ SAFI[RFC2858]. The mechanism is flexible and backwards compatible with the current methods for exchanging prefixes and hence does not require any changes to the the protocol formats. It introduces a new capability that allows two BGP speakers negotiate during the BGP OPEN phase in order to define what each AFI/SAFI means. In other words, the concept of a 'context' is defined and each such 'context' can be mapped to an AFI/SAFI. The context to AFI/SAFI mapping is only relevant to the BGP peers of the BGP session and hence offers great flexibility in how 2 BGP speakers can choose to group and exchange prefix information.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)