Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 18
- Abstract
- This memo defines an address allocation policy in which the address of the Rendezvous Point (RP) is encoded in an IPv6 multicast group address. For Protocol Independent Multicast - Sparse Mode (PIM-SM), this can be seen as a specification of a group-to-RP mapping mechanism. This allows an easy deployment of scalable inter-domain multicast and simplifies the intra-domain multicast configuration as well. This memo updates the addressing format presented in RFC 3306. [STANDARDS-TRACK]
- Publication Date
- 2004-11-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3956- Link
- https://doi.org/10.17487/RFC3956
- Author(s)
- Pekka SavolaBrian Haberman
- Keyword(s)
- Rendezvous Point, IP
Latest version of IETF RFC 3956
Document Versions — IETF RFC 3956
-
▶ IETF RFC 3956 (2004-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Amended by:
- RFC7371 NOT IN REGISTRY
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3306 [Active*]
- IETF RFC 3513 [Superseded*]
Bibliographic Reference(s)
- Hagino, J. and K. Ettikan, "An analysis of IPv6 anycast" , Work in Progress, June 2003. EXTERNAL
- Savola, P., Lehtonen, R., and D. Meyer, "PIM-SM Multicast Routing Security Issues and Enhancements", Work in Progress, October 2004. EXTERNAL
- Savola, P., "IPv6 Multicast Deployment Issues" , Work in Progress, September 2004. EXTERNAL
- Farinacci, D. and Y. Cai, "Anycast-RP using PIM" , Work in Progress, June 2004. EXTERNAL
- Holbrook, H. et al, "Source-Specific Multicast for IP" , Work in Progress, September 2004. EXTERNAL
- Fenner, B., et al., "Bootstrap Router (BSR) Mechanism for PIM Sparse Mode", Work in Progress, July 2004. EXTERNAL
- Fenner, B. et al, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", Work in Progress, July 2004. EXTERNAL
- IETF RFC 3446 [Active*]
- IETF RFC 3618 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3956.json
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 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. Available at https://doi.org/10.17487/RFC3956
Snippet:
IETF RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. Available at https://doi.org/10.17487/RFC3956
HTML (ISO 690 compliant)
Preview:
IETF RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. Available at https://doi.org/10.17487/RFC3956
Snippet:
<span class="citation"><cite>IETF RFC 3956</cite>, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. Available at <a href="https://doi.org/10.17487/RFC3956" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3956</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address
doi: 10.17487/RFC3956
url: https://doi.org/10.17487/RFC3956
doi: 10.17487/RFC3956
url: https://doi.org/10.17487/RFC3956
Snippet:
<li> <cite id="bib-rfc3956">IETF RFC 3956</cite>, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address <span class="doi">10.17487/RFC3956</span> </li>
Referenced By
- IETF RFC 4038 [Active*]
- IETF RFC 4291 [Active*]
- IETF RFC 4601 [Superseded*]
- IETF RFC 6282 [Active*]
- IETF RFC 7761 [Active*]