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

Peter van der Stok <stokcons@bbhmail.nl> Mon, 24 September 2018 07:39 UTC

Return-Path: <stokcons@bbhmail.nl>
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 63CE3130E6A for <ace@ietfa.amsl.com>; Mon, 24 Sep 2018 00:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 2Ol_SMMrmzvD for <ace@ietfa.amsl.com>; Mon, 24 Sep 2018 00:39:29 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0222.hostedemail.com [216.40.44.222]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E8A8130E21 for <ace@ietf.org>; Mon, 24 Sep 2018 00:39:29 -0700 (PDT)
Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay04.hostedemail.com (Postfix) with ESMTP id 3DDA9180A8431; Mon, 24 Sep 2018 07:39:28 +0000 (UTC)
X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C
X-Spam-Summary: 2, -10, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :::::::::, RULES_HIT:41:72:152:355:379:582:599:800:962:967:973:983:988:989:1152:1189:1208:1212:1221:1260:1313:1314:1345:1359:1431:1436:1437:1516:1517:1518:1535:1542:1575:1588:1589:1592:1594:1711:1730:1777:1792:2068:2069:2198:2199:2525:2528:2559:2564:2682:2685:2692:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3353:3622:3865:3866:3867:3868:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4117:4250:4321:4860:5007:6117:6119:6261:6657:6659:6678:7875:7903:8603:9010:9025:9177:10004:10376:10400:10848:11232:11658:11914:12043:12109:12291:12379:12438:12683:12740:12895:13139:13141:13230:13439:13846:14093:14095:14096:14149:14181:14721:21080:21324:21433:21451:21627:21819:30003:30022:30025:30034:30054:30060, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral
X-HE-Tag: can40_6fb0f762b9557
X-Filterd-Recvd-Size: 6293
Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf04.hostedemail.com (Postfix) with ESMTPA; Mon, 24 Sep 2018 07:39:27 +0000 (UTC)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_840c29b6475bfc80757e8e7dd050a2a0"
Date: Mon, 24 Sep 2018 09:39:27 +0200
From: Peter van der Stok <stokcons@bbhmail.nl>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, consultancy@vanderstok.org, ace@ietf.org
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <DB6P190MB0054BB06A482C9E5BE1A1E9FFD120@DB6P190MB0054.EURP190.PROD.OUTLOOK.COM>
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>
Message-ID: <8efff06eacacd876bf1c926cde6a3fc5@bbhmail.nl>
X-Sender: stokcons@bbhmail.nl
User-Agent: Roundcube Webmail/1.2.7
X-Originating-IP: [90.0.6.116]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/_9Sn0PLlIucullWx-DeRprsqhi8>
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 07:39:31 -0000

Sorry folks,

But you confuse me.
discovery is about /.well-known/core.
I don't understand where /.well-known/est comes in for discovery.

Peter.
Esko Dijk schreef op 2018-09-21 10:24:

>> I've asked if discovery is always required, permitted, or encouraged.
> 
> Normally it is always encouraged to use discovery in favour of fixed URIs at the server, to avoid specs squatting the URI namespace. But in our case the /.well-known/est space is already assigned (RFC 7030) so we have to support it also in coaps-est and no additional squatting takes place. Besides support for the well-known URI location, discovery by a client is permitted to find "ace.est" type resources at other places e.g. to get shorter URIs or to get 6lowpan-compressible port numbers, or both.
> 
>> I.e. - can the client avoid the round trip to do the discovery?
>> - does the server have to provide the discovery?
>> -- if not, what does a client do that performs the discovery and fails?
>> I've been told it was required.
> 
> - So it can't be required for the client, is my opinion. 
> - The server must support it (being a good CoAP-citizen) in some way as in the previous email.
> - If it fails, the client might try another time using the /.well-known/est resource, or retry the discovery later on. (There could be various implementation-specific tactics here. Maybe the IP address of the EST server was configured wrongly; and the process that lead to this IP address can be redone by the client.)
> 
> Esko
> 
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace