PIM Null register packing
draft-ietf-pim-null-register-packing-02

The information below is for an old version of the document
Document Type Active Internet-Draft (pim WG)
Last updated 2019-04-16 (latest revision 2019-03-11)
Stream IETF
Intended RFC status (None)
Formats pdf htmlized 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                                          V. Kamath
Internet-Draft                                                    VMware
Intended status: Standards Track            R. Chokkanathapuram Sundaram
Expires: September 12, 2019                          Cisco Systems, Inc.
                                                          March 11, 2019

                       PIM Null register packing
                draft-ietf-pim-null-register-packing-02

Abstract

   In PIM-SM networks PIM registers are sent from the first hop router
   to the RP (Rendezvous Point) to signal the presence of Multicast
   source in the network.  There are periodic PIM Null registers sent
   from first hop router to the RP to keep the state alive at the RP as
   long as the source is active.  The PIM Null register packet carries
   information about a single Multicast source and group.  This document
   defines a standard to send multiple Multicast source and group
   information in a single pim Null register packet and the
   interoperability between the PIM routers which do not understand the
   packet format with multiple Multicast source and group details.

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 September 12, 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

Kamath & ChokkanathapurExpiresaSeptember 12, 2019               [Page 1]
Internet-Draft          PIM Null register packing             March 2019

   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.  Conventions Used in This Document . . . . . . . . . . . .   2
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  PIM Register Stop format with capability option . . . . . . .   3
   3.  New PIM Null register message . . . . . . . . . . . . . . . .   4
   4.  New PIM Register Stop message format  . . . . . . . . . . . .   4
   5.  Protocol operation  . . . . . . . . . . . . . . . . . . . . .   5
   6.  PIM Anycast RP considerations . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   PIM Null registers are sent by First hop routers periodically for
   Multicast streams to keep the states active on the RP as long as the
   Multicast source is alive.  As the number of multicast sources
   increases, the number of PIM Null register packets that are sent
   increases at a given time.  This results in more PIM packet
   processing at RP and FHR.  The control plane policing (COPP),
   monitors the packets that gets processed by the control plane.  Due
   to the high rate at which Null registers are received at the RP, this
   can lead to COPP drops of Multicast PIM Null register packets.  This
   draft proposes a method to efficiently pack multiple PIM Null
   registers and register stop into a single message as these packets
   anyway don't contain data.  The draft also proposes interoperability
   with the routers that do not understand the new packet format.

1.1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Kamath & ChokkanathapurExpiresaSeptember 12, 2019               [Page 2]
Show full document text