Re: [apps-discuss] +exi

"Paul E. Jones" <paulej@packetizer.com> Fri, 16 December 2011 19:26 UTC

Return-Path: <paulej@packetizer.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 92A6421F86A6 for <apps-discuss@ietfa.amsl.com>; Fri, 16 Dec 2011 11:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.944
X-Spam-Level:
X-Spam-Status: No, score=-1.944 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, J_CHICKENPOX_33=0.6]
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 mlCBk0QmgfyF for <apps-discuss@ietfa.amsl.com>; Fri, 16 Dec 2011 11:26:48 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id B85BF21F86A1 for <apps-discuss@ietf.org>; Fri, 16 Dec 2011 11:26:48 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id pBGJQjJS005141 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 16 Dec 2011 14:26:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1324063606; bh=dcKfUmZ2oWGQq2nPASLqToKUouauhYKlV2Ga1BRs0ow=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=BMJ+r9m7+OkJRiD8bHmUrnfETKeRZQNAQCMY/MN6vkL/kpnzblnCuHrhP6AxHf80N 1Rv1aavZVo5hD1Vmri/d/wxyo3vdjdrNVmZAJ7z/rvDeOQ7LBIDKXojfVWBq3vpGgY Q0ZuuCfYFKxkhTV2jh2J76HUK5z2Dx6ow/nzqB2M=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Peter Saint-Andre'" <stpeter@stpeter.im>, "'Zach Shelby'" <zach@sensinode.com>
References: <01O8GE5O3B5K00RCTX@mauve.mrochek.com> <C68CB012D9182D408CED7B884F441D4D0611DAC31D@nambxv01a.corp.adobe.com> <4EC31F1E.6070304@stpeter.im> <8p86c7d6chvadsku6k5dhct20qkl7uk73l@hive.bjoern.hoehrmann.de> <4EC326FE.1010809@stpeter.im> <lu96c7hsl37325nn3184ub4vr88qjgja50@hive.bjoern.hoehrmann.de> <EDB50792-348B-4693-9FDF-04BA091F8BE9@sensinode.com> <4EE78F2F.2070601@stpeter.im> <20111213215816.GI5525@jay.w3.org> <5EFF390A-3D29-4F15-95BE-C81EFCF6D3D5@mnot.net> <20111214092327.GK5525@jay.w3.org> <7472087B-86F9-4683-BA74-F70EC98D483C@sensinode.com> <4EEB6EB2.30807@stpeter.im>
In-Reply-To: <4EEB6EB2.30807@stpeter.im>
Date: Fri, 16 Dec 2011 14:26:32 -0500
Message-ID: <01b701ccbc28$9ed3dbe0$dc7b93a0$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIEa5/2+nM5lYQ8PPERrPCRFDYWOwDpOMZWAhK12sMBrC/z+gIDa7CbAnnL4GYBQheGCAIdzTIAAeYrRR0B+zsargIIb4djAnE0zJoBxnfi8JS6QiFg
Content-Language: en-us
Cc: paduffy@cisco.com, 'Mark Nottingham' <mnot@mnot.net>, 'Thomas Herbst' <therbst@silverspringnet.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] +exi
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, 16 Dec 2011 19:26:49 -0000

What might also be interesting to understand is how register +exi would be
different than registering other binary XML formats.  Would we need
+fastinfoset and +BiM and so on?

I'm not opposed to +exi if that helps in decoding the data somehow, but it
doesn't seem like it would add any more value than signaling the media type
and indicating the content encoding.  In fact, the latter might be used to
indicate various modes of EXI, if that was necessary.

Paul

> -----Original Message-----
> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> bounces@ietf.org] On Behalf Of Peter Saint-Andre
> Sent: Friday, December 16, 2011 11:16 AM
> To: Zach Shelby
> Cc: paduffy@cisco.com; Mark Nottingham; Thomas Herbst; apps-
> discuss@ietf.org
> Subject: Re: [apps-discuss] +exi
> 
> On 12/16/11 12:24 AM, Zach Shelby wrote:
> > On Dec 14, 2011, at 11:23 AM, Carine Bournez wrote:
> >
> >> In the schema-informed mode the encoder and the decoder use a schema,
> >> the EXI 1.0 version specifies XML schema informed grammars.
> >> The reference to that schema is carried in the EXI header. The format
> >> of that "schemaId" is not specified for 1.0 processors, it can be
> >> whatever is practical for the application. It is *optional* in the
> >> EXI header, even when a schema is in use: applications can also
> >> "share" this information out of band. EXI 1.0 is intentionally
> >> liberal on a number of details and defers them to the application
> >> level, so that it can support a large range of use cases.
> >
> > Right. It is exactly these kinds of applications that are using schema
> > informed mode natively (without intermediate XML), where the
> > application/foo+exi media type helps to determine this information out
> > of band. When registering foo+exi, the schema information should be
> > included in the registration.  In addition to SE2 mentioned so far,
> > also our specification on SenML
> > [http://tools.ietf.org/html/draft-jennings-senml-07] is requesting an
> > application/senml+exi media type. Both of these media types are aimed
> > at constrained embedded devices.
> 
> Zach, thanks for clarifying the matter. Perhaps it would make sense for
> someone to write a brief I-D describing the rationale for media types
> with the +exi suffix and the information required to register such
> types.
> 
> Peter
> 
> --
> Peter Saint-Andre
> https://stpeter.im/
> 
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss