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

"Panos Kampanakis (pkampana)" <pkampana@cisco.com> Wed, 12 September 2018 15:31 UTC

Return-Path: <pkampana@cisco.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 13308130E1E for <ace@ietfa.amsl.com>; Wed, 12 Sep 2018 08:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 BVRSN3dihD5c for <ace@ietfa.amsl.com>; Wed, 12 Sep 2018 08:31:25 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7597112F1A5 for <ace@ietf.org>; Wed, 12 Sep 2018 08:31:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10634; q=dns/txt; s=iport; t=1536766285; x=1537975885; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=JTxzPOXBtiuEDy3TkqBpGEBErFJ+3hvDLMImf0Rsr/Q=; b=lRC7bovMxORj+I09fZWK8lJqLjGIggsBb0Q8lqIprlbYggsHfKJ9IHz8 0lwIgVRKAl2ATeHKVd6U9OFHrn45x70n8td2l4f2+TQTMFyKUq7MfO/oo H+vAHo3vPlZPG4apZ24EUXrBL9xoTrlv7iZErqTbbI1aZC++CT4wXtJZS g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CLAAA/MJlb/4YNJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYFPgRB3ZX8oCpgYgg2RCIU1FIFmC4RsAoNLITUXAQIBAQIBAQJtKIU4AQEBAQMtXAIBCBEEAQEoBzIUCQgBAQQBEgiDGoEdZKY8igqKZxeBQT+EJIRGboUiAo04hWSINU8JAokAOYZHH457k3kCERSBJR8CNIFVcBWDJ5BTb41kgR4BAQ
X-IronPort-AV: E=Sophos;i="5.53,365,1531785600"; d="scan'208,217";a="170759591"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Sep 2018 15:31:24 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id w8CFVONB022490 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 12 Sep 2018 15:31:24 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 12 Sep 2018 10:31:23 -0500
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1395.000; Wed, 12 Sep 2018 10:31:23 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>, "ace@ietf.org" <ace@ietf.org>
Thread-Topic: ace-coap-est: unclear definition of /.well-known/est URI
Thread-Index: AdRKqeFCUK1AzigFR5qvzUaQ2+R0GgAAdGzw
Date: Wed, 12 Sep 2018 15:31:23 +0000
Message-ID: <39ff6ec1903c4c3a9d333c41a38a1ad9@XCH-ALN-010.cisco.com>
References: <DB6P190MB005479015E3F02D4028541A9FD1B0@DB6P190MB0054.EURP190.PROD.OUTLOOK.COM>
In-Reply-To: <DB6P190MB005479015E3F02D4028541A9FD1B0@DB6P190MB0054.EURP190.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.150.34.37]
Content-Type: multipart/alternative; boundary="_000_39ff6ec1903c4c3a9d333c41a38a1ad9XCHALN010ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.20, xch-rcd-010.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/SgeX1NXIQ1W9L1PNv8quFN15KWw>
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: Wed, 12 Sep 2018 15:31:27 -0000

Hi Esko,

Thanks for the comment.

Certificate authorities use the ArbitraryLabel in order to direct the CSR request and issue certificates based on a certain policy / cert profile. For example, if you are ClientX you get label ClientX198282 and when you hit the CA HTTP URI .well-known/est/ ClientX198282/sen the CA knows to use the policy for ClientX in order to issue a certificate. Of course, someone that has deployed an on-prem CA that has the same cert profile for all endpoints will not need an arbitrary label and the default EST namespace is enough.

So, even though coaps://www.example..com/.well-known/est/<short-est> would work for many cases, we needed to keep the coaps://www.example..com/.well-known/est/ArbitraryLabel/<short-est> as well for cases where the client is getting a cert from a CA that serves more than on cert profiles. We may need to specify that the labl should be as short as possible, even though it is kind of self-explanatory.

I hope it makes sense.

Panos


From: Ace [mailto:ace-bounces@ietf.org] On Behalf Of Esko Dijk
Sent: Wednesday, September 12, 2018 11:10 AM
To: ace@ietf.org
Subject: [Ace] ace-coap-est: unclear definition of /.well-known/est URI

Dear all/authors of ace-coap-est,

Section 5 of ace-coap-est-05 indicates URI discovery is possible to find the EST functions entry point URI. Also a well-known URI is defined:

coaps://www.example..com/.well-known/est/ArbitraryLabel/<short-est>.

This URI seems more complicated than needed? What if we simply define an always-available well-known URI, usable without any discovery:

coaps://www.example..com/.well-known/est/<short-est>

This re-uses the well-known EST namespace which is exactly defined to do EST functions. So using the short-est names within this namespace should be fine.
It is important that a well-known URI is available that is usable without discovery, just like EST RFC 7030 defines it for https.
The "ArbitraryLabel" only makes the URI longer.

best regards
Esko Dijk