IETF Logo Mail Archive

Re: [Iot-onboarding] EST CACerts and Pinned Domain Certificate

Eliot Lear <lear@cisco.com> Mon, 23 March 2020 14:43 UTC

Return-Path: <lear@cisco.com>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED5173A08A3 for <iot-onboarding@ietfa.amsl.com>; Mon, 23 Mar 2020 07:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 mythz5wRRnfg for <iot-onboarding@ietfa.amsl.com>; Mon, 23 Mar 2020 07:42:58 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E145D3A0878 for <iot-onboarding@ietf.org>; Mon, 23 Mar 2020 07:42:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=802; q=dns/txt; s=iport; t=1584974578; x=1586184178; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=pyy899IICOFs1h0jMrUCDQHVBPHjy3XP6BUTxB2bQcQ=; b=kGSle/Zo3gKgOkdKfmZM9zQIdSwE9ou8LqgCbe4pRsLgGZHOYvml/Szm 3CDSjxEGPtZQEANslzcTq0pZkOWK7XoFAO+OD94aMM178lloVPLFtIkrY Kv5jGUo6Ugvmg7O+4PL7OUTb8cZbBWI7PPZ0z26AugKgV8qqVSUDA3X7x 4=;
X-IronPort-AV: E=Sophos;i="5.72,296,1580774400"; d="scan'208";a="24615757"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Mar 2020 14:42:55 +0000
Received: from [10.61.164.61] ([10.61.164.61]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 02NEgsZ7018451 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 Mar 2020 14:42:55 GMT
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <CAHiu4JO93swur42mT7rjhGTouVhefjjXftHJi=4Bnpk=t_aV-Q@mail.gmail.com>
Date: Mon, 23 Mar 2020 15:42:54 +0100
Cc: iot-onboarding@ietf.org, "Max Pritikin (pritikin)" <pritikin@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC1D9B31-1225-4E34-83E9-10C608349693@cisco.com>
References: <CAHiu4JO93swur42mT7rjhGTouVhefjjXftHJi=4Bnpk=t_aV-Q@mail.gmail.com>
To: "M. Ranganathan" <mranga@gmail.com>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
X-Outbound-SMTP-Client: 10.61.164.61, [10.61.164.61]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/7NktmQb0lBJQ7V7s_x9S1iReEt4>
Subject: Re: [Iot-onboarding] EST CACerts and Pinned Domain Certificate
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IoT onboarding mechanisms <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2020 14:43:05 -0000


> On 22 Mar 2020, at 00:10, M. Ranganathan <mranga@gmail.com> wrote:
> 
> Hello,
> 
> Consider an integrated BRSKI-EST server. The pledge bootstraps and gets the pinned domain certificate. Then the pledge queries EST for the ca-certs. Is it correct to require that the pinned domain cert must be present in the CACerts collection returned by the EST server when the pledge does a cacerts query  (but can include additional certificates) ? 

I don’t think so, because you may make that query from time to time if you are reregistering.  What do others think?

> 
> Thanks 
> 
> Ranga
> 
> -- 
> M. Ranganathan 
> 
> -- 
> Iot-onboarding mailing list
> Iot-onboarding@ietf.org
> https://www.ietf.org/mailman/listinfo/iot-onboarding

v2.23.0 | Report a Bug | By Email