Echo Protocol
draft-yevstifeyev-rfc862bis-echo-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mykyta Yevstifeyev | ||
| Last updated | 2011-01-23 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)