Browse Prior Art Database

Hierarchical Join/Prune Attributes (RFC7887) Disclosure Number: IPCOM000246755D
Original Publication Date: 2016-Jun-01
Included in the Prior Art Database: 2016-Jun-29
Document File: 16 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Venaas: AUTHOR [+2]


PIM Join attributes as defined in [RFC5384] allow for specifying a set of attributes for each of the joined or pruned sources in a PIM Join/Prune message. Attributes must be separately specified for each individual source in the message. However, in some cases, the same attributes and values need to be specified for some, or even all, the sources in the message. The attributes and their values then need to be repeated for each of the sources where they apply.

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

Internet Engineering Task Force (IETF)                         S. Venaas Request for Comments: 7887                                     J. Arango Updates: 5384                                              Cisco Systems Category: Standards Track                                    I. Kouvelas ISSN: 2070-1721                                          Arista Networks                                                                June 2016

                    Hierarchical Join/Prune Attributes


   This document defines a hierarchical method of encoding Join/Prune    attributes that provides a more efficient encoding when the same    attribute values need to be specified for multiple sources in a PIM    Join/Prune message.  This document updates RFC 5384 by renaming the    encoding type registry specified there.

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

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    ( 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 without warranty as    described in the Simplified BSD License.

Venaas, et al.               Standards Track                    [Page 1]
 RFC 7887           Hierarchical Join/Prune Attributes          June 2016

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3    2.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   3    3.  Hierarchical Join/Prune Attribute Definition  . . . . . . . .   3    4.  PIM Address Encoding Types  . . . . . . . . . . . . . . . . .   6    5.  Hierarchical...