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

Zach Shelby <zach@sensinode.com> Fri, 13 April 2012 18:25 UTC

Return-Path: <zach@sensinode.com>
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 B57E321F8726 for <apps-discuss@ietfa.amsl.com>; Fri, 13 Apr 2012 11:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 1P0tBMOKcPBq for <apps-discuss@ietfa.amsl.com>; Fri, 13 Apr 2012 11:25:05 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 2A1AC21F8722 for <apps-discuss@ietf.org>; Fri, 13 Apr 2012 11:25:04 -0700 (PDT)
Received: from [192.168.1.102] (188-67-213-61.bb.dnainternet.fi [188.67.213.61]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q3DIP0Hb023031; Fri, 13 Apr 2012 21:25:00 +0300
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <4F886D9B.9030203@gmx.de>
Date: Fri, 13 Apr 2012 21:24:59 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5FC2180-3FCB-4E26-9E28-873C6CF0DA6E@sensinode.com>
References: <20120329204732.13711.266.idtracker@ietfa.amsl.com> <20120402124522.GX16698@jay.w3.org> <8B84EAAD-CD22-4461-9BC6-AB78974A94A2@sensinode.com> <20120411075024.GN18899@jay.w3.org> <4F85410D.20802@toshiba.co.jp> <20120411085920.GP18899@jay.w3.org> <FBCADBF9-D6FB-4E0D-9668-F5B3EF744037@tzi.org> <f5bobqye1vj.fsf@calexico.inf.ed.ac.uk> <4F85A3A2.9000505@gmx.de> <01OE6QSJQ2EW00ZUIL@mauve.mrochek.com> <42487F00-DE42-49AA-9E4C-23412504C70A@tzi.org> <01OE8GNZLGKE00ZUIL@mauve.mrochek.com> <7AB551FC-03FC-4A89-8929-9E9017493C28@sensinode.com> <4F884862.9080609@att.com> <D73B8F43-AC66-48B9-BE26-A38A97C628B4@tzi.org> <f5bmx6ftxm2.fsf@calexico.inf.ed.ac.uk> <4F88546D.5020007@gmx.de> <f5behrrtwqc.fsf@calexico.inf.ed.ac.uk> <4F885889.5020401@gmx.de> <f5baa2ftvfy.fsf@calexico.inf.ed.ac.uk> <4F886487.3050806@gmx.de> <f5b62d3tsg2.fsf@calexico.inf.ed.ac.uk> <4F886D9B.9030203@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1084)
Cc: "apps-discuss@ietf.org Discuss" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Fwd: 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: Fri, 13 Apr 2012 18:25:06 -0000

On Apr 13, 2012, at 9:16 PM, Julian Reschke wrote:

> On 2012-04-13 20:09, Henry S. Thompson wrote:
>> Julian Reschke writes:
>> 
>>>> ...
>>> 
>>> All true, but as far as I can tell, you didn't mention
>>> Content-Encoding in the message I replied to.
>> 
>> Ah, I see the disconnect.  In my original message, I said:
>> 
>>  "Why not call it application/senml+xml and encode it with EXI?
>>   Doesn't that tell you everything you need?"
>> 
>> I should have been more explicit -- what I meant the above to convey
>> was
>> 
>>  "Why not call it application/senml+xml and encode it with EXI?
>>   That is, use Content-Type: application/senml+xml and
>>                Content-Encoding: exi .
>>   Doesn't that tell you everything you need?"
>> 
>> So, reset.  With that clarification, what do you think?
> 
> Yes, absolutely, that works with HTTP.

Correct, content-encoding is valid for the non-schema informed mode of EXI where there is no OOB dictionary needed. There has never been an argument against that, so all good there.

We are trying to improve the interoperability situation with schema-informed EXI (my +exi draft was an attempt at that). As Ned pointed out though, for schema-informed EXI content-encoding is not really valid, but at the same time +exi is not suitable either. For this reason we are now looking at just using e.g. application/senml-exi informally or possible thinking about a more formal suffix style for encodings that require OOB dictionary information. 

> AFAIR, Core (<http://tools.ietf.org/wg/core/>) doesn't have Content-Encoding, though.

We actually fixed that in the -09 revision of CoAP. It is possible for us to deal with content-encodings, we just have to make multiple code entries in our registry. 

Zach

> 
> Best regards, Julian
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

-- 
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