RFC 2463: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4443.
Current document in this lineage: RFC 4443 — Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
In plain English — editorial summary, not part of the RFC
This document specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). [STANDARDS-TRACK]
Document record
- Document ID
- RFC2463
- Published
- December 1998
- Authors
- A. Conta; S. Deering
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 18
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1885 (1995)
- RFC 2463 (1998)
- RFC 4443 (2006) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2464Transmission of IPv6 Packets over Ethernet NetworksUpdated
December 1998
- RFC 3146Transmission of IPv6 Packets over IEEE 1394 NetworksUpdated
October 2001
- RFC 2467Transmission of IPv6 Packets over FDDI NetworksUpdated
December 1998
- RFC 2470Transmission of IPv6 Packets over Token Ring NetworksUpdated
December 1998
- RFC 2529Transmission of IPv6 over IPv4 Domains without Explicit TunnelsCurrent
March 1999
- RFC 3831Transmission of IPv6 Packets over Fibre ChannelObsoleted
July 2004
- RFC 2462IPv6 Stateless Address AutoconfigurationObsoleted
December 1998
- RFC 2450Proposed TLA and NLA Assignment RuleCurrent
December 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?