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

[Ties de Kock <[e-mail]>]

Hi Randy,

> On 8 Aug 2021, at 22:43, Randy Bush <[e-mail]> wrote:
> 
> my (always suspect) memory on this one is that, when it was first
> published, there was a lot of discussion exacerbated by some lack of
> clarity.  this was cleaned up when we made clear that we were not
> attacking RTA or RSC, only warning of potential misuse.  so it was
> adopted as a wg document.

First of all: I like the draft and it demonstrates some problem with using the
RPKI for external attestations really well.

> 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.

Kind regards,
Ties