ICMP Extension Structure Length Field
draft-ietf-intarea-icmp-exten-hdr-len-08
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ron Bonica , hexiaoming , Xiao Min , Tal Mizrahi | ||
| Last updated | 2026-02-21 (Latest revision 2025-08-20) | ||
| Replaces | draft-bonica-intarea-icmp-exten-hdr-len | ||
| RFC stream | (None) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Reviews | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Yes | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | Éric Vyncke | ||
| Send notices to | ggx@gigix.net | ||
| IANA | IANA review state | Version Changed - Review Needed |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The ICMP Extension Structure (RFC4884) does not have a length field. Therefore, unless the length of the Extension Structure can be inferred from other data in the ICMP message, the Extension Structure must be the last item in the ICMP message. This document updates RFC 4884 to define a length field for the ICMP Extension Structure. When length information is provided, receivers can use it to parse ICMP messages. Specifically, receivers can use length information to determine the offset at which the item after the ICMP Extension Structure begins.
Authors
Ron Bonica
hexiaoming
Xiao Min
Tal Mizrahi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)