metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3956: Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address

Still current, but amended. Parts of this document are changed or extended by RFC 7371. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC3956
Published
November 2004
Authors
P. Savola; B. Haberman
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
18
Also known as
—
Updates:
RFC 3306
Updated by:
RFC 7371

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3956-embedding-the-rendezvous-point-rp-address-in-an-ipv6-multicast-address