BMP Peer Up Message Namespace
draft-ietf-grow-bmp-peer-up-00
GROW J. Scudder
Internet-Draft Juniper Networks
Updates: 7854 (if approved) July 24, 2019
Intended status: Standards Track
Expires: January 25, 2020
BMP Peer Up Message Namespace
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 25, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
Scudder Expires January 25, 2020 [Page 1]
Internet-Draft BMP Peer Up Namespace July 2019
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. String Definition . . . . . . . . . . . . . . . . . . . . . . 3
3. Changes to RFC 7854 . . . . . . . . . . . . . . . . . . . . . 3
3.1. Revision to Information TLV, Renamed as Initiation
Information TLV . . . . . . . . . . . . . . . . . . . . . 3
3.2. Revision to Peer Up Notification . . . . . . . . . . . . 3
3.3. Definition of Peer Up Information TLV . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
[RFC7854] defines a number of different BMP message types. With the
exception of the Route Monitoring message type, these messages are
TLV-structured. Most message types have distinct namespaces and IANA
registries. However, the namespace of the Peer Up message overlaps
that of the Initiation message. As the BMP protocol has been
extended, this oversight has become problematic. In this document,
we create a distinct namespace for the Peer Up message to eliminate
this overlap, and create the corresponding missing registry.
The changes in this document are formal only, compliant
implementations of [RFC7854] also comply with this specification.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Scudder Expires January 25, 2020 [Page 2]
Internet-Draft BMP Peer Up Namespace July 2019
2. String Definition
A string TLV is a free-form sequence of UTF-8 characters whose length
is given by the TLV's Length field. There is no requirement to
terminate the string with a null (or any other particular) character
-- the Length field gives its termination.
Show full document text