RFC 2075: IP Echo Host Service
In plain English — editorial summary, not part of the RFC
This memo describes how to implement an IP echo host. IP echo hosts send back IP datagrams after exchanging the source and destination IP addresses. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC2075
- Published
- January 1997
- Authors
- C. Partridge
- Status
- EXPERIMENTAL
- Stream
- Legacy
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2098Toshiba's Router Architecture Extensions for ATM : OverviewCurrent
February 1997
- RFC 2391Load Sharing using IP Network Address Translation (LSNAT)Current
August 1998
- RFC 2147TCP and UDP over IPv6 JumbogramsObsoleted
May 1997
- RFC 2393IP Payload Compression Protocol (IPComp)Obsoleted
December 1998
- RFC 2394IP Payload Compression Using DEFLATECurrent
December 1998
- RFC 2395IP Payload Compression Using LZSCurrent
December 1998
- RFC 3096Requirements for robust IP/UDP/RTP header compressionCurrent
July 2001
- RFC 3243RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP CompressionCurrent
April 2002
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?