Protocol independent multicast- Next Generation (PIM-NG): Protocol Specifications
draft-sami-pim-ng-11

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2017-11-26 (latest revision 2017-05-25)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-sami-pim-ng-11.txt

Abstract

This document specifies protocol independent multicast- Next generation or simply called PIM-NG. PIM-NG uses the underlying unicast routing information, but unlike PIM-SM it doesn't necessarily need to build unidirectional shared trees rooted at a Rendezvous Point (RP) per group, due to the fact that the processes through which a source registers with the Rendezvous Point and a host finds the source of the multicast destination groups it needs are done in a whole new way and hence, the source of multicast group (G) is discovered faster. So at some points PIM-NG works faster than its predecessor. Also the new Domain concept, unique to PIM-NG, along the RPF check method used in PIM-NG specifications provides many features along a robust and flexible control and administration over multicast networks.

Authors

saeed sami (sami@ssami.biz)

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