idnits 2.17.1 draft-ietf-magma-igmp-iana-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 BCP 57 4 RFC 3228 6 Title: IANA Considerations for IPv4 7 Internet Group Management Protocol (IGMP) 8 Author(s): B. Fenner 9 Status: Best Current Practice 10 Date: February 2002 11 Mailbox: fenner@research.att.com 12 Pages: 4 13 Characters: 6473 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-magma-igmp-iana-01.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3228.txt 20 This memo requests that the IANA create a registry for fields in the 21 IGMP (Internet Group Management Protocol) protocol header, and 22 provides guidance for the IANA to use in assigning parameters for 23 those fields. 25 This document is a product of the Multicast & Anycast Group Membership 26 Working Group of the IETF. 28 This document specifies an Internet Best Current Practices for the 29 Internet Community, and requests discussion and suggestions for 30 improvements. Distribution of this memo is unlimited. 32 This announcement is sent to the IETF list and the RFC-DIST list. 33 Requests to be added to or deleted from the IETF distribution list 34 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 35 added to or deleted from the RFC-DIST distribution list should 36 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 38 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 39 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 40 help: ways_to_get_rfcs. For example: 42 To: rfc-info@RFC-EDITOR.ORG 43 Subject: getting rfcs 45 help: ways_to_get_rfcs 47 Requests for special distribution should be addressed to either the 48 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 49 specifically noted otherwise on the RFC itself, all RFCs are for 50 unlimited distribution.echo 51 Submissions for Requests for Comments should be sent to 52 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 53 Authors, for further information.