Re: [Ace] Embedded Content Types

Jim Schaad <ietf@augustcellars.com> Thu, 21 February 2019 23:35 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24C981312A8; Thu, 21 Feb 2019 15:35:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aLGFWhtjz2oB; Thu, 21 Feb 2019 15:35:35 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E39971312A0; Thu, 21 Feb 2019 15:35:32 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 21 Feb 2019 15:35:03 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Carsten Bormann' <cabo@tzi.org>
CC: "'Panos Kampanakis (pkampana)'" <pkampana@cisco.com>, 'ace' <ace@ietf.org>, 'Klaus Hartke' <hartke@projectcool.de>, <draft-ietf-ace-coap-est@ietf.org>
References: <02a201d4c945$eb10a510$c131ef30$@augustcellars.com> <17e617f1090e451c8b17f6550c2e213a@XCH-ALN-010.cisco.com> <CCD28BCC-16AA-492B-8E14-DAE9F2CF2E3C@tzi.org> <38fa1ec646974a329c286279b3fa9ff0@XCH-ALN-010.cisco.com> <032f01d4ca2f$ff19c6a0$fd4d53e0$@augustcellars.com> <b4bb6e5f3c7c47ffa040389f000f027f@XCH-ALN-010.cisco.com> <033201d4ca35$23f58f40$6be0adc0$@augustcellars.com> <6F0FAFC5-947C-4B8E-B83F-82D68750A80A@tzi.org>
In-Reply-To: <6F0FAFC5-947C-4B8E-B83F-82D68750A80A@tzi.org>
Date: Thu, 21 Feb 2019 15:35:03 -0800
Message-ID: <033301d4ca3e$14130180$3c390480$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJrZGJxf0tFnICB97QT3wBXQb1jnQH8O2UCAceAOO4BnmC3sAE5b/I6AkVh340B7+iMHAIsQf8dpFXKSvA=
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/HmBcI60zzMLey-XwdD7aNX2rLUw>
Subject: Re: [Ace] Embedded Content Types
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Feb 2019 23:35:37 -0000

It is true that the query parameters are part of the type.  However, the use of two different URIs allows for the discovery to figure out if both versions are supported rather than having either a failure occur because the query parameter is not supported or getting the wrong answer back because it is not looked for.

Jim


> -----Original Message-----
> From: Carsten Bormann <cabo@tzi.org>;
> Sent: Thursday, February 21, 2019 2:52 PM
> To: Jim Schaad <ietf@augustcellars.com>;
> Cc: Panos Kampanakis (pkampana) <pkampana@cisco.com>;; ace
> <ace@ietf.org>;; Klaus Hartke <hartke@projectcool.de>;; draft-ietf-ace-coap-
> est@ietf.org
> Subject: Re: [Ace] Embedded Content Types
> 
> On Feb 21, 2019, at 23:31, Jim Schaad <ietf@augustcellars.com>; wrote:
> >
> > I am thinking of two different URLs, that is not do the difference by a query
> parameter but by changing the URI.
> 
> Note that the query parameters are part of the URI, so fundamentally there
> is no difference between putting the info there or in the path part of the
> URI.
> 
> The path part can be slightly more concise.  We are more used to
> “computing” the query part.  I don’t have a strong preference.
> 
> But in either case it is good if discovery can find the URI being offered
> (including its query parameters, if those are used).
> 
> (And I agree that the “ct” target attribute really is for the top level media
> type; of course we could invent a new target attribute “ect” for embedded
> content formats [and fight against autocorrection for the rest of our lives :-
> )].)
> 
> Grüße, Carsten