Requirements of Interoperable Messaging
draft-ralston-mimi-messaging-requirements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Travis Ralston | ||
| Last updated | 2023-09-14 (Latest revision 2023-03-13) | ||
| 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 set of requirements for messaging services to interoperate. These requirements are independent of any particular protocol or messaging service, describing the set of features an interoperable messaging service should support. Services should expect to go beyond the requirements listed here, as MIMI's future content format evolves.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)