RFC 7887: Hierarchical Join/Prune Attributes
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7887
- Published
- June 2016
- Authors
- S. Venaas; J. Arango; I. Kouvelas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 5384
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 8487Mtrace Version 2: Traceroute Facility for IP MulticastCurrent
October 2018
- RFC 7900Extranet Multicast in BGP/IP MPLS VPNsUpdated
June 2016
- RFC 7968Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination DataCurrent
August 2016
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?