Re: [Sidrops] Barry Leiba's No Objection on draft-ietf-sidrops-https-tal-07: (with COMMENT)

Tim Bruijnzeels <tim@nlnetlabs.nl> Tue, 09 April 2019 15:08 UTC

Return-Path: <tim@nlnetlabs.nl>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEC51203CE; Tue, 9 Apr 2019 08:08:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nlnetlabs.nl
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 Iyn4gVLC8x2P; Tue, 9 Apr 2019 08:08:28 -0700 (PDT)
Received: from dicht.nlnetlabs.nl (open.nlnetlabs.nl [185.49.140.10]) (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 B3BF41202FA; Tue, 9 Apr 2019 08:08:28 -0700 (PDT)
Received: from [10.87.0.224] (unknown [145.15.244.27]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 21C9425177; Tue, 9 Apr 2019 17:08:25 +0200 (CEST)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=fail (p=none dis=none) header.from=nlnetlabs.nl
Authentication-Results: dicht.nlnetlabs.nl; spf=fail smtp.mailfrom=tim@nlnetlabs.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1554822506; bh=1xJRHclVh6skyRlAMcmRZBQvIYVImgB7+7hggBkAMd4=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=BMroz+GRD9mvypSzC71ZfUQwItb1YmzV1+6kbOlu9n2T1JcztMU3iOeutKPEv2V5z D1pQS2geC9FmMK7kxu3EOGgvmG1br7UelU1h8aBe8Qn9NtGn5yjY00lDy+rWQNlYC7 msoVXf2Dd0mJ1uZ6L8R/yZ2u7cCi+rSlKnWn8HE4=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Tim Bruijnzeels <tim@nlnetlabs.nl>
In-Reply-To: <155469895228.18178.17765650719093981433.idtracker@ietfa.amsl.com>
Date: Tue, 9 Apr 2019 17:08:24 +0200
Cc: The IESG <iesg@ietf.org>, draft-ietf-sidrops-https-tal@ietf.org, Chris Morrow <morrowc@ops-netman.net>, sidrops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2EBF7A6-E1F3-4616-B689-3A63E556F047@nlnetlabs.nl>
References: <155469895228.18178.17765650719093981433.idtracker@ietfa.amsl.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/KCyfmAowVBpcp9Mi-2cL2Nk7cHM>
Subject: Re: [Sidrops] Barry Leiba's No Objection on draft-ietf-sidrops-https-tal-07: (with COMMENT)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2019 15:08:31 -0000

Dear Barry,

> On 8 Apr 2019, at 06:49, Barry Leiba via Datatracker <noreply@ietf.org>; wrote:
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I realize that this document inherits the text in Section 3 from RFC 6490, but
> can you tell me why there are SHOULDs and not MUSTs?  Why would one NOT do it
> the way Section 3 specifies?

The first half of section 3 specifies how an RP uses the TAL to download and validate a TA certificate. In my opinion the SHOULD in the first sentence could be a MUST.

The remainder of the section deals with strategies regarding downloading fresh copies, and choosing which of the (equivalent) URIs to use. In practice I believe that most if not all RP implementations fetch TA certificates on each validation run and the expiration time of the certificate is generally ignored - this does not conflict with the SHOULDs because generally these validation runs happen with a frequency of 10 mins, or hours at must - so it's much sooner. Furthermore some RPs choose to only try one URI to keep their code complexity low.

In short I don't remember clearly from the time that RFC7730 was discussed, but I don't think that there was consensus in the WG for a more formal and MUST-y specification for RP use. So, I think the SHOULDs reflect that.


> Then I’ll ask the same question for the new https text in Section 4, especially
> about TLS certificate and host name validation.

Yes, and good point. Pete Resnick raised a similar point and I replied to him yesterday. Are your okay with discussing this point in that thread?

Thank you

Tim