PIM reserved bits and type space extension
draft-ietf-pim-reserved-bits-00

Document Type Active Internet-Draft (pim WG)
Last updated 2018-10-18
Replaces draft-venaas-pim-reserved-bits
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          S. Venaas
Internet-Draft                                       Cisco Systems, Inc.
Updates: 3973, 5015, 6754, 7761, 8364                          A. Retana
         (if approved)                                    Huawei R&D USA
Intended status: Standards Track                        October 12, 2018
Expires: April 15, 2019

               PIM reserved bits and type space extension
                    draft-ietf-pim-reserved-bits-00

Abstract

   The currently defined 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 RFC7761 and RFC3973 by defining the use of the
   currently Reserved field in the PIM common header.  This document
   further updates RFC7761 and RFC3973, along with RFC5015, RFC6754 and
   RFC8364, by specifying the use of the currently Reserved bits for
   each PIM message.

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 April 15, 2019.

Venaas & Retana          Expires April 15, 2019                 [Page 1]
Internet-Draft PIM reserved bits and type space extension   October 2018

Copyright Notice

   Copyright (c) 2018 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 Type 13 (Type Space Extension)  . . . . . .   4
     4.5.  Flag Bits for Type 14 (Type Space Extension)  . . . . . .   4
     4.6.  Flag Bits for Type 15 (Type Space Extension)  . . . . . .   4
   5.  PIM Type Space Extension  . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The currently defined PIM version 2 messages share a common message
   header format defined in the PIM Sparse Mode [RFC7761] and Dense Mode
   [RFC3973] specifications.  The common header definition contains
   eight reserved bits.  The message types defined in these documents
   all use this common header.  However, several messages already make
   use of one or more bits, including the Bootstrap [RFC5059], DF-
   Election [RFC5015], and PIM Flooding Mechanism (PFM) [RFC8364]
   messages.  There is no document formally specifying that these bits
   are to be used per message type.

Venaas & Retana          Expires April 15, 2019                 [Page 2]
Internet-Draft PIM reserved bits and type space extension   October 2018

   This document refers to the bits specified as Reserved in the common
   PIM header [RFC7761] [RFC3973] as PIM message type flag bits, or
Show full document text