Simple Protocol Application Data Encoding
draft-hudson-spade-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Greg Hudson | ||
| Last updated | 1999-09-01 | ||
| 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 describes a simple scheme for encoding network protocol data and a simple notation for describing protocol data elements. All encodings are self-terminating (you know when you've reached the end) and assume that the decoder knows what type of protocol element it is expecting.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)