IETF Logo Mail Archive

Re: [Sidrops] draft-ietf-sidrops-rpki-has-no-identity-00

Tim Bruijnzeels <tim@nlnetlabs.nl> Tue, 11 May 2021 15:03 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 F30C33A1ACA for <sidrops@ietfa.amsl.com>; Tue, 11 May 2021 08:03:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-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 vIQ_oc-nc0Gc for <sidrops@ietfa.amsl.com>; Tue, 11 May 2021 08:03:40 -0700 (PDT)
Received: from outbound.soverin.net (outbound.soverin.net [116.202.65.218]) (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 079E13A1AC1 for <sidrops@ietf.org>; Tue, 11 May 2021 08:03:39 -0700 (PDT)
Received: from smtp.soverin.net (unknown [10.10.3.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id 0AC7B60134; Tue, 11 May 2021 15:03:37 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [159.69.232.142]) by soverin.net
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nlnetlabs.nl; s=soverin; t=1620745416; bh=5J2k6KTUJF67eW/Snt7zI3iMOu+Gb6+30cx0hCiLSWw=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=f1gb5PxGHtndtWEPo0KX29g2AA+IiUfyYTheqt3VDYS03ConBgYSeME6eFV/h5tMM 6/6gwIcVDm743QhhUoz3Z6XSYftTA6XzdrB51F5rv+VzyP8zcfqB9sVB82K0h+/N8J 3xqzCtmObI/PHTbLOSzrAXX5+6PW4IUAB1PjRld/W8KggTO6hY3PsoKS8P2MRrmsoh JVCrNl9PeUlY6eNXhg25kIAys3jbeUazcma9P2rTl9R58DvZMELfvM8P9T9QHeUt6J TJ726kiUou2jlI+N3goGMShN1rIgc6DWxiL/72pvGJFkyp053EUtR8ZLXDRqpG2BY8 ZuqtLX/yuLxGg==
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Tim Bruijnzeels <tim@nlnetlabs.nl>
In-Reply-To: <m2wns5tj50.wl-randy@psg.com>
Date: Tue, 11 May 2021 17:03:33 +0200
Cc: SIDR Operations WG <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F69F473-EDC3-4038-A6E8-E0971DB96A2B@nlnetlabs.nl>
References: <m2k0o6uqot.wl-randy@psg.com> <CAKr6gn3oCZBOP3L8AQWvH9Nk4fum-ycZCnHO_DUtgdx5M=z_+A@mail.gmail.com> <m2fsyuuofa.wl-randy@psg.com> <CAKr6gn18yGTrAiqPA2P+kc+JBt2Tf8D-G4Gf5WCnASm8vk1Fvg@mail.gmail.com> <4455A207-2637-444B-BDA0-1209425C2EF2@vigilsec.com> <2D988AA2-7860-4F5E-B9D4-87A747A39FD2@nlnetlabs.nl> <41914016-4496-4FBC-A753-9481CAEDD231@vigilsec.com> <A8A5DE46-60E0-4C33-9BE8-8794C1C34819@nlnetlabs.nl> <m2wns5tj50.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/qMFwIKaTfSWMFMYQaH1i8EgxGYI>
Subject: Re: [Sidrops] draft-ietf-sidrops-rpki-has-no-identity-00
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, 11 May 2021 15:03:46 -0000


> On 11 May 2021, at 16:55, Randy Bush <randy@psg.com> wrote:
> 
> aside: "BPKI" has meaning in the RPKI internal protocols.  i have come
> to strongly suspect you are accidentally reusing this keyword for other
> meanings.

I agree.

BPKI is used in the context of provisioning (6492), publication (8181) and the out-of-band identity exchanges (8183).

We may not want to use the term in this context, or if we do then with proper clarity. This is not about the above RPKI internals.

Tim


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

v2.23.0 | Report a Bug | By Email