EXI Messaging Requirements
draft-doi-exi-messaging-requirements-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yusuke Doi | ||
| Last updated | 2013-08-28 (Latest revision 2013-02-24) | ||
| 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
EXI (Efficient XML Interchange) is a specification on efficient encoding of XML. EXI is useful if an application requires XML based message exchange but no sufficient resource is available. However, schema-informed mode of EXI needs some out-of-band coordination between communicating nodes. This document discusses requirement on use of schema-informed EXI as a message exchange format on the Internet systems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)