IETF Logo Mail Archive

Re: [Ace] Early media-type registration for EST over CoAP

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 16 May 2018 12:16 UTC

Return-Path: <mcr@sandelman.ca>
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 CA71C12D872 for <ace@ietfa.amsl.com>; Wed, 16 May 2018 05:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 YZFaeUuOqi4p for <ace@ietfa.amsl.com>; Wed, 16 May 2018 05:16:20 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD6DD12946D for <ace@ietf.org>; Wed, 16 May 2018 05:16:20 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [75.98.19.134]) by relay.sandelman.ca (Postfix) with ESMTPS id BF16C1F906; Wed, 16 May 2018 12:16:15 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 09A241145; Wed, 16 May 2018 13:15:52 +0100 (BST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
cc: "ace@ietf.org" <ace@ietf.org>
In-reply-to: <VI1PR0801MB2112C0B4E644A32082BA1257FA920@VI1PR0801MB2112.eurprd08.prod.outlook.com>
References: <VI1PR0801MB21122FFD4F19026259ABDF55FA930@VI1PR0801MB2112.eurprd08.prod.outlook.com> <30374.1526404823@localhost> <VI1PR0801MB2112C0B4E644A32082BA1257FA920@VI1PR0801MB2112.eurprd08.prod.outlook.com>
Comments: In-reply-to Hannes Tschofenig <Hannes.Tschofenig@arm.com> message dated "Wed, 16 May 2018 10:39:46 -0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 16 May 2018 08:15:52 -0400
Message-ID: <29971.1526472952@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/PGsIA3j1JqlPjEkBCEkSw2MCf-A>
Subject: Re: [Ace] Early media-type registration for EST over CoAP
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 16 May 2018 12:16:23 -0000

Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
    >> Hannes: do you have any opinion about the necessity of going through
    >> /.well-known/core to get the short URL, vs just using a
    >> /.well-known/est URL?

Yes, exactly.  Is option #1 useful enough to justify the code to parse
links?  Os is the code impact already paid for in your view?

    > (RTT for the lookup vs extra bytes in the URL)
    > Are you asking me about these two options:
    > Option #1 - going through /.well-known/core
    >      REQ: GET /.well-known/core?rt=ace.est
    >      RES: 2.05 Content </est-root >; rt="ace.est"


    > Option #2 - using a /.well-known/est URL
    >      REQ: GET /.well-known/est
    >      RES: 2.05 Content </est-root>; rt="ace.est"

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email