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

A new Request for Comments is now available in online RFC libraries.

        RFC 3956

        Title:      Embedding the Rendezvous Point (RP) Address
                    in an IPv6 Multicast Address
        Author(s):  P. Savola, B. Haberman
        Status:     Standards Track
        Date:       November 2004
        Mailbox:    psavola@funet.fi, brian@innovationslab.net
        Pages:      18
        Characters: 40136
        Updates:    3306

        I-D Tag:    draft-ietf-mboned-embeddedrp-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3956.txt

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.

This document is a product of the MBONE Deployment Working Group of
the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.