PIM Null-Register packing
draft-ietf-pim-null-register-packing-06
Document | Type | Active Internet-Draft (pim WG) | |
---|---|---|---|
Authors | Vikas Kamath , Ramakrishnan Sundaram , Raunak Banthia , Ananya Gopal | ||
Last updated | 2020-10-31 | ||
Replaces | draft-ramki-pim-null-register-packing | ||
Stream | Internent Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | plain text xml pdf htmlized (tools) htmlized bibtex | ||
Stream | WG state | WG Document | |
Document shepherd | Mike McBride | ||
Shepherd write-up | Show (last changed 2020-02-24) | ||
IESG | IESG state | I-D Exists (IESG: Dead) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alvaro Retana | ||
Send notices to | Mike McBride <mmcbride7@gmail.com> |
Network Working Group V. Kamath Internet-Draft VMware Intended status: Standards Track R. Chokkanathapuram Sundaram Expires: May 4, 2021 Cisco Systems, Inc. R. Banthia Apstra A. Gopal Cisco Systems, Inc. October 31, 2020 PIM Null-Register packing draft-ietf-pim-null-register-packing-06 Abstract In PIM-SM networks PIM Register messages are sent by the Designated Router (DR) to the Rendezvous Point (RP) to signal the presence of Multicast sources in the network. There are periodic PIM Null- Registers sent by a DR to the RP to keep the state alive at the RP as long as the source is active. The PIM Null-Register message carries information about a single Multicast source and group. This document defines a standard to send information about multiple multicast sources and multicast groups in a single PIM Null-Register message, in a packed format. This document also discusses the interoperability between PIM routers that support the new packed message format and PIM routers that do not support the new format. 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 May 4, 2021. Kamath, et al. Expires May 4, 2021 [Page 1] Internet-Draft PIM Null-Register packing October 2020 Copyright Notice Copyright (c) 2020 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 1.1. Conventions used in this document . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2. Packed Register Capability . . . . . . . . . . . . . . . . . 3 3. PIM Packed Null-Register message . . . . . . . . . . . . . . 4 4. PIM Packed Register-Stop message format . . . . . . . . . . . 5 5. Protocol operation . . . . . . . . . . . . . . . . . . . . . 6 6. PIM Anycast RP considerations . . . . . . . . . . . . . . . . 6 7. PIM RP router version downgrade . . . . . . . . . . . . . . . 7 8. Fragmentation consideration . . . . . . . . . . . . . . . . . 7 9. Security Considerations . . . . . . . . . . . . . . . . . . . 7 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 12. Normative References . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 1. Introduction PIM Null-Registers are sent by a DR periodically for Multicast streams to keep the states active on the RP, as long as the source is active. As the number of multicast sources increases, the number of PIM Null-Register messages that are sent also increases. This results in more PIM packet processing at the RP and at the DRs. The control plane policing (COPP), monitors the packets that are 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 messages. This document defines a method to efficiently pack multiple PIM Null-Registers [[RFC7761] (Section 4.4)] and Register-Stops [[RFC7761] (Section 3.2)] into aShow full document text