Extended Optional Parameters Length for BGP OPEN Message
draft-ietf-idr-ext-opt-param-05
| Document | Type | Expired Internet-Draft (idr WG) | |
|---|---|---|---|
| Last updated | 2016-12-30 (latest revision 2016-06-28) | ||
| Replaces | draft-chen-bgp-ext-opt-param | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-idr-ext-opt-param-05.txt
Abstract
The Optional Parameters in the BGP OPEN message as defined in the base BGP specification are limited to 255 octets due to a one-octet length field. BGP Capabilities are carried in this field and may foreseeably exceed 255 octets in the future, leading to concern about this limitation. In this document we update RFC 4271 by extending the BGP OPEN length field in a backward-compatible manner. The Parameter Length field of individual Optional Parameters is similarly extended.
Authors
Enke Chen
(enkechen@cisco.com)
John Scudder
(jgs@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)