PIM Message Type Space Extension and Reserved Bits
draft-ietf-pim-reserved-bits-04
Network Working Group S. Venaas
Internet-Draft Cisco Systems, Inc.
Obsoletes: 6166 (if approved) A. Retana
Updates: 3973, 5015, 5059, 6754, 7761, Futurewei Technologies, Inc.
8364 (if approved) September 19, 2019
Intended status: Standards Track
Expires: March 22, 2020
PIM Message Type Space Extension and Reserved Bits
draft-ietf-pim-reserved-bits-04
Abstract
The PIM version 2 messages share a common message header format. The
common header definition contains eight reserved bits. This document
specifies how these bits may be used by individual message types, and
creates a registry containing the per-message-type usage. This
document also extends the PIM type space by defining three new
message types. For each of the new types, four of the previously
reserved bits are used to form an extended type range.
This document Updates RFC 7761 and RFC 3973 by defining the use of
the currently Reserved field in the PIM common header. This document
further updates RFC 7761 and RFC 3973, along with RFC 5015, RFC 5059,
RFC 6754 and RFC 8364, by specifying the use of the currently
Reserved bits for each PIM message.
This document obsoletes RFC 6166.
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 March 22, 2020.
Venaas & Retana Expires March 22, 2020 [Page 1]
Internet-Draft PIM Type Extension and Reserved Bits September 2019
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
(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
2. Conventions used in this document . . . . . . . . . . . . . . 3
3. PIM header common format . . . . . . . . . . . . . . . . . . 3
4. Flag Bit definitions . . . . . . . . . . . . . . . . . . . . 3
4.1. Flag Bits for Type 4 (Bootstrap) . . . . . . . . . . . . 4
4.2. Flag Bits for Type 10 (DF Election) . . . . . . . . . . . 4
4.3. Flag Bits for Type 12 (PFM) . . . . . . . . . . . . . . . 4
4.4. Flag Bits for Types 13, 14 and 15 (Type Space Extension) 4
5. PIM Type Space Extension . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
The PIM version 2 messages share a common message header format
defined in the PIM Sparse Mode [RFC7761] specification. The common
header definition contains eight Reserved bits. While all message
types use this common header, there is no document formally
specifying that these bits are to be used per message type.
This document refers to the bits specified as Reserved in the common
PIM header [RFC7761] as PIM message type Flag Bits, or simply Flag
Bits, and it specifies that they are to be separately used on a per-
message-type basis. It creates a registry containing the per-
message-type usage.
Venaas & Retana Expires March 22, 2020 [Page 2]
Internet-Draft PIM Type Extension and Reserved Bits September 2019
This document Updates [RFC7761] and [RFC3973] by defining the use of
the currently Reserved field in the PIM common header. This document
Show full document text