Guidelines for the Definition of New Top Level Media Types
draft-duerst-mediaman-toplevel-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin J. Dürst | ||
| Last updated | 2022-03-06 | ||
| Replaced by | draft-ietf-mediaman-toplevel | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-mediaman-toplevel | |
| 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
The goal of this document is to identify best practices for defining new top-level media types. It updates RFC 6838 [RFC6838], when approved. Comments and discussion about this document should be directed to media-types@ietf.org, the mailing list of the Media Type Maintenance (mediaman) WG.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)