[Search] [pdf|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 rfc3171                   Best Current Practice
A new Request for Comments is now available in online RFC libraries.


        BCP 51
        RFC 3171

        Title:      IANA Guidelines for IPv4 Multicast Address
                    Assignments
        Author(s):  Z. Albanna, K. Almeroth, D. Meyer, M. Schipper
        Status:     Best Current Practice
        Date:       August 2001
        Mailbox:    zaid@juniper.net, almeroth@cs.ucsb.edu,
                    dmm@sprint.net, iana@iana.org
        Pages:      8
        Characters: 15389
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-mboned-iana-ipv4-mcast-guidelines-04.txt

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


This memo provides guidance for the Internet Assigned Numbers
Authority (IANA) in assigning IPv4 multicast addresses.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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.