The +exi Media Type Suffix
draft-shelby-exi-registration-02
|
| Document |
Type |
|
Active Internet-Draft (individual in art area)
|
|
Last updated |
|
2017-03-14
(latest revision 2017-02-27)
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
AD is watching
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alexey Melnikov
|
|
Send notices to |
|
(None)
|
Appsawg Z. Shelby
Internet-Draft Micro:bit Foundation
Intended status: Informational O. Bergmann
Expires: August 26, 2017 C. Bormann
Universitaet Bremen TZI
February 22, 2017
The +exi Media Type Suffix
draft-shelby-exi-registration-02
Abstract
Efficient XML Interchange (EXI) is an XML representation technique
specified by the W3C to provide a time and space efficient encoding
for XML documents. This document defines a new Structured Syntax
Suffix "+exi" for use in a specific class of protocols, where "exi"
content-type encoding or the generic "application/exi" media type are
not applicable.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 26, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Shelby, et al. Expires August 26, 2017 [Page 1]
Internet-Draft +exi February 2017
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. When to Use the +exi Suffix . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
Efficient XML Interchange (EXI) [W3C.REC-exi-20140211] is an XML
representation technique specified by the W3C to provide a time and
space efficient binary encoding alternative to the standard text XML
representation. EXI is not a generic compression technique like gzip
or deflate, but an encoding technique specifically for XML structured
documents, which uses either learned or pre-informed schema
information.
[W3C.REC-exi-20140211] defines a generic media type for documents
encoded in EXI, "application/exi"; this does not provide a way to
indicate more information about structure and semantics of the EXI-
encoded XML. Also, [W3C.REC-exi-20140211] defines an HTTP content
encoding, "exi", that can be used to indicate EXI coding in
combination with an existing XML media type.
This document defines a new Structured Syntax Suffix "+exi" for use
in media types for a specific class of protocols, where the "exi"
content-type encoding or the generic "application/exi" media type are
not viable. In particular, the Constrained Application Protocol
(CoAP) [RFC7252] combines the media type and its encoding in a single
option value. Thus, a client would include an _Accept_ option in a
"GET" request to indicate its capability of processing, e.g., "text/
plain" in UTF-8 encoding, or "application/exi", while the actual
media type and encoding of a transferred payload would be described
Show full document text