ICMPv6 errors for discarding packets due to processing limits
draft-ietf-6man-icmp-limits-00
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8883.
Expired & archived
|
|
|---|---|---|---|
| Author | Tom Herbert | ||
| Last updated | 2018-11-30 (Latest revision 2018-05-29) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
TSVART Last Call review
(of
-07)
by Bernard Aboba
Ready w/issues
GENART Last Call review
(of
-07)
by Pete Resnick
Ready w/nits
OPSDIR Last Call Review due 2020-02-25
Incomplete
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Network nodes may discard packets if they are unable to process protocol headers of packets due to processing constraints or limits. When such packets are dropped, the sender receives no indication so it cannot take action to address the cause of discarded packets. This document defines ICMPv6 errors that can be sent by a node that discards packets because it is unable to process the protocol headers. A node that receives such an ICMPv6 error may be able to modify what it sends in future packets to avoid subsequent packet discards.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)