As per the discussion regarding an +exi suffix on this list, I wrote up a short draft describing the registration for such a suffix, when it would be applicable, and what the interoperability requirements are. I will send this to the CoRE list and to ZigBee SE2 for comments as well.
http://www.ietf.org/id/draft-shelby-exi-registration-00.txtZach
Begin forwarded message:
> From:
internet-drafts@...
> Date: March 5, 2012 11:43:30 AM GMT+02:00
> To:
zach@...
> Subject: New Version Notification for draft-shelby-exi-registration-00.txt
>
> A new version of I-D, draft-shelby-exi-registration-00.txt has been successfully submitted by Zach Shelby and posted to the IETF repository.
>
> Filename: draft-shelby-exi-registration
> Revision: 00
> Title: The +exi Media Type Suffix
> Creation date: 2012-03-05
> WG ID: Individual Submission
> Number of pages: 5
>
> Abstract:
> Efficient XML Interchange (EXI) is an XML representation technique
> specified by the W3C to provie a binary alternative to the standard
> text XML representation. This document defines a new Structure
> 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.
>
>
>
>
> The IETF Secretariat
--
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.comhttp://zachshelby.org - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297
_______________________________________________
apps-discuss mailing list
apps-discuss@...
https://www.ietf.org/mailman/listinfo/apps-discuss