RFC 3446: Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)
In plain English — editorial summary, not part of the RFC
This document describes a mechanism to allow for an arbitrary number of Rendevous Points (RPs) per group in a single shared-tree Protocol Independent Multicast-Sparse Mode (PIM-SM) domain. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3446
- Published
- January 2003
- Authors
- D. Kim; D. Meyer; H. Kilmer; D. Farinacci
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3440Definitions of Extension Managed Objects for Asymmetric Digital Subscriber LinesCurrent
January 2003
- RFC 3434Remote Monitoring MIB Extensions for High Capacity AlarmsCurrent
December 2002
- RFC 3433Entity Sensor Management Information BaseCurrent
December 2002
- RFC 3432Network performance measurement with periodic streamsCurrent
December 2002
- RFC 3460Policy Core Information Model (PCIM) ExtensionsCurrent
January 2003
- RFC 3418Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)Current
December 2002
- RFC 3417Transport Mappings for the Simple Network Management Protocol (SNMP)Updated
December 2002
- RFC 3416Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)Current
December 2002
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?