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