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

Randy Bush <randy@psg.com> Mon, 09 August 2021 19:41 UTC

Return-Path: <randy@psg.com>
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 CBF053A148F for <sidrops@ietfa.amsl.com>; Mon, 9 Aug 2021 12:41:26 -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 LJtNBTl2TNmO for <sidrops@ietfa.amsl.com>; Mon, 9 Aug 2021 12:41:22 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 BD4D53A1481 for <sidrops@ietf.org>; Mon, 9 Aug 2021 12:41:21 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1mDB9D-00071c-4P; Mon, 09 Aug 2021 19:41:19 +0000
Date: Mon, 09 Aug 2021 12:41:18 -0700
Message-ID: <m25ywemmn5.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ties de Kock <tdekock@ripe.net>
Cc: SIDR Operations WG <sidrops@ietf.org>
In-Reply-To: <76BFDB10-2FE5-4FBD-8E16-8104CBE3D86C@ripe.net>
References: <162845509942.28236.7404410032742481217@ietfa.amsl.com> <m2bl671xbk.wl-randy@psg.com> <76BFDB10-2FE5-4FBD-8E16-8104CBE3D86C@ripe.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="ISO-2022-JP"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/XWie8Uonb9I3wpTfIfplYCn-_hk>
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: Mon, 09 Aug 2021 19:41:35 -0000

>> In large organizations, INR management is often compartmentalized
>> with no authority over anything beyond dealing with INR registration.
>> The INR manager for Bill's Bait and Sushi is unlikely to be
>> authorized to conduct bank transactions for BB&S, or even to
>> authorize access to BB&S's servers in some colocation facility.
> 
> About this paragraph: This may even need to be more specific.
> 
> I think that the department performing INR _management_ often may not
> even have legal authority to change INR _registration_s. I imagine a
> department that can change the data related to the INR registration
> (“update the ROAs”) but not manage the INR registration (“garage sale
> of the IPv4”).
> 
> For the latter you (hopefully) need legal signing power.

yes, but ...

i do not see where rsc/mta/... and folk wanting to sign bank statements
with registry data are asking to change the registry database.  clue
bat, please.

randy