Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)
draft-ietf-mboned-anycast-rp-08

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3446.
Authors Hank Kilmer , David Meyer , Dorian R. Kim , Dino Farinacci
Last updated 2022-06-18 (Latest revision 2001-05-30)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
txt htmlized pdf bibtex bibxml
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Became RFC 3446 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Randy Bush
IESG note ** No value found for 'doc.notedoc.note' **
Send notices to <dmm@1-4-5.net>
Email authors Email WG IPR References Referenced by Nits Search email archive
draft-ietf-mboned-anycast-rp-08 
A new Request for Comments is now available in online RFC libraries.

        RFC 3446

        Title:      Anycast Rendevous Point (RP) mechanism using
                    Protocol Independent Multicast (PIM)
                    and Multicast Source Discovery Protocol (MSDP)
        Author(s):  D. Kim, D. Meyer, H. Kilmer, D. Farinacci
        Status:     Informational
        Date:       January 2003
        Mailbox:    dorian@blackrose.org, hank@rem.com,
                    dino@procket.com, dmm@maoz.com
        Pages:      7
        Characters: 14792
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mboned-anycast-rp-08.txt

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

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 document is a product of the MBONE Deployment Working Group of
the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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.echo 
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.