IETF Logo Mail Archive

Re: [Sidrops] 6486 bis

Tim Bruijnzeels <tim@nlnetlabs.nl> Thu, 02 July 2020 10:27 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 27E1C3A09A3 for <sidrops@ietfa.amsl.com>; Thu, 2 Jul 2020 03:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, 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 RcMm1oBvFuk2 for <sidrops@ietfa.amsl.com>; Thu, 2 Jul 2020 03:27:16 -0700 (PDT)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [IPv6:2a04:b900::1:0:0: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 B67E53A098B for <sidrops@ietf.org>; Thu, 2 Jul 2020 03:27:16 -0700 (PDT)
Received: from yoda.fritz.box (62-251-31-8.ip.xs4all.nl [62.251.31.8]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 7C4921512E; Thu, 2 Jul 2020 12:27:14 +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=1593685634; bh=aLHcnHuD4TpjFFVdinGV0bFah8MTu6GDPaAbZny92gQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=ogKmCY+ZWl+vgYCLJaZbE5wfEwiS9ac0HvnCbQpG0znWas9PaaDpkADk+tzlyP9yh qAit40Et+WC4owxsZI56YJ8BcUgJWjGNVisKPw/U9P0cScNMDBVO3t9X3vzJBtkgDn SWkxMTPTCdJdN8OskqajSwJwON36KDTsCI9a4l70=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Tim Bruijnzeels <tim@nlnetlabs.nl>
In-Reply-To: <a37c45f4-4cd0-7119-38d5-c5877b32de6b@verizon.net>
Date: Thu, 02 Jul 2020 12:27:14 +0200
Cc: sidrops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <27E6CC06-0375-467C-8F77-235A470FE3E6@nlnetlabs.nl>
References: <0365f842-ff05-b252-2fc7-f6f408fc52e3.ref@verizon.net> <0365f842-ff05-b252-2fc7-f6f408fc52e3@verizon.net> <20200701150648.GI85729@bench.sobornost.net> <a37c45f4-4cd0-7119-38d5-c5877b32de6b@verizon.net>
To: Stephen Kent <stkent=40verizon.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/AuhmU_Wqg7sleGKuHsg729d_uto>
Subject: Re: [Sidrops] 6486 bis
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: Thu, 02 Jul 2020 10:27:18 -0000

Hi,

> On 1 Jul 2020, at 19:49, Stephen Kent <stkent=40verizon.net@dmarc.ietf.org> wrote:
> 
> I have a question for the CA operators on the list. The manifest RFC calls out the possibility of using "one-time-use" manifests, in a few places (not in Section 6, which I have been revising). Does anyone make use of that "feature?" If not, I suggest we delete the discussion of this feature as part of the document revision.

Speaking for Krill - it *always* uses "one-time-use" EE certificates for Manifests, and for other RPKI signed objects for that matter.

Personally I would be happy with "one-time-use" being mandatory or RECOMMENDED.. I don't see any real advantage in multi-use. But, I understand this is another issue. It's not a big deal, although having one flavour only could potentially allow simplifying the text.

Tim


> 
> Steve
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops

v2.23.0 | Report a Bug | By Email