INTERNET-DRAFT M. Yevstifeyev Intended Status: Standards Track January 24, 2011 Obsoletes: 347, 862 (if approved) Expires: July 28, 2011 Echo Protocol Abstract This document specifies Echo protocol, that was firstly defined in RFC 862. However that document does not match current Internet Standards and specifies Echo protocol for TCP and UDP only, while a number of other transport-layer protocols have appeared since the time of publication of RFC 862. This document aligns Echo protocol specification with the current Internet Standards and specifies Echo protocol for the most wide- spread transport-layer protocols. It obsoletes RFC 347 and RFC 862 and moves the last to Historic status. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. 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. Internet-Drafts are draft documents valid for a maximum of six months 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/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright and License Notice Copyright (c) 2011 IETF Trust and the persons identified as the Yevstifeyev Expires July 28, 2011 [Page 1] INTERNET DRAFT Echo Protocol January 24, 2011 document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2. Protocol Specification . . . . . . . . . . . . . . . . . . . . 4 2.1. DCCP Based Echo Protocol . . . . . . . . . . . . . . . . . 4 2.2. SCTP Based Echo Protocol . . . . . . . . . . . . . . . . . 4 2.3. TCP Based Echo Protocol . . . . . . . . . . . . . . . . . . 4 2.4. UDP and UDP-Lite Based Echo Protocol . . . . . . . . . . . 4 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 4. RFC Editor Considerations . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Yevstifeyev Expires July 28, 2011 [Page 2] INTERNET DRAFT Echo Protocol January 24, 2011 1. Introduction The Echo protocol is a very useful debugging and measurement tool. The echo service simply sends back to the originating source any data it receives. The first proposal of Echo protocol appeared in RFC 347 [RFC347]. Echo protocol itself was specified in RFC 862 [RFC862]. However this document does not match current Internet Standards and specifies Echo protocol only for TCP [RFC793] and UDP [RFC768], while a number of other transport-layer protocols appeared since the time of publication of RFC 862. This document aligns the Echo protocol specification with current Internet Standards and specifies Echo protocol for the most wide-spread transport-layer protocols. It obsoletes RFC 347 [RFC347] and RFC 862 [RFC862] and moves the last to Historic status [RFC2026]. 1.1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Yevstifeyev Expires July 28, 2011 [Page 3] INTERNET DRAFT Echo Protocol January 24, 2011 2. Protocol Specification 2.1. DCCP Based Echo Protocol The Echo protocol supports DCCP [RFC4340] as a lower-layer protocol. If this protocol is used, one DCCP host listens for incoming connection on the port TBD1. Once a DCCP connection is established, any data received by this host SHALL be sent back. This continues until the DCCP connection is terminated. 2.2. SCTP Based Echo Protocol The Echo protocol supports SCTP [RFC4960] as a lower-layer protocol. If this protocol is used, one SCTP host listens for incoming connection on the port TBD2. Once a SCTP stream connection is established, any data received by this host SHALL be sent back. This continues until the SCTP connection is terminated. 2.3. TCP Based Echo Protocol The Echo protocol supports TCP [RFC793] as a lower-layer protocol. If this protocol is used, one TCP host listens for incoming connection on the port 7. Once a TCP connection is established, any data received by this host SHALL be sent back. This continues until the TCP connection is terminated. 2.4. UDP and UDP-Lite Based Echo Protocol The Echo protocol supports UDP [RFC768] and UDP-Lite [RFC3828] as lower-layer protocols. If these protocols are used, one host listens for UDP or UDP-Lite datagrams on the port 7. When a datagram is received, the data from it SHALL be sent back in an answering datagram. In the case, when UDP-Lite is used, the checksum MUST cover all the packet. Yevstifeyev Expires July 28, 2011 [Page 4] INTERNET DRAFT Echo Protocol January 24, 2011 3. Security Considerations The Echo protocol is used for debugging purposes and is not believed to cause any changes to the security of the Internet. 4. RFC Editor Considerations RFC Editor is asked to mark the following documents as obsoleted by this RFC: RFC 347 [RFC347] RFC 862 [RFC862] RFC Editor is also asked to mark RFC 862 [RFC862] as Historic RFC. 5. IANA Considerations IANA has assigned the DCCP port number TBD1 for use with Echo protocol. IANA has assigned the SCTP port number TBD2 for use with Echo protocol. IANA has assigned the TCP port number 7 for use with Echo protocol. IANA has assigned the UDP port number 7 for use with Echo protocol. 6. References 6.1. Normative References [RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980. [RFC793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981. [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3828] Larzon, L-A., Degermark, M., Pink, S., Jonsson, L-E., Ed., and G. Fairhurst, Ed., "The Lightweight User Datagram Protocol (UDP-Lite)", RFC 3828, July 2004. Yevstifeyev Expires July 28, 2011 [Page 5] INTERNET DRAFT Echo Protocol January 24, 2011 [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram Congestion Control Protocol (DCCP)", RFC 4340, March 2006. [RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol", RFC 4960, September 2007. 6.2. Informative References [RFC347] Postel, J., "Echo process", RFC 347, May 1972. [RFC862] Postel, J., "Echo Protocol", STD 20, RFC 862, May 1983. [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. Acknowledgments This documents is heavily based on RFC 862, whose author - Jon Postel - is cordially acknowledged. Author's Addresses Mykyta Yevstifeyev 8 Kuzovkov St., flat 25, Kotovsk, Ukraine EMail: evnikita2@gmail.com Yevstifeyev Expires July 28, 2011 [Page 6]