RFC 8883 on ICMPv6 Errors for Discarding Packets Due to Processing Limits
rfc-editor@rfc-editor.org Thu, 24 September 2020 22:57 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F69F3A0A03; Thu, 24 Sep 2020 15:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ePOkAE6me_A4; Thu, 24 Sep 2020 15:57:05 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CFF93A0A00; Thu, 24 Sep 2020 15:57:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3309EF40756; Thu, 24 Sep 2020 15:56:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8883 on ICMPv6 Errors for Discarding Packets Due to Processing Limits
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipv6@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200924225655.3309EF40756@rfc-editor.org>
Date: Thu, 24 Sep 2020 15:56:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/bfwEKd6jcyrO2j38gR2FnTFlOxw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2020 22:57:07 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8883
Title: ICMPv6 Errors for Discarding Packets
Due to Processing Limits
Author: T. Herbert
Status: Standards Track
Stream: IETF
Date: September 2020
Mailbox: tom@quantonium.net
Pages: 15
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-6man-icmp-limits-08.txt
URL: https://www.rfc-editor.org/info/rfc8883
DOI: 10.17487/RFC8883
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
specification defines several new 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 use
the information to diagnose packet loss and may modify what it sends
in future packets to avoid subsequent packet discards.
This document is a product of the IPv6 Maintenance Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC