IETF Logo Mail Archive

Re: [Ace] Embedded Content Types

Carsten Bormann <cabo@tzi.org> Thu, 21 February 2019 22:52 UTC

Return-Path: <cabo@tzi.org>
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 57FA0130F1D; Thu, 21 Feb 2019 14:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Ob9K-0nlR8np; Thu, 21 Feb 2019 14:52:45 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24EA9129C6A; Thu, 21 Feb 2019 14:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x1LMqRMw008893; Thu, 21 Feb 2019 23:52:33 +0100 (CET)
Received: from [192.168.217.106] (p54A6C2FE.dip0.t-ipconnect.de [84.166.194.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4458qv4brVz1Bp8; Thu, 21 Feb 2019 23:52:27 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <033201d4ca35$23f58f40$6be0adc0$@augustcellars.com>
Date: Thu, 21 Feb 2019 23:52:26 +0100
Cc: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, ace <ace@ietf.org>, Klaus Hartke <hartke@projectcool.de>, draft-ietf-ace-coap-est@ietf.org
X-Mao-Original-Outgoing-Id: 572482344.983409-5a342cd7b2c801f26edc6bf42c4caa0c
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F0FAFC5-947C-4B8E-B83F-82D68750A80A@tzi.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>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/irhHEIDMnc4pvYJTwfZ2UmJUJQw>
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 22:52:48 -0000

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

v2.23.0 | Report a Bug | By Email