Hierarchical Join/Prune Attributes
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 8
- Abstract
- 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.
- Publication Date
- 2016-06-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7887- Link
- https://doi.org/10.17487/RFC7887
- Author(s)
- Stig VenaasJesus ArangoIsidor Kouvelas
- Keyword(s)
- PIM
Latest version of IETF RFC 7887
Document Versions — IETF RFC 7887
-
▶ IETF RFC 7887 (2016-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 5384 [Active*]
- IETF RFC 7761 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7887.json
Amends:
IETF RFC 5384 [Active*]
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7887, Hierarchical Join/Prune Attributes. Available at https://doi.org/10.17487/RFC7887
Snippet:
IETF RFC 7887, Hierarchical Join/Prune Attributes. Available at https://doi.org/10.17487/RFC7887
HTML (ISO 690 compliant)
Preview:
IETF RFC 7887, Hierarchical Join/Prune Attributes. Available at https://doi.org/10.17487/RFC7887
Snippet:
<span class="citation"><cite>IETF RFC 7887</cite>, Hierarchical Join/Prune Attributes. Available at <a href="https://doi.org/10.17487/RFC7887" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7887</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7887, Hierarchical Join/Prune Attributes
doi: 10.17487/RFC7887
url: https://doi.org/10.17487/RFC7887
doi: 10.17487/RFC7887
url: https://doi.org/10.17487/RFC7887
Snippet:
<li> <cite id="bib-rfc7887">IETF RFC 7887</cite>, Hierarchical Join/Prune Attributes <span class="doi">10.17487/RFC7887</span> </li>