Multicast Routing Blackhole Avoidance
draft-asati-pim-multicast-routing-blackhole-avoid-00

Document Type Expired Internet-Draft (individual)
Authors Rajiv Asati  , Mike McBride 
Last updated 2008-07-06
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text 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-asati-pim-multicast-routing-blackhole-avoid-00.txt

Abstract

This document specifies a mechanism to avoid blackholing of IP Multicast traffic due to the disruption of multicast tree during the time when the RPF neighbor is yet to become the PIM neighbor. Such scenario is possible during the topology change (e.g. link UP) in an IP network that employs PIM-SM (or SSM) as the multicast routing protocol and a unicast routing protocol (including static routing). Conventions used in this document In examples, "C:" and "S:" indicate lines sent by the client and server respectively. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119 [RFC2119].

Authors

Rajiv Asati (rajiva@cisco.com)
Mike McBride (mmcbride7@gmail.com)

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