PIM NULL Register packing
draft-ramki-pim-null-register-packing-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Vikas Ramesh Kamath , Ramakrishnan Cokkanathapuram Sundaram | ||
| Last updated | 2019-03-03 (Latest revision 2018-08-30) | ||
| Replaced by | draft-ietf-pim-null-register-packing, draft-ietf-pim-null-register-packing, RFC 9465 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 carry 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 Ramesh Kamath
Ramakrishnan Cokkanathapuram Sundaram
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)