Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Explicit Reverse Path Forwarding (RPF) Vector (RFC7891)

IP.com Disclosure Number: IPCOM000246759D
Original Publication Date: 2016-Jun-01
Included in the Prior Art Database: 2016-Jun-29
Document File: 18 page(s) / 19K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Asghar: AUTHOR [+6]

Abstract

The procedures in [RFC5496] define how an RPF Vector can be used to influence the path selection in the absence of a route to the source. The same procedures can be used to override a route to the source when it exists. It is possible to include multiple RPF Vectors in the list where each router along the path will perform a unicast route lookup on the first Vector in the attribute list. Once the router owning the address of the RPF Vector is reached, following the procedures in [RFC5496], the RPF Vector will be removed from the attribute list. This will result in a 'loosely' routed path that still depends on unicast reachability to the RPF Vector(s).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 14% of the total text.

Internet Engineering Task Force (IETF)                         J. Asghar Request for Comments: 7891                             IJ. Wijnands, Ed. Category: Standards Track                                S. Krishnaswamy ISSN: 2070-1721                                                 A. Karan                                                            Cisco Systems                                                                  V. Arya                                                             DIRECTV Inc.                                                                June 2016

              Explicit Reverse Path Forwarding (RPF) Vector

Abstract

   The PIM Reverse Path Forwarding (RPF) Vector TLV defined in RFC 5496    can be included in a PIM Join Attribute such that the RPF neighbor is    selected based on the unicast reachability of the RPF Vector instead    of the source or Rendezvous Point associated with the multicast tree.

   This document defines a new RPF Vector Attribute type such that an    explicit RPF neighbor list can be encoded in the PIM Join Attribute,    thus bypassing the unicast route lookup.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7891.

Asghar, et al.               Standards Track                    [Page 1]
 RFC 7891      Explicit Reverse Path Forwarding (RPF) Vector    June 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided w...