UMF - The Universal Message Format
draft-cordell-mmusic-umf-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Peter Cordell | ||
| Last updated | 2001-05-30 | ||
| 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
A number of methods and tools are available for defining the format of messages used for signalling protocols. However, many of these methods and tools have been designed for purposes other than message definition, and have been adopted on the basis that they are readily available rather than being ideally suited to the task. This often means that the methods make it difficult to get definitions correct, or result in unnecessary verbosity both in the definition and on the wire. UMF - the Universal Message Format - has been custom designed for the purpose of message definition. It is thus easy to specify messages in a compact, extensible format that is readily machine manipulated to produce a compact encoding on the wire.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)