Extensible Protocol
draft-harding-extensible-protocol-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tom Harding | ||
| Last updated | 1999-02-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 memo defines the Extensible Protocol (XP). XP is a generic application-level protocol meant to serve as the foundation for specific protocols, in a manner analogous to the way in which the Extensible Markup Language (XML) recommendation of the World Wide Web Consortium serves as the foundation for specific markup languages. XP is a bidirectional protocol on which XML documents are exchanged between two endpoints.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)