Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
 with ESMTP id 27FA721F85FF for <apps-discuss@ietfa.amsl.com>;
 Mon,  2 Apr 2012 08:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WWlQnLksJ2JA for
 <apps-discuss@ietfa.amsl.com>; Mon,  2 Apr 2012 08:08:40 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by
 ietfa.amsl.com (Postfix) with ESMTP id 4D9BE21F85EF for
 <apps-discuss@ietf.org>; Mon,  2 Apr 2012 08:08:33 -0700 (PDT)
Received: from [10.4.80.59] (unknown [74.205.24.231]) (using TLSv1 with cipher
 AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net
 (Postfix) with ESMTPSA id 33E2750A64; Mon,  2 Apr 2012 11:08:25 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=utf-8
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <201204020745.q327j8Rr014728@toshiba.co.jp>
Date: Mon, 2 Apr 2012 11:08:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A39CB179-C9AB-4B29-B775-25098F574223@mnot.net>
References: <20120329204732.13711.266.idtracker@ietfa.amsl.com>
 <5580A282-E191-4962-9410-6CF9FB14EDFC@sensinode.com>
 <0885CE0D-11A3-4396-9443-37B4FF8D36C9@mnot.net>
 <201204020745.q327j8Rr014728@toshiba.co.jp>
To: Yusuke DOI <yusuke.doi@toshiba.co.jp>
X-Mailer: Apple Mail (2.1257)
Cc: "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] New Version Notification for
 draft-shelby-exi-registration-01.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols
 <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>,
 <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>,
 <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2012 15:08:41 -0000

Potentially exploding the number of XML media types defined across the =
Web and in e-mail to save a few bytes in *one* use case seems like a =
poor trade-off to me.=20


On 02/04/2012, at 3:45 AM, Yusuke DOI wrote:

> Dear Mark,
>=20
> I have a following use case.
>=20
> As EXI is expected to be used in constrained environments, we want to =
make it as short as possible. With application+exi content-type, we can =
make sure the field is under the application's convention; schemaId '1' =
may mean the version 1 of a schema for the application, and so on.
>=20
> In other words, this kind of content-type definition (application + =
encoding) can imply the format of schemaId field used in the =
application. And this helps 'option/encoding negotiation' of EXI.
>=20
> Regards,
>=20
> Yusuke
>=20
>=20
> On 2012=E5=B9=B403=E6=9C=8831=E6=97=A5 19:55, Mark Nottingham wrote:
>> What's the use case here? Content negotiation, or something else?
>>=20
>> Regards,
>>=20
>>=20
>> On 29/03/2012, at 10:52 PM, Zach Shelby wrote:
>>=20
>>> I have posted a new version of the +exi registration draft. This =
version improves the Interoperability considerations of the registration =
requirements and further clarifies when this suffix may be used, as per =
the feedback on the list from Carine and others.
>>>=20
>>> http://www.ietf.org/id/draft-shelby-exi-registration-01.txt
>>>=20
>>> Regards,
>>> Zach
>>>=20
>>> Begin forwarded message:
>>>=20
>>>> From: internet-drafts@ietf.org
>>>> Date: March 29, 2012 10:47:32 PM GMT+02:00
>>>> To: zach@sensinode.com
>>>> Subject: New Version Notification for =
draft-shelby-exi-registration-01.txt
>>>>=20
>>>> A new version of I-D, draft-shelby-exi-registration-01.txt has been =
successfully submitted by Zach Shelby and posted to the IETF repository.
>>>>=20
>>>> Filename:	 draft-shelby-exi-registration
>>>> Revision:	 01
>>>> Title:		 The +exi Media Type Suffix
>>>> Creation date:	 2012-03-29
>>>> WG ID:		 Individual Submission
>>>> Number of pages: 5
>>>>=20
>>>> 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&quot;+exi&quot; for use in a specific class of =
protocols, where
>>>>  &quot;exi&quot; content-type encoding or the =
generic&quot;application/exi&quot; Media
>>>>  Type are not applicable.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> The IETF Secretariat
>>>=20
>>> --
>>> Zach Shelby, Chief Nerd, Sensinode Ltd.
>>> http://www.sensinode.com
>>> http://zachshelby.org  - My blog "On the Internet of Things"
>>> http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded =
Internet"
>>> Mobile: +358 40 7796297
>>>=20
>>> _______________________________________________
>>> apps-discuss mailing list
>>> apps-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>=20
>> --
>> Mark Nottingham
>> http://www.mnot.net/
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>=20

--
Mark Nottingham
http://www.mnot.net/




