Re: [apps-discuss] New Version Notification for draft-shelby-exi-registration-01.txt

Yusuke DOI <yusuke.doi@toshiba.co.jp> Mon, 02 April 2012 07:45 UTC

Return-Path: <yusuke.doi@toshiba.co.jp>
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 71C5121F8874 for <apps-discuss@ietfa.amsl.com>; Mon, 2 Apr 2012 00:45:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.09
X-Spam-Level:
X-Spam-Status: No, score=-8.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-8]
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 hyTZcKGTBVvL for <apps-discuss@ietfa.amsl.com>; Mon, 2 Apr 2012 00:45:11 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id 5BEC921F887B for <apps-discuss@ietf.org>; Mon, 2 Apr 2012 00:45:11 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp with ESMTP id q327j9xP027126 for <apps-discuss@ietf.org>; Mon, 2 Apr 2012 16:45:09 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp id q327j9UU021940 for apps-discuss@ietf.org; Mon, 2 Apr 2012 16:45:09 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id SAA21938; Mon, 2 Apr 2012 16:45:09 +0900
Received: from mx12.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id q327j93o014425 for <apps-discuss@ietf.org>; Mon, 2 Apr 2012 16:45:09 +0900 (JST)
Received: by toshiba.co.jp id q327j8ZO014723; Mon, 2 Apr 2012 16:45:08 +0900 (JST)
Message-Id: <201204020745.q327j8ZO014723@toshiba.co.jp>
Date: Mon, 02 Apr 2012 16:45:08 +0900
From: Yusuke DOI <yusuke.doi@toshiba.co.jp>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
References: <20120329204732.13711.266.idtracker@ietfa.amsl.com> <5580A282-E191-4962-9410-6CF9FB14EDFC@sensinode.com> <0885CE0D-11A3-4396-9443-37B4FF8D36C9@mnot.net>
In-Reply-To: <0885CE0D-11A3-4396-9443-37B4FF8D36C9@mnot.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
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 07:45:12 -0000

Dear Mark,

I have a following use case.

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.

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.

Regards,

Yusuke


On 2012年03月31日 19:55, Mark Nottingham wrote:
> What's the use case here? Content negotiation, or something else?
>
> Regards,
>
>
> On 29/03/2012, at 10:52 PM, Zach Shelby wrote:
>
>> 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.
>>
>> http://www.ietf.org/id/draft-shelby-exi-registration-01.txt
>>
>> Regards,
>> Zach
>>
>> Begin forwarded message:
>>
>>> 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
>>>
>>> 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.
>>>
>>> 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
>>>
>>> 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.
>>>
>>>
>>>
>>>
>>> The IETF Secretariat
>>
>> --
>> 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
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
> --
> Mark Nottingham
> http://www.mnot.net/
>
>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss