[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RFC 3618 on Multicast Source Discovery Protocol (MSDP)




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


        RFC 3618

        Title:      Multicast Source Discovery Protocol (MSDP)
        Author(s):  B. Fenner, Ed., D. Meyer, Ed.
        Status:     Experimental
        Date:       October 2003
        Mailbox:    fenner@research.att.com, dmm@1-4-5.net
        Pages:      19
        Characters: 42238
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-msdp-spec-20.txt

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


The Multicast Source Discovery Protocol (MSDP) describes a mechanism
to connect multiple IP Version 4 Protocol Independent Multicast
Sparse-Mode (PIM-SM) domains together.  Each PIM-SM domain
uses its own independent Rendezvous Point (RP) and does not have to
depend on RPs in other domains.  This document reflects existing MSDP
implementations.

This document is a product of the Multicast Source Discovery Protocol
Working Group of the IETF.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  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.


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.
<ftp://ftp.isi.edu/in-notes/rfc3618.txt>