RFC - 4884

Extended ICMP to Support Multi-Part Messages

Original:	ftp://ftp.isi.edu/in-notes/rfc4884.txt
Authors:	R. Bonica [Juniper Networks], D. Gan [Consultant], D. Tappan [Consultant], C. Pignataro [Cisco Systems, Inc.]
Date:	April 2007
Category:	Proposed Standard

---

Updates:
RFC-4443draft	Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification (Updated by RFC-4884prop)
RFC-792std5 [STD 5]	Internet Control Message Protocol (Updated by RFC-4884prop, RFC-950std5)

Referred by:	0 RFC
Refers to:	7 RFC

---

Status

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The IETF Trust (2007).

Abstract

This document redefines selected ICMP messages to support multi-part operation. A multi-part ICMP message carries all of the information that ICMP messages carried previously, as well as additional information that applications may require.

Multi-part messages are supported by an ICMP extension structure. The extension structure is situated at the end of the ICMP message. It includes an extension header followed by one or more extension objects. Each extension object contains an object header and object payload. All object headers share a common format.

This document further redefines the above mentioned ICMP messages by specifying a length attribute. All of the currently defined ICMP messages to which an extension structure can be appended include an "original datagram" field. The "original datagram" field contains the initial octets of the datagram that elicited the ICMP error message. Although the original datagram field is of variable length, the ICMP message does not include a field that specifies its length. Therefore, in order to facilitate message parsing, this document allocates eight previously reserved bits to reflect the length of the "original datagram" field.

The proposed modifications change the requirements for ICMP compliance. The impact of these changes on compliant implementations is discussed, and new requirements for future implementations are presented.

This memo updates RFC 792 and RFC 4443.

---