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

Carsten Bormann <cabo@tzi.org> Fri, 26 October 2012 16:35 UTC

Return-Path: <cabo@tzi.org>
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 0F9D221F853B for <core@ietfa.amsl.com>; Fri, 26 Oct 2012 09:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.227
X-Spam-Level:
X-Spam-Status: No, score=-106.227 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 mFQhxzl5G+4B for <core@ietfa.amsl.com>; Fri, 26 Oct 2012 09:35:54 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 4621921F8526 for <core@ietf.org>; Fri, 26 Oct 2012 09:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q9QGZiuT000117; Fri, 26 Oct 2012 18:35:44 +0200 (CEST)
Received: from [192.168.217.117] (p548935F1.dip.t-dialin.net [84.137.53.241]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 57E657AF; Fri, 26 Oct 2012 18:35:44 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <508AB6F1.4060701@toshiba.co.jp>
Date: Fri, 26 Oct 2012 18:35:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B77ADFDC-06A6-4A95-8E35-86D9DC5CB094@tzi.org>
References: <AE8DC8D8-C0F2-4F70-ABAD-638F2884CEF2@tzi.org> <508AB6F1.4060701@toshiba.co.jp>
To: Yusuke DOI <yusuke.doi@toshiba.co.jp>
X-Mailer: Apple Mail (2.1499)
Cc: "core@ietf.org WG" <core@ietf.org>
Subject: [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: Fri, 26 Oct 2012 16:35:55 -0000

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