Explicit RPF Vector
draft-asghar-pim-explicit-rpf-vector-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Javed Asghar , IJsbrand Wijnands , Sowmya Krishnaswamy , Apoorva Karan , Vishal Arya | ||
Last updated | 2013-05-09 (Latest revision 2013-02-20) | ||
Replaced by | draft-ietf-pim-explicit-rpf-vector | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-pim-explicit-rpf-vector | |
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
This document describes a use of the Reverse Path Forwarding (RPF) Vector TLV as defined in [RPC 5496] to build multicast trees via an explicitly configured path sent in the PIM join.
Authors
Javed Asghar
IJsbrand Wijnands
Sowmya Krishnaswamy
Apoorva Karan
Vishal Arya
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)