STD 89, RFC 4443 on Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
rfc-editor@rfc-editor.org Fri, 14 July 2017 17:42 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 03B431317DD for <ietf-announce@ietfa.amsl.com>; Fri, 14 Jul 2017 10:42:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 DEGMAeQG8Bgv for <ietf-announce@ietfa.amsl.com>; Fri, 14 Jul 2017 10:42:25 -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 C6B0E131698 for <ietf-announce@ietf.org>; Fri, 14 Jul 2017 10:42:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 487B4B80D63; Fri, 14 Jul 2017 10:42:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: STD 89, RFC 4443 on Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
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
Message-Id: <20170714174213.487B4B80D63@rfc-editor.org>
Date: Fri, 14 Jul 2017 10:42:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/0BDUozNk_QL8E_nPuQqj5lhNDa0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 14 Jul 2017 17:42:27 -0000
RFC 4443 has been elevated to Internet Standard.
STD 89
RFC 4443
Title: Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6)
Specification
Author: A. Conta,
S. Deering,
M. Gupta, Ed.
Status: Standards Track
Stream: IETF
Date: March 2006
Pages: 24
Characters: 48969
Obsoletes: RFC 2463
Updates: RFC 2780
See Also: STD 89
I-D Tag: draft-ietf-ipngwg-icmp-v3-07.txt
URL: https://www.rfc-editor.org/info/rfc4443
DOI: 10.17487/RFC4443
This document describes the format of a set of control messages used
in ICMPv6 (Internet Control Message Protocol). ICMPv6 is the
Internet Control Message Protocol for Internet Protocol version 6
(IPv6).
This document is a product of the IP Version 6 Working Group of the IETF.
This is now an Internet 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