PIM Null register packing
draft-ramki-pim-null-register-packing-03

Document Type Expired Internet-Draft (individual)
Last updated 2019-10-14 (latest revision 2019-04-12)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ramki-pim-null-register-packing-03.txt

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.

Authors

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.)