One document matched: draft-ietf-idmr-pim-sm-specv2-00.txt

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


        RFC 2362:

        Title:      Protocol Independent Multicast-Sparse Mode
		    (PIM-SM): Protocol Specification
	Author(s):  D.  Estrin, D. Farinacci, A. Helmy, D. Thaler, 
		    S. Deering, M. Handley, V. Jacobson, C. Liu,
		    P. Sharma, L. Wei
	Status:     Experimental
	Date:       June 1998
        Mailbox:    estrin@usc.edu, dino@cisco.com,
		    ahelmy@catarina.usc.edu,
		    thalerd@eecs.umich.edu, deering@parc.xerox.com,
		    m.handley@cs.ucl.ac.uk, van@ee.lbl.gov, 
		    charley@catarina.usc.edu, puneet@catarina.usc.edu,
		    lwei@cisco.com
	Pages:      66
        Characters: 159833 
        Obsoletes:  2117


        URL:        ftp://ftp.isi.edu/in-notes/rfc2362.txt


This document describes a protocol for efficiently routing to
multicast groups that may span wide-area (and inter-domain) internets.
We refer to the approach as Protocol Independent Multicast--Sparse
Mode (PIM-SM) because it is not dependent on any particular unicast
routing protocol, and because it is designed to support sparse groups.

This document is a product of the Inter-Domain Multicast Routing
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@ISI.EDU.

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

        To: rfc-info@ISI.EDU
        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@ISI.EDU.  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@ISI.EDU.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute