IETF Logo Mail Archive

Re: [Ace] ace-coap-est: unclear definition of /.well-known/est URI

Jim Schaad <ietf@augustcellars.com> Mon, 24 September 2018 17:22 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 40E92130E3F for <ace@ietfa.amsl.com>; Mon, 24 Sep 2018 10:22:11 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 d_YJhgbaCGE4 for <ace@ietfa.amsl.com>; Mon, 24 Sep 2018 10:22:09 -0700 (PDT)
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 231B5126CB6 for <ace@ietf.org>; Mon, 24 Sep 2018 10:22:09 -0700 (PDT)
Received: from Jude (192.168.1.157) by mail2.augustcellars.com (192.168.1.201) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 24 Sep 2018 10:17:59 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Michael Richardson' <mcr@sandelman.ca>, consultancy@vanderstok.org
CC: 'Esko Dijk' <esko.dijk@iotconsultancy.nl>, "'Panos Kampanakis (pkampana)'" <pkampana@cisco.com>, ace@ietf.org
References: <DB6P190MB005479015E3F02D4028541A9FD1B0@DB6P190MB0054.EURP190.PROD.OUTLOOK.COM> <39ff6ec1903c4c3a9d333c41a38a1ad9@XCH-ALN-010.cisco.com> <DB6P190MB00548845B38C0B0DF2380CD1FD180@DB6P190MB0054.EURP190.PROD.OUTLOOK.COM> <fc396115e9a54f80babfe9a9f5ae9e74@XCH-ALN-010.cisco.com> <DB6P190MB005441A30B3C3414EFF55D5EFD1D0@DB6P190MB0054.EURP190.PROD.OUTLOOK.COM> <26476.1537455069@localhost> <1c3188c5281a3bc921b97c9c7bc6b053@bbhmail.nl> <DB6P190MB00547429FEA6C0B70337AB69FD130@DB6P190MB0054.EURP190.PROD.OUTLOOK.COM> <7584.1537475677@localhost> <DB6P190MB0054BB06A482C9E5BE1A1E9FFD120@DB6P190MB0054.EURP190.PROD.OUTLOOK.COM> <245cff4973f04818a2b8d14a75dc56d0@bbhmail.nl> <30212.1537806440@localhost>
In-Reply-To: <30212.1537806440@localhost>
Date: Mon, 24 Sep 2018 10:21:58 -0700
Message-ID: <00f101d4542b$1b0a6520$511f2f60$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHtkAbQdT6NZbqXUyKz57/9IdduJwECnv5oAW+A2K4B0oHkfgL64OWRArtbt6sBKUdDIgHjmVscAm3GiXkCrna0/QIUoJUQAlssiYykGJc48A==
Content-Language: en-us
X-Originating-IP: [192.168.1.157]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/nwywR3KnAsynOROu3QHMcTbOJ_g>
Subject: Re: [Ace] ace-coap-est: unclear definition of /.well-known/est URI
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: Mon, 24 Sep 2018 17:22:11 -0000


> -----Original Message-----
> From: Ace <ace-bounces@ietf.org> On Behalf Of Michael Richardson
> Sent: Monday, September 24, 2018 9:27 AM
> To: consultancy@vanderstok.org
> Cc: Esko Dijk <esko.dijk@iotconsultancy.nl>; Panos Kampanakis (pkampana)
> <pkampana@cisco.com>; ace@ietf.org
> Subject: Re: [Ace] ace-coap-est: unclear definition of /.well-known/est
URI
> 
> 
> Peter van der Stok <stokcons@bbhmail.nl> wrote:
>     > What do I read?  when you do GET coap://example.com/.well-known/core
>     > The discovery is on port 5683.  When you do GET
>     > coaps://example.com/.well-known/core the discovery port is 5684.
> 
> yes, the question is, when you ask:
> 
> coap://example.com/.well-known/core?rt=ace.est
> 
> do you expect to get back a pointer to:
> 
>    coaps://example.com/est
> 
>     > RFC 7030 does not ask a port number from IANA.  And a search through
>     > IANA port numbers on "est" does not yield anything.
> 
> It does not.
> a) it doesn't do discovery, but just uses /.well-known directly.
> b) it assumes https://

Is there any reason to assume that you need a different port from the
default pair of coap ports?  Knowing what the protocol and host name will
point it to the correct location and you have the URI path to go to the
correct resource on that server.  

Jim

> 
> --
> ]               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
[

v2.23.0 | Report a Bug | By Email