Re: [Sidrops] I-D Action: draft-ietf-sidrops-rpki-has-no-identity-01.txt

Ties de Kock <tdekock@ripe.net> Wed, 11 August 2021 07:19 UTC

Return-Path: <tdekock@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 422553A0112 for <sidrops@ietfa.amsl.com>; Wed, 11 Aug 2021 00:19:27 -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 (2048-bit key) header.d=ripe.net
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 P2-ojd239tuj for <sidrops@ietfa.amsl.com>; Wed, 11 Aug 2021 00:19:20 -0700 (PDT)
Received: from mahimahi.ripe.net (mahimahi.ripe.net [IPv6:2001:67c:2e8:11::c100:1372]) (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 164BA3A011F for <sidrops@ietf.org>; Wed, 11 Aug 2021 00:19:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ripe.net; s=s1-ripe-net; h=To:Message-Id:Cc:Date:From:Subject:Mime-Version:Content-Type ; bh=Lst3BluX/maOfJhbSPVmWoLidbq0Kyo5PPUwd18ZRyw=; b=httEE7eZc9kbyZTLDSoHqaM8 1n1jn8TO+ANTkauViwm2/IRWVRXfI2TNTYU2pcYdi5yUYrLf1FsuV+ZbVdsTi45GXsIB7P2JeTfBO Pg1cxTisJcpWlzp+rr/zIP8mT28Dsa6W+ovEwMl3DBU8G/IfYU/He6QsWvge4zX/spnA2hkepe/Y2 Od64zhjgY09q4rLYM1iVKC3068O6hCSMspWSHwvf5gMIGqOzqQKM6JaYlsOrJi7VhtzsJiMj5o6tx J7RPf4ATt/1Q9/mqHpjBmFfFg6zKhMTgSszvpzLK8ALGBBb/uF67AGNDmG1FJT3xuuj9uyy1wAuWm NZCX0cJoIg==;
Received: from allealle.ripe.net ([2001:67c:2e8:23::c100:170c]:38998) by mahimahi.ripe.net with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <tdekock@ripe.net>) id 1mDiW8-0002Zt-A2; Wed, 11 Aug 2021 09:19:12 +0200
Received: from sslvpn.ipv6.ripe.net ([2001:67c:2e8:9::c100:14e6] helo=smtpclient.apple) by allealle.ripe.net with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <tdekock@ripe.net>) id 1mDiW8-0002z8-7J; Wed, 11 Aug 2021 09:19:12 +0200
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Ties de Kock <tdekock@ripe.net>
In-Reply-To: <m2v94ck5zr.wl-randy@psg.com>
Date: Wed, 11 Aug 2021 09:19:11 +0200
Cc: SIDR Operations WG <sidrops@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <9727EFC1-D132-4E25-B2F0-7852C67766E2@ripe.net>
References: <162845509942.28236.7404410032742481217@ietfa.amsl.com> <m2bl671xbk.wl-randy@psg.com> <76BFDB10-2FE5-4FBD-8E16-8104CBE3D86C@ripe.net> <m25ywemmn5.wl-randy@psg.com> <8170EFA9-8832-4B7A-816D-9829790C23FA@ripe.net> <m2v94ck5zr.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-RIPE-Signature: 059faafd1cc22ebb05e1592c815fe1e1b6df362ba33711cb631c8c62476da976
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/ZgFJjMsgt1iZJjny6aBUT_wwJLo>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-rpki-has-no-identity-01.txt
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: Wed, 11 Aug 2021 07:19:27 -0000

On 11 Aug 2021, at 05:36, Randy Bush <randy@psg.com> wrote:
> 
>> I was thinking about the situation where an actor uses an RPKI object
>> to lead people to believe they have legal authority to sign contracts
>> concerning the resources.
>> 
>> RPKI does not have identity but it does not imply being an legal
>> representative either? I was wondering if we needed to clarify that as
>> well.
> 
> so you want something such as
> 
>    That someone can provide 'proof of possession' of the private key
>    signing over a particular INR should not be taken to imply that they
>    are a valid legal representative of the organization in possession
>    of that INR.  They could be just an INR administrative person.

I think that looks good!

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