CurrentPROPOSED STANDARDIETF stream

RFC 4610: Anycast-RP Using Protocol Independent Multicast (PIM)

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

This specification allows Anycast-RP (Rendezvous Point) to be used inside a domain that runs Protocol Independent Multicast (PIM) only. Other multicast protocols (such as Multicast Source Discovery Protocol (MSDP), which has been used traditionally to solve this problem) are not required to support Anycast-RP. [STANDARDS-TRACK]

Document record

Document ID
RFC4610
Published
August 2006
Authors
D. Farinacci; Y. Cai
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
12
Also known as

Topics

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/4610-anycast-rp-using-protocol-independent-multicast-pim