draft-ietf-ipngwg-icmp-v3-00.txt   draft-ietf-ipngwg-icmp-v3-01.txt 
INTERNET-DRAFT A. Conta, Lucent
INTERNET-DRAFT A. Conta, Transwitch
IPNG Working Group S. Deering, Cisco Systems IPNG Working Group S. Deering, Cisco Systems
Internet Control Message Protocol (ICMPv6) Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6) for the Internet Protocol Version 6 (IPv6)
Specification Specification
<draft-ietf-ipngwg-icmp-v3-00.txt> <draft-ietf-ipngwg-icmp-v3-01.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This internet draft will expire on January 19, 2002.
Abstract Abstract
This document specifies a set of Internet Control Message Protocol This document specifies a set of Internet Control Message Protocol
(ICMP) messages for use with version 6 of the Internet Protocol (ICMP) messages for use with version 6 of the Internet Protocol
(IPv6). (IPv6).
Table of Contents Table of Contents
1. Introduction........................................3 1. Introduction........................................3
skipping to change at page 15, line 49 skipping to change at page 15, line 49
Every node MUST implement an ICMPv6 Echo responder function that Every node MUST implement an ICMPv6 Echo responder function that
receives Echo Requests and sends corresponding Echo Replies. A node receives Echo Requests and sends corresponding Echo Replies. A node
SHOULD also implement an application-layer interface for sending Echo SHOULD also implement an application-layer interface for sending Echo
Requests and receiving Echo Replies, for diagnostic purposes. Requests and receiving Echo Replies, for diagnostic purposes.
The source address of an Echo Reply sent in response to a unicast 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 Echo Request message MUST be the same as the destination address of
that Echo Request message. that Echo Request message.
An Echo Reply SHOULD be sent in response to an Echo Request message 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 sent to an IPv6 multicast or anycast address. In this case, the
MUST be a unicast address belonging to the interface on which the source address of the reply MUST be a unicast address belonging to
multicast Echo Request message was received. the interface on which the Echo Request message was received.
The data received in the ICMPv6 Echo Request message MUST be returned The data received in the ICMPv6 Echo Request message MUST be returned
entirely and unmodified in the ICMPv6 Echo Reply message. entirely and unmodified in the ICMPv6 Echo Reply message.
Upper layer notification Upper layer notification
Echo Reply messages MUST be passed to the process that originated an Echo Reply messages MUST be passed to the process that originated an
Echo Request message. An Echo Reply message MAY be passed to Echo Request message. An Echo Reply message MAY be passed to
processes that did not originate the Echo Request message. processes that did not originate the Echo Request message.
skipping to change at page 20, line 5 skipping to change at page 19, line 47
7. Acknowledgments 7. Acknowledgments
The document is derived from previous ICMP drafts of the SIPP and The document is derived from previous ICMP drafts of the SIPP and
IPng working group. IPng working group.
The IPng working group and particularly Robert Elz, Jim Bound, Bill The IPng working group and particularly Robert Elz, Jim Bound, Bill
Simpson, Thomas Narten, Charlie Lynn, Bill Fink, Scott Bradner, Simpson, Thomas Narten, Charlie Lynn, Bill Fink, Scott Bradner,
Dimitri Haskin, and Bob Hinden (in chronological order) provided Dimitri Haskin, and Bob Hinden (in chronological order) provided
extensive review information and feedback. extensive review information and feedback.
Bob Hinden was the document editor for this document.
8. Authors' Addresses 8. Authors' Addresses
Alex Conta Stephen Deering Alex Conta Stephen Deering
Lucent Technologies Inc. Cisco Systems, Inc. Transwitch Corporation Cisco Systems, Inc.
300 Baker Ave, Suite 100 170 West Tasman Drive 3 Enterprise Drive 170 West Tasman Drive
Concord, MA 01742 San Jose, CA 95134-1706 Shelton, CT 06484 San Jose, CA 95134-1706
USA USA US US
phone: +1 978 287-2842 phone: +1 408 527-8213 phone: +1 408 527-8213
email: aconta@lucent.com email: deering@cisco.com email: aconta@txc.com email: deering@cisco.com
Appendix A - Changes from RFC 2463 Appendix A - Changes from RFC 2463
Version 3-00 The following changes were made from RFC 2463:
- Added "beyond scope of source address" message to the family of - Added "beyond scope of source address" message to the family of
"unreachable destination" type ICMP error messages (section 3.1). "unreachable destination" type ICMP error messages (section 3.1).
- Added a NOTE in section 2.4, that specifies ICMP message - Added a NOTE in section 2.4, that specifies ICMP message
processing rules precedence. processing rules precedence.
- Added ICMP REDIRECT to the list in Section 2.4 e) of cases in - Added ICMP REDIRECT to the list in Section 2.4 e) of cases in
which ICMP error messages are not to be generated. which ICMP error messages are not to be generated.
- Made minor editorial changes in Section 2.3 on checksum - Made minor editorial changes in Section 2.3 on checksum
calculation, and in Section 5.2. calculation, and in Section 5.2.
- Clarified in section 4.2, regarding the Echo Reply Message, that
the source address of an Echo Reply to an anycast Echo Request
should be a unicast address, as is the case of multicast.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/