Browse Prior Art Database

IANA Considerations for IPv4 Internet Group Management Protocol (IGMP) (RFC3228)

IP.com Disclosure Number: IPCOM000006951D
Original Publication Date: 2002-Feb-01
Included in the Prior Art Database: 2002-Feb-12
Document File: 5 page(s) / 7K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Fenner: AUTHOR

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 50% of the total text.

Network Working Group                                          B. Fenner

Request for Comments: 3228                                 AT&T Research

BCP: 57                                                    February 2002

Category: Best Current Practice

                        IANA Considerations for

             IPv4 Internet Group Management Protocol (IGMP)

Status of this Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   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.

Table of Contents

   1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . .   1

   2. IANA Considerations for fields in the IPv4 IGMP header. . . .   2

   3. Assignments for testing and experimentation . . . . . . . . .   2

   4. Security Considerations . . . . . . . . . . . . . . . . . . .   2

   5. Normative References. . . . . . . . . . . . . . . . . . . . .   2

   6. Informative References. . . . . . . . . . . . . . . . . . . .   3

   7. Author's Address. . . . . . . . . . . . . . . . . . . . . . .   3

   8. Full Copyright Statement. . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   This memo requests that the IANA create a registry for fields in the

   IGMP protocol header.

   The terms "Specification Required", "Expert Review", "IESG Approval",

   "IETF Consensus", and "Standards Action", are used in this memo to

   refer to the processes described in [2].

Fenner                   Best Current Practice                  [Page 1]

RFC 3228           IANA Considerations for IPv4 IGMP       February 2002

2.  IANA Considerations for fields in the IPv4 IGMP header

   The IPv4 IGMP header [1] contains the following fields that carry

   values assigned from IANA-managed name spaces: Type and Code.  Code

   field values are defined relative to a specific Type value.

   Values for the IPv4 IGMP Type fields are allocated using an IESG

   Approval or Standards Action processes.  Code Values for existing

   IPv4 IGMP Type fields are allocated using IESG Approval or Standards

   Action processes.  The policy for assigning Code values for new IPv4

   IGMP Types should be defined in the document defining the new Type

   value.

3.  Assignments for testing and experimentation

   Instead of suggesting temporary assignments as in [3], this document

   follows the lead of [4] and assigns a range of values for

   experimental use.  The IGMP Code values 240-255 inclusive (0xf0 -

   0xff) are reserved for protocol testing and experimentation.

   Systems should silently ignore IGMP messages with unknown Code

   values.

4.  Security Considerations

   Security analyzers such as firewalls and network intrusion detection

   monitors often rely on unambiguous interpretations of the fields

   described in this memo.  As new values for the fields...