IETF Logo Mail Archive

Re: [Sidrops] 6486 bis

ntrenaman <ntrenaman@ripe.net> Fri, 03 July 2020 09:08 UTC

Return-Path: <ntrenaman@ripe.net>
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 129E63A0B2F; Fri, 3 Jul 2020 02:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 jLIuqUA9QL6m; Fri, 3 Jul 2020 02:08:48 -0700 (PDT)
Received: from molamola.ripe.net (molamola.ripe.net [IPv6:2001:67c:2e8:11::c100:1371]) (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 D0D873A0B2E; Fri, 3 Jul 2020 02:08:47 -0700 (PDT)
Received: from limalima.ripe.net ([193.0.19.81] helo=webmail.ripe.net) by molamola.ripe.net with esmtp (Exim 4.92.3) (envelope-from <ntrenaman@ripe.net>) id 1jrHgb-000B0W-TG; Fri, 03 Jul 2020 11:08:45 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Fri, 03 Jul 2020 11:08:45 +0200
From: ntrenaman <ntrenaman@ripe.net>
To: Stephen Kent <stkent=40verizon.net@dmarc.ietf.org>
Cc: sidrops@ietf.org
In-Reply-To: <a37c45f4-4cd0-7119-38d5-c5877b32de6b@verizon.net>
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>
User-Agent: Roundcube Webmail/1.4.0
Message-ID: <cba7d26b902ce945309246b153132515@ripe.net>
X-Sender: ntrenaman@ripe.net
X-ACL-Warn: Delaying message
X-RIPE-Signature: 18706c59bce47014ab71a1af93a0d016304a3cdffd1aab4eb76d84434bf72a63
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/GUWyCskhFcOTZ1ufK9i3KM_E748>
X-Mailman-Approved-At: Mon, 06 Jul 2020 08:32:44 -0700
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: Fri, 03 Jul 2020 09:42:54 -0000

Hi Steve,


On 2020-07-01 19:49, Stephen Kent wrote:
> Job,
> 
> Sorry for the delay. As Chris noted a few of us have been reviewing
> the changes before publishing.
> 
> 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.


Yes, we at RIPE NCC have only one-time-use certificates for manifests 
(since 2011).

Thanks,
Nathalie Trenaman
Routing Security Programme Manager
RIPE NCC

v2.30.2 | Report a Bug | By Email | System Status