RFC 1885
Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)
1. Introduction 🎀
RFC 1885: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification 💖
- Network Working Group 💜 Request for Comments: 1885
- Authors: A. Conta, Digital Equipment Corporation, and S. Deering, Xerox PARC 🫶
- Category: Standards Track ✨
- Date: December 1995 📅
- Obsoletes / Updates: nothing is listed in this header 🙈
Status of this Memo ✨
Okay so this doc is an Internet standards track protocol for the Internet community, and it's literally asking for discussion and suggestions for improvements 🔥. If you want the standardization state and status, check the current edition of the "Internet Official Protocol Standards" (STD 1) 📚. Distribution of this memo is unlimited 🌈.
Abstract 🌸
This doc lays out a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6) 🧚. The Internet Group Management Protocol (IGMP) messages specified in STD 5, RFC 1112 have been merged into ICMP, for IPv6, and they're included right here 💅.
Table of Contents 📚
1. Introduction........................................3
2. ICMPv6 (ICMP for IPv6)..............................3
2.1 Message General Format.......................3
2.2 Message Source Address Determination.........4
2.3 Message Checksum Calculation.................5
2.4 Message Processing Rules.....................5
3. ICMPv6 Error Messages...............................8
3.1 Destination Unreachable Message..............8
3.2 Packet Too Big Message......................10
3.3 Time Exceeded Message.......................11
3.4 Parameter Problem Message...................12
4. ICMPv6 Informational Messages......................14
4.1 Echo Request Message........................14
4.2 Echo Reply Message..........................15
4.3 Group Membership Messages...................17
5. References.........................................19
6. Acknowledgements...................................19
7. Security Considerations............................19
Authors' Addresses....................................201. Introduction 🦋
Okay so, IPv6 is a brand new version of IP 💖. It uses the Internet Control Message Protocol (ICMP) as defined for IPv4 [RFC-792], but with a bunch of changes ✨. The Internet Group Membership Protocol (IGMP) specified for IPv4 [RFC-1112] also got a glow-up: it's been revised and absorbed into ICMP for IPv6 🫶. The result is called ICMPv6, and it has an IPv6 Next Header value of 58 👑.
This doc describes the format of a set of control messages used in ICMPv6 📝. It does not walk through the procedures for using these messages to do things like Path MTU discovery or multicast group membership maintenance 🙈. Those procedures live in other documents (e.g., [RFC-1112, RFC-1191]). Other documents may also introduce extra ICMPv6 message types, like Neighbor Discovery messages [IPv6-DISC], as long as they follow the general rules for ICMPv6 messages given in section 2 of this document 🧚.
Terminology defined in the IPv6 specification [IPv6] and the IPv6 Routing and Addressing specification [IPv6-ADDR] applies to this document too 💅.
2. ICMPv6 (ICMP for IPv6) 💜
ICMPv6 is how IPv6 nodes report errors they run into while processing packets 🚨. It also handles other internet-layer jobs, like diagnostics (ICMPv6 "ping") and multicast membership reporting 🌸. ICMPv6 is an integral part of IPv6, so it MUST be fully implemented by every IPv6 node 🔥.
2.1 Message General Format 🎀
ICMPv6 messages come in two classes: error messages and informational messages 💖. Error messages are identified by having a zero in the high-order bit of their message Type field values. So error messages have message Types from 0 to 127, and informational messages have message Types from 128 to 255 ✨.
This document defines the message formats for the following ICMPv6 messages:
ICMPv6 error messages:
1 Destination Unreachable (see section 3.1)
2 Packet Too Big (see section 3.2)
3 Time Exceeded (see section 3.3)
4 Parameter Problem (see section 3.4)
ICMPv6 informational messages:
128 Echo Request (see section 4.1)
129 Echo Reply (see section 4.2)
130 Group Membership Query (see section 4.3)
131 Group Membership Report (see section 4.3)
132 Group Membership Reduction (see section 4.3)Every ICMPv6 message is preceded by an IPv6 header and zero or more IPv6 extension headers 🧸. The ICMPv6 header is identified by a Next Header value of 58 in the header right before it 🫶. (NOTE: this is different from the value used to identify ICMP for IPv4 👀.)
The ICMPv6 messages have the following general format 📐:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Message Body +
| |The type field tells you what kind of message it is. Its value decides the format of the rest of the data 💅.
The code field depends on the message type. It adds an extra level of message granularity 🍓.
The checksum field is there to detect data corruption in the ICMPv6 message and in parts of the IPv6 header 🔍.
2.2 Message Source Address Determination 🧚
Okay this one matters, bestie. A node that sends an ICMPv6 message has to figure out both the Source and Destination IPv6 Addresses in the IPv6 header before it calculates the checksum 🧮. If the node has more than one unicast address, it must choose the Source Address of the message like this 👑:
- (a) If the message is a response to a message sent to one of the node's unicast addresses, the Source Address of the reply must be that same address 💖.
- (b) If the message is a response to a message sent to a multicast or anycast group the node is a member of, the Source Address of the reply must be a unicast address belonging to the interface on which the multicast or anycast packet was received 🦋.
- (c) If the message is a response to a message sent to an address that doesn't belong to the node, the Source Address should be that unicast address belonging to the node that will be most helpful in diagnosing the error 🔎. For example, if the message is a response to a packet forwarding action that cannot complete successfully, the Source Address should be a unicast address belonging to the interface on which the packet forwarding failed 🙈.
- (d) Otherwise, the node's routing table must be examined to determine which interface will be used to transmit the message to its destination, and a unicast address belonging to that interface must be used as the Source Address of the message 🗺️.
2.3 Message Checksum Calculation 🧮
The checksum is the 16-bit one's complement of the one's complement sum of the entire ICMPv6 message, starting with the ICMPv6 message type field 🍒. It gets prepended with a "pseudo-header" of IPv6 header fields, as specified in [IPv6, section 8.1] ✨. The Next Header value used in the pseudo-header is 58 💜. (NOTE: putting a pseudo-header into the ICMPv6 checksum is a change from IPv4. See [IPv6] for the rationale behind that change 🤓.)
For computing the checksum, the checksum field is set to zero 🫧.
2.4 Message Processing Rules 🔥
Implementations MUST observe the following rules when processing ICMPv6 messages (from [RFC-1122]) 📜:
- (a) If an ICMPv6 error message of unknown type is received, it MUST be passed to the upper layer 🚀.
- (b) If an ICMPv6 informational message of unknown type is received, it MUST be silently discarded 🤫.
- (c) Every ICMPv6 error message (type < 128) includes as much of the IPv6 offending (invoking) packet, the packet that caused the error, as will fit without making the error message packet exceed 576 octets 📦.
- (d) In cases where the internet-layer protocol is required to pass an ICMPv6 error message to the upper-layer protocol, the upper-layer protocol type is extracted from the original packet (contained in the body of the ICMPv6 error message). That type is then used to select the appropriate upper-layer protocol entity to handle the error 🎯.
If the original packet had an unusually large amount of extension headers, the upper-layer protocol type may not be present in the ICMPv6 message, because the original packet got truncated to meet the 576-octet limit 😭. In that case, the error message is silently dropped after any IPv6-layer processing 🫥.
- (e) An ICMPv6 error message MUST NOT be sent as a result of receiving:
- (e.1) an ICMPv6 error message, or
- (e.2) a packet destined to an IPv6 multicast address (there are two exceptions to this rule: (1) the Packet Too Big Message - Section 3.2 - to allow Path MTU discovery to work for IPv6 multicast, and (2) the Parameter Problem Message, Code 2 - Section 3.4 - reporting an unrecognized IPv6 option that has the Option Type highest-order two bits set to 10), or
- (e.3) a packet sent as a link-layer multicast (the exception from e.2 applies to this case too), or
- (e.4) a packet sent as a link-layer broadcast (the exception from e.2 applies to this case too), or
- (e.5) a packet whose source address does not uniquely identify a single node, e.g., the IPv6 Unspecified Address, an IPv6 multicast address, or an address known by the ICMP message sender to be an IPv6 anycast address 🚫.
- (f) Finally, to each sender of an erroneous data packet, an IPv6 node MUST limit the rate of ICMPv6 error messages it sends. This keeps the bandwidth and forwarding costs of those error messages in check when a generator of erroneous packets doesn't stop transmitting after getting the errors 🛑.
There are a variety of ways to implement the rate-limiting function, for example:
- (f.1) Timer-based, for example, limiting the rate of transmission of error messages to a given source, or to any source, to at most once every T milliseconds ⏱️.
- (f.2) Bandwidth-based, for example, limiting the rate at which error messages are sent from a particular interface to some fraction F of the attached link's bandwidth 📶.
The limit parameters (e.g., T or F in the above examples) MUST be configurable for the node, with a conservative default value (e.g., T = 1 second, not 0 seconds, or F = 2 percent, not 100 percent) 🎀.
The following sections describe the message formats for the above ICMPv6 messages 💅.
3. ICMPv6 Error Messages 🌈
3.1 Destination Unreachable Message ✨
okay bestie, this is the message a router (or the IPv6 layer on the originating node) sends back when it can't deliver a packet 💌 here's the layout:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unused |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| As much of invoking packet |
+ as will fit without the ICMPv6 packet +
| exceeding 576 octets |IPv6 Fields
Destination Address: copied from theSource Addressfield of the invoking packet 🫶
ICMPv6 Fields
Type:1🌸Code: tells you why the delivery failed 💅0- no route to destination1- communication with destination administratively prohibited2- not a neighbor3- address unreachable4- port unreachable
Unused: this field is unused for all code values. It must be initialized to zero by the sender and ignored by the receiver. 🫧
Description
okay so a Destination Unreachable message SHOULD be generated by a router, or by the IPv6 layer in the originating node, when a packet can't reach its destination address for reasons other than congestion 🚫 (and an ICMPv6 message MUST NOT be generated if a packet is dropped due to congestion, so don't even try 🙈)
if the failure is because the forwarding node has no matching entry in its routing table, the Code field is set to 0 (NOTE: this error can occur only in nodes that do not hold a "default route" in their routing tables) 🗺️
if the failure is administrative prohibition, like a "firewall filter", the Code field is set to 1 🔥
if the next destination address in the Routing header is not a neighbor of the processing node but the "strict" bit is set for that address, the Code field is set to 2 🧱
and if there's any other reason for the failure, like being unable to resolve the IPv6 destination address into a corresponding link address, or some link-specific problem, the Code field is set to 3 🌧️
a destination node SHOULD send a Destination Unreachable message with Code 4 in response to a packet for which the transport protocol (e.g., UDP) has no listener, if that transport protocol has no alternative means to inform the sender 🎯
Upper layer notification
a node receiving the ICMPv6 Destination Unreachable message MUST notify the upper-layer protocol 📣
3.2 Packet Too Big Message ✨
this one is the "that's too chunky for my link" message 🍓 here's the shape:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MTU |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| As much of invoking packet |
+ as will fit without the ICMPv6 packet +
| exceeding 576 octets |IPv6 Fields
Destination Address: copied from theSource Addressfield of the invoking packet 🫶
ICMPv6 Fields
Type:2🌸Code:0MTU: the Maximum Transmission Unit of the next-hop link 📏
Description
a Packet Too Big MUST be sent by a router in response to a packet it cannot forward because the packet is larger than the MTU of the outgoing link 🙅♀️ the info in this message gets used as part of the Path MTU Discovery process [RFC-1191] 🔍
sending a Packet Too Big Message is the main exception to the rules about when to send an ICMPv6 error message 👑 unlike the other messages, it's sent in response to a packet received with an IPv6 multicast destination address, or a link-layer multicast or link-layer broadcast address. main character energy, no notes 💅
Upper layer notification
an incoming Packet Too Big message MUST be passed to the upper-layer protocol 📬
3.3 Time Exceeded Message ✨
the "I ran out of hops" message ⏳ check the layout:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unused |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| As much of invoking packet |
+ as will fit without the ICMPv6 packet +
| exceeding 576 octets |IPv6 Fields
Destination Address: copied from theSource Addressfield of the invoking packet 🫶
ICMPv6 Fields
Type:3🌸Code:0- hop limit exceeded in transit,1- fragment reassembly time exceeded ⌛Unused: this field is unused for all code values. It must be initialized to zero by the sender and ignored by the receiver. 🫧
Description
if a router receives a packet with a Hop Limit of zero, or a router decrements a packet's Hop Limit to zero, it MUST discard the packet and send an ICMPv6 Time Exceeded message with Code 0 to the source of the packet 🗑️ this points to either a routing loop or too small an initial Hop Limit value, so it's a whole vibe check 🔁
the router sending an ICMPv6 Time Exceeded message with Code 0 SHOULD consider the receiving interface of the packet as the interface on which the packet forwarding failed in following rule (d) for selecting the Source Address of the message 🧭
Upper layer notification
an incoming Time Exceeded message MUST be passed to the upper-layer protocol 📨
3.4 Parameter Problem Message ✨
this is the "something in your header is sus" message 🕵️♀️ here's the layout:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Pointer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| As much of invoking packet |
+ as will fit without the ICMPv6 packet +
| exceeding 576 octets |IPv6 Fields
Destination Address: copied from theSource Addressfield of the invoking packet 🫶
ICMPv6 Fields
Type:4🌸Code:0- erroneous header field encountered1- unrecognized Next Header type encountered2- unrecognized IPv6 option encountered
Pointer: identifies the octet offset within the invoking packet where the error was detected 📍
the pointer will point beyond the end of the ICMPv6 packet if the field in error is beyond what can fit in the 576-byte limit of an ICMPv6 error message 🫣
Description
if an IPv6 node processing a packet finds a problem with a field in the IPv6 header or extension headers so that it can't finish processing the packet, it MUST discard the packet and SHOULD send an ICMPv6 Parameter Problem message to the packet's source, indicating the type and location of the problem 🚨
the pointer identifies the octet of the original packet's header where the error was detected. for example, an ICMPv6 message with Type field = 4, Code field = 1, and Pointer field = 40 would indicate that the IPv6 extension header following the IPv6 header of the original packet holds an unrecognized Next Header field value 🧩
Upper layer notification
a node receiving this ICMPv6 message MUST notify the upper-layer protocol 🗣️
4. ICMPv6 Informational Messages 🧚
4.1 Echo Request Message ✨
the classic "are you alive?" ping 🏓 check the shape:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data ...
+-+-+-+-+-IPv6 Fields
Destination Address: any legal IPv6 address 🌐
ICMPv6 Fields
Type:128🌸Code:0Identifier: an identifier to aid in matching Echo Replies to this Echo Request. may be zero 🪪Sequence Number: a sequence number to aid in matching Echo Replies to this Echo Request. may be zero 🔢Data: zero or more octets of arbitrary data 🎁
Description
every node MUST implement an ICMPv6 Echo responder function that receives Echo Requests and sends corresponding Echo Replies. that's non-negotiable, bestie 🫶 a node SHOULD also implement an application-layer interface for sending Echo Requests and receiving Echo Replies, for diagnostic purposes 🩺
Upper layer notification
a node receiving this ICMPv6 message MAY notify the upper-layer protocol 💜
4.2 Echo Reply Message 🦋
okay so the Echo Reply is literally the "yes bestie, I'm here!" answer to an Echo Request 💖 here's the layout:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data ...
+-+-+-+-+-IPv6 Fields:
Destination Address: copied from the Source Address field of the invoking Echo Request packet. 🎀
ICMPv6 Fields:
Type:129✨Code:0Identifier: the identifier from the invoking Echo Request message.Sequence Number: the sequence number from the invoking Echo Request message.Data: the data from the invoking Echo Request message.
Description 💅
okay so every node MUST implement an ICMPv6 Echo responder function that receives Echo Requests and sends the matching Echo Replies, no exceptions bestie 🫶 and a node SHOULD also implement an application-layer interface for sending Echo Requests and receiving Echo Replies, for diagnostic purposes. it's giving troubleshooting glow-up 🔥
the source address of an Echo Reply sent in response to a unicast Echo Request message MUST be the same as the destination address of that Echo Request message. main character energy, the reply always comes back from the address that was pinged 🦋
an Echo Reply SHOULD be sent in response to an Echo Request message sent to an IPv6 multicast address. the source address of the reply MUST be a unicast address belonging to the interface on which the multicast Echo Request message was received. the reply has to come from a unicast address that lives on the interface where the multicast request came in 💜
the data received in the ICMPv6 Echo Request message MUST be returned entirely and unmodified in the ICMPv6 Echo Reply message, unless the Echo Reply would exceed the MTU of the path back to the Echo requester, in which case the data is truncated to fit that path MTU. so the payload gets handed back exactly as it arrived, unless it's too big for the path back, then it gets trimmed to fit 🍓
Upper layer notification 🌸
Echo Reply messages MUST be passed to the ICMPv6 user interface, unless the corresponding Echo Request originated in the IP layer. iykyk 🙈
4.3 Group Membership Messages 🌈
okay the Group Membership messages are where the vibes get a little more organised ✨ these ones have this format:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum Response Delay | Unused |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| Multicast |
+ +
| Address |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+IPv6 Fields:
Destination Address: in a Group Membership Query message, the multicast address of the group being queried, or the Link-Local All-Nodes multicast address. 💖Destination Address: in a Group Membership Report or a Group Membership Reduction message, the multicast address of the group being reported or terminated.Hop Limit:1
ICMPv6 Fields:
Type:130(Group Membership Query),131(Group Membership Report),132(Group Membership Reduction) 🦋Code:0Maximum Response Delay: in Query messages, the maximum time that responding Report messages may be delayed, in milliseconds. in Report and Reduction messages, this field is initialized to zero by the sender and ignored by receivers.Unused: initialized to zero by the sender; ignored by receivers.Multicast Address: the address of the multicast group about which the message is being sent. in Query messages, the Multicast Address field may be zero, implying a query for all groups. 🧚
Description 💅
the Group Membership messages are how nodes tell their neighbouring routers what multicast groups they're in, lowkey the group chat update of the internet 🫶 the details of how they get used are in [RFC-1112].
5. References 📚
- [IPv6] Deering, S., and R. Hinden, "Internet Protocol, Version 6, Specification", RFC 1883, Xerox PARC, Ipsilon Networks, December 1995.
- [IPv6-ADDR] Hinden, R., and S. Deering, Editors, "IP Version 6 Addressing Architecture", RFC 1884, Ipsilon Networks, Xerox PARC, December 1995.
- [IPv6-DISC] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", Work in Progress.
- [RFC-792] Postel, J., "Internet Control Message Protocol", STD 5, RFC 792, USC/Information Sciences Institute, September 1981.
- [RFC-1112] Deering, S., "Host Extensions for IP Multicasting", STD 5, RFC 1112, Stanford University, August 1989.
- [RFC-1122] Braden, R., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, USC/Information Sciences Institute, October 1989.
- [RFC-1191] Mogul, J., and S. Deering, "Path MTU Discovery", RFC 1191, DECWRL, Stanford University, November 1990.
6. Acknowledgements 🫶
the document is derived from previous ICMP drafts of the SIPP and IPng working group ✨
the IPng working group, and especially Robert Elz, Jim Bound, Bill Simpson, Thomas Narten, Charlie Lynn, Bill Fink, and Scott Bradner (in chronological order), gave extensive review information and feedback. the real MVPs 👑
7. Security Considerations 💀
Security issues are not discussed in this memo.
Authors' Addresses 🎀
Alex Conta Stephen Deering
Digital Equipment Corporation Xerox Palo Alto Research Center
110 Spitbrook Rd 3333 Coyote Hill Road
Nashua, NH 03062 Palo Alto, CA 94304
Phone: +1-603-881-0744 Phone: +1-415-812-4839
EMail: conta@zk3.dec.com EMail: deering@parc.xerox.com📦 where this page comes from
- ietf: rfc1885 1995-12
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms