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

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

        BCP 57
        RFC 3228

        Title:      IANA Considerations for IPv4
                    Internet Group Management Protocol (IGMP)
        Author(s):  B. Fenner
        Status:     Best Current Practice
        Date:       February 2002
        Mailbox:    fenner@research.att.com
        Pages:      4
        Characters: 6473
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-magma-igmp-iana-01.txt

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

This memo requests that the IANA create a registry for fields in the
IGMP (Internet Group Management Protocol) protocol header, and
provides guidance for the IANA to use in assigning parameters for
those fields.

This document is a product of the Multicast & Anycast Group Membership
Working Group of the IETF.

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

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.