Re: [Danish] Charter Text and the Problem Statement

Viktor Dukhovni <ietf-dane@dukhovni.org> Thu, 17 June 2021 20:14 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: danish@ietfa.amsl.com
Delivered-To: danish@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C85A3A2C80 for <danish@ietfa.amsl.com>; Thu, 17 Jun 2021 13:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 zzwRrcL1wp-u for <danish@ietfa.amsl.com>; Thu, 17 Jun 2021 13:14:02 -0700 (PDT)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A6363A2C7E for <danish@ietf.org>; Thu, 17 Jun 2021 13:14:02 -0700 (PDT)
Received: by straasha.imrryr.org (Postfix, from userid 1001) id F0DEEC7B37; Thu, 17 Jun 2021 16:13:59 -0400 (EDT)
Date: Thu, 17 Jun 2021 16:13:59 -0400
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: danish@ietf.org
Message-ID: <YMutB/Dz94SdGhes@straasha.imrryr.org>
Reply-To: danish@ietf.org
References: <DBBPR08MB5915066E1CE5BDB2D695A8DAFA0F9@DBBPR08MB5915.eurprd08.prod.outlook.com> <CAEfM=vQehhvSNeBNitJJjisEbimn_gizoo8VTtHWUJ1zSU+rQg@mail.gmail.com> <DBBPR08MB5915D8FC201DFEB31F7D8EA8FA0E9@DBBPR08MB5915.eurprd08.prod.outlook.com> <CAEfM=vTHPmDcOimf9xOvkYgeObbHvpfG1uZUVjBJFhykrZNafg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAEfM=vTHPmDcOimf9xOvkYgeObbHvpfG1uZUVjBJFhykrZNafg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/danish/XSljk_738TaD03cuYnAK4hiCFoI>
Subject: Re: [Danish] Charter Text and the Problem Statement
X-BeenThere: danish@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DANE AutheNtication for Iot Service Hardening <danish.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/danish>, <mailto:danish-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/danish/>
List-Post: <mailto:danish@ietf.org>
List-Help: <mailto:danish-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/danish>, <mailto:danish-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2021 20:14:05 -0000

On Thu, Jun 17, 2021 at 11:21:44AM -0700, Ash Wilson wrote:

> DANE server authentication with EAP-TLS brings another challenge: the
> absence of IP connectivity prior to authentication. This could be remedied
> by https://datatracker.ietf.org/doc/html/draft-ietf-tls-dnssec-chain-extension-07,
> if the work on that draft were to continue.

That seems rather unlikely in the short term, but in the meantime

    https://datatracker.ietf.org/doc/draft-dukhovni-tls-dnssec-chain/

will soon be published via the ISE.

> There are also challenges with validating the chain, tied to root key
> rotation. Devices which remain unplugged too long may not be able to
> authenticate.  On the other hand, it is a best practice to ensure that
> a device is patched before putting it into production, and updating
> roots of trust fits within the scope of that sort of activity.

Indeed a device that's been on the shelf for O(1 year) or more may well
find that the root key has been rolled.  There is therefore a need for a
mechanism to allow it to "catch up" by updating its software and trust
anchors.  Secure update of dormant devices is a tricky problem, that may
not have a one size fits all solution, there's likely a continuum of
tradeoffs between convenience and security.

-- 
    Viktor.