RFC 3973 on Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)

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

 



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


        RFC 3973

        Title:      Protocol Independent Multicast - Dense Mode
                    (PIM-DM): Protocol Specification (Revised)
        Author(s):  A. Adams, J. Nicholas, W. Siadak
        Status:     Experimental
        Date:       January 2005
        Mailbox:    ala@nexthop.com, jonathan.nicholas@itt.com,
                    wfs@nexthop.com
        Pages:      61
        Characters: 136708
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-pim-dm-new-v2-05.txt

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


This document specifies Protocol Independent Multicast - Dense Mode
(PIM-DM).  PIM-DM is a multicast routing protocol that uses the
underlying unicast routing information base to flood multicast
datagrams to all multicast routers.  Prune messages are used to
prevent future messages from propagating to routers without group
membership information.

This document is a product of the Protocol Independent Multicast
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.

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/rfc3973.txt>
_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux