RFC - 3956
Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address
| Original: | ftp://ftp.isi.edu/in-notes/rfc3956.txt |
|---|---|
| Authors: | P. Savola [CSC/FUNET], B. Haberman [JHU APL] |
| Date: | November 2004 |
| Category: | Proposed Standard |
| Updates: | |
|---|---|
| RFC-3306prop | Unicast-Prefix-based IPv6 Multicast Addresses (Updated by RFC-3956prop, RFC-4489prop) |
| Referred by: | 5 RFC |
| Refers to: | 5 RFC |
Status
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004).
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.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry