From 98e4f12efef27df42aad2d48a9772a7ef55ca707 Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Fri, 15 Apr 2022 14:00:38 -0700 Subject: [PATCH] =?UTF-8?q?=C3=89ric=20Vyncke=20nits?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- draft-ietf-sidrops-rpki-has-no-identity.xml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/draft-ietf-sidrops-rpki-has-no-identity.xml b/draft-ietf-sidrops-rpki-has-no-identity.xml index 176cd5a..d1573cd 100644 --- a/draft-ietf-sidrops-rpki-has-no-identity.xml +++ b/draft-ietf-sidrops-rpki-has-no-identity.xml @@ -49,8 +49,9 @@ There is a false notion that Internet Number Resources (INRs) in - the RPKI can be associated with the real-world identity of the 'holder' - of an INR. This document attempts to put that notion to rest. + the RPKI can be associated with the real-world identity of the + 'holder' of an INR. This document attempts to make clear that + notion is incorrect. @@ -93,11 +94,11 @@ It has been suggested that one could authenticate real-world business transactions with the signatures of INR holders. E.g. - Bill's Bait and Sushi could use the private key attesting to that - they are the holder of their AS in the RPKI to sign a Letter of - Authorization (LOA) for some other party to rack and stack hardware - owned by BB&S. Unfortunately, while this may be technically - possible, it is neither appropriate nor meaningful. + Bill's Bait and Sushi (BB&S) could use the private key attesting + to that they are the holder of their AS in the RPKI to sign a Letter + of Authorization (LOA) for some other party to rack and stack + hardware owned by BB&S. Unfortunately, while this may be + technically possible, it is neither appropriate nor meaningful. The I in RPKI actually stands for "Infrastructure," as in Resource Public Key Infrastructure, not for "Identity". In fact,