BMP Peer Up Message Namespace
draft-ietf-grow-bmp-peer-up-00
| Document | Type | Expired Internet-Draft (grow WG) | |
|---|---|---|---|
| Last updated | 2020-01-25 (latest revision 2019-07-24) | ||
| Replaces | draft-scudder-grow-bmp-peer-up | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| 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-grow-bmp-peer-up-00.txt
Abstract
RFC 7854, BMP, uses different message types for different purposes. Most of these are Type, Length, Value (TLV) structured. One message type, the Peer Up message, lacks a set of TLVs defined for its use, instead sharing a namespace with the Initiation message. Subsequent experience has shown that this namespace sharing was a mistake, as it hampers the extension of the protocol. This document updates RFC 7854 by creating an independent namespace for the Peer Up message. The changes in this document are formal only, compliant implementations of RFC 7854 also comply with this specification.
Authors
John Scudder (jgs@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)