PIM Null register packing

The information below is for an old version of the document
Document Type Expired Internet-Draft (pim WG)
Authors Vikas Kamath  , Ramakrishnan Sundaram  , Raunak Banthia 
Last updated 2020-08-29 (latest revision 2020-02-26)
Replaces draft-ramki-pim-null-register-packing
Stream Internet Engineering Task Force (IETF)
Expired & archived
pdf htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Revised I-D Needed - Issue raised by AD
Document shepherd Mike McBride
Shepherd write-up Show (last changed 2020-02-24)
IESG IESG state Expired (IESG: Dead)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to Mike McBride <mmcbride7@gmail.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Vikas Kamath (vkamath@vmware.com)
Ramakrishnan Sundaram (ramaksun@cisco.com)
Raunak Banthia (rbanthia@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)