Re: [core] Content-Format vs. Parameters (Re: CoRE agenda @ IETF85)

Yusuke DOI <yusuke.doi@toshiba.co.jp> Sun, 28 October 2012 16:05 UTC

Return-Path: <yusuke.doi@toshiba.co.jp>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A61DC21F866E for <core@ietfa.amsl.com>; Sun, 28 Oct 2012 09:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.489
X-Spam-Level:
X-Spam-Status: No, score=-5.489 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qFl7ig8Icf+Y for <core@ietfa.amsl.com>; Sun, 28 Oct 2012 09:05:44 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id 84E6021F8513 for <core@ietf.org>; Sun, 28 Oct 2012 09:05:40 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp with ESMTP id q9SG5dfo014201 for <core@ietf.org>; Mon, 29 Oct 2012 01:05:39 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp id q9SG5d8N015616 for core@ietf.org; Mon, 29 Oct 2012 01:05:39 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id BAA15615; Mon, 29 Oct 2012 01:05:39 +0900
Received: from mx12.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id q9SG5csD010231 for <core@ietf.org>; Mon, 29 Oct 2012 01:05:38 +0900 (JST)
Received: from spiffy21.isl.rdc.toshiba.co.jp by toshiba.co.jp id q9SG5cA6005971; Mon, 29 Oct 2012 01:05:38 +0900 (JST)
Received: from [133.199.16.107] (ivpn-1-107.mobile.toshiba.co.jp [133.199.16.107]) by spiffy21.isl.rdc.toshiba.co.jp (Postfix) with ESMTP id A777597CC0; Mon, 29 Oct 2012 01:05:38 +0900 (JST)
Message-ID: <508D57D2.7090405@toshiba.co.jp>
Date: Mon, 29 Oct 2012 01:05:38 +0900
From: Yusuke DOI <yusuke.doi@toshiba.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
References: <AE8DC8D8-C0F2-4F70-ABAD-638F2884CEF2@tzi.org> <508AB6F1.4060701@toshiba.co.jp> <B77ADFDC-06A6-4A95-8E35-86D9DC5CB094@tzi.org>
In-Reply-To: <B77ADFDC-06A6-4A95-8E35-86D9DC5CB094@tzi.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "core@ietf.org WG" <core@ietf.org>
Subject: Re: [core] Content-Format vs. Parameters (Re: CoRE agenda @ IETF85)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Oct 2012 16:05:44 -0000

Carsten,

Thank you for arrangement!

Yusuke

(2012/10/27 1:35), Carsten Bormann wrote:
> On Oct 26, 2012, at 18:14, Yusuke DOI<yusuke.doi@toshiba.co.jp>  wrote:
>
>> Carsten,
>>
>> if it's not too late, please let me introduce content-type parameter option in 5 min. talk. I'll be on the site.
>>
>> - Time: 5 min. for presentation, maybe another 5 min. for discussion?
>>   (I have no idea it's too long or short)
>> - Presenter: Yusuke DOI
>> - Objective: discussion on the content-type parameter proposal
>
> Certainly!
>
> I would like to structure this discussion into three items:
>
>          1) sanity check: Is what we are doing with Content-Format (coap-12's
>             name for what was Content-Type earlier) the right thing for the
>             majority of CoAP applications?
>
>          2) requirements: What are the applications we can't cover with
>             Content-Format?  What use-cases are behind them?
>
>          3) solution: is draft-doi-core-parameter-option the right solution
>             for these (some of these) use-cases?
>
> I think I can introduce 1, and I'd like you to do 2 and 3, with a focus on really making the case for 2.
>
> I'd like to allocate some 10 min for this.  If we get a good discussion about 1 and/or 2, we should be flexible about that.
>
> Updated agenda proposal is at:
>
> 	http://www.ietf.org/proceedings/85/agenda/agenda-85-core
>
> Grüße, Carsten
>