BCP 57, RFC 3228 on IANA Considerations for IPv4 IGMP
RFC Editor <rfc-ed@ISI.EDU> Wed, 13 February 2002 01:20 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02487; Tue, 12 Feb 2002 20:20:53 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA01168 for ietf-123-outbound.10@ietf.org; Tue, 12 Feb 2002 20:15:02 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA00913 for <all-ietf@loki.ietf.org>; Tue, 12 Feb 2002 19:36:41 -0500 (EST)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01632 for <all-ietf@ietf.org>; Tue, 12 Feb 2002 19:36:38 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g1D0acR18725; Tue, 12 Feb 2002 16:36:38 -0800 (PST)
Message-Id: <200202130036.g1D0acR18725@gamma.isi.edu>
To: IETF-Announce:;
Subject: BCP 57, RFC 3228 on IANA Considerations for IPv4 IGMP
Cc: rfc-ed@ISI.EDU, magma@innovationslab.net.cnri.reston.va
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 12 Feb 2002 16:36:38 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
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 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.