BGP Based Generic TransPort (bgpBGP)
draft-white-bgpbgp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alvaro Retana , Russ White , Jakob Heitz | ||
| Last updated | 2014-12-20 (Latest revision 2014-06-18) | ||
| 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
A wide array of information is being carried (or proposed to be carried) through BGP peering sessions. While this information is necessary and valid, BGP was not designed to carry blobs of information, but rather network layer reachability and information related directly to forwarding traffic from peer to peer. This document proposes a new BGP message type with a well defined structure to use BGP peering sessions for information passed from provider to provider along edge peering points, the BGP based Generic transPort (bgpBGP). This message type is designed to allow any pair of BGP speakers to transfer information within an existing session, or for BGP peering semantics to be used with multihop sessions between "information exchange speakers" within an autonomous system. The new message type is designed to provide flexibility by allowing the encoding of virtually any information within a BGP session through the use of type-length-vector formatting.
Authors
Alvaro Retana
Russ White
Jakob Heitz
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)