Re: [Sidrops] AD Review of: draft-ietf-sidrops-rpki-has-no-identity

Warren Kumari <warren@kumari.net> Thu, 03 March 2022 16:01 UTC

Return-Path: <warren@kumari.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 857233A0D62 for <sidrops@ietfa.amsl.com>; Thu, 3 Mar 2022 08:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari.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 ntzHr6a4j5CK for <sidrops@ietfa.amsl.com>; Thu, 3 Mar 2022 08:01:51 -0800 (PST)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA0D23A0D9E for <sidrops@ietf.org>; Thu, 3 Mar 2022 08:01:50 -0800 (PST)
Received: by mail-il1-x12e.google.com with SMTP id j5so4383461ila.2 for <sidrops@ietf.org>; Thu, 03 Mar 2022 08:01:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yibGBtPnPfZBVqsiHh6G5Zg0MviLglaoOtEkBTM7mEM=; b=Q/xzLAoBsoAJsUryi5HD2g/eB3CYiqQhDSDtEZ9bMss8x8tAX9UxhIIW7H3iJN5FtW gaCgrWWlWzJd9kD8Yo5mdykXa/1Ezjm1/db9vcaZz3XUZl68UPoJ28u1RgI5KBLRU+1G 1RUQTMGbWpYEGvqPW/DKFLAAvklu8JCuXar2dFXe1MKq+LnTlvXXQfDozZviwsK6V9a1 mDl74hcB3Hz84VjiqCJaUy50Lz2xJ9TZns6UqFhQZLlQdepQTTxnRSokULWUTIoQAZfw LlAI8oTES01cqMsdr4m30ybChMBBOqO44AXR9GKCaDL0T3aYgYFhGM76eEdrm0A+QeJO /L4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yibGBtPnPfZBVqsiHh6G5Zg0MviLglaoOtEkBTM7mEM=; b=l8RT0PgPt3uLiXXPPE+3HCzFrRYDmi4rOXTZkT/obUAljeCo9KYR4a1MjtcXJSMdwP 94B/DqW/0nCTpoEve2+D3oEOS5tXXZu+bVg0ACgiHRWcr0IsvzHGnmwCVhCIZsI08SBi Se5l8+/Dbtf5EnBLGVRJ1wKXti40cy0ri6oU9Eu3E5qkwp6KSNwive2HBYAVe9+ab8D6 /Zy0cpCzKce8rKL4SmvG/KhS71Evn/kvVbfd6V1SFkRK49/9O0pcte7QPucpxHmbHSk5 WVOdgHlHHahwS+49EFCMMqQu8W1hGYNgPRgmC2PVmV2pdWOauNu+ezfpP2yZM2/Hn68b GnrQ==
X-Gm-Message-State: AOAM533qMuxb2u3LvJGiLYBJE1C2G0dZsdBE1/tEkmfResjX4DYUIqpE 5EfDBJhUa/X2deYdCW9wRyyyYeluecs80KGoxM/a5tw+adc=
X-Google-Smtp-Source: ABdhPJyaHbOee+hSrS/0oRmQAn7AK36EXc7zSuH3zrwDvk+Uzq0ZNCXz0v1uK3VdWlSWT2bTdCY0XuQR8jJG6E1VntI=
X-Received: by 2002:a92:ca47:0:b0:2c2:ab28:1163 with SMTP id q7-20020a92ca47000000b002c2ab281163mr28584982ilo.260.1646323309075; Thu, 03 Mar 2022 08:01:49 -0800 (PST)
MIME-Version: 1.0
References: <CAHw9_i+Ti0ghT7C+UMVSR2Xjc2ynPxoe3Q4wUDFCaci88-TRaA@mail.gmail.com> <1C80C283-B3B4-41C4-B983-95C7B1775A5C@vigilsec.com>
In-Reply-To: <1C80C283-B3B4-41C4-B983-95C7B1775A5C@vigilsec.com>
From: Warren Kumari <warren@kumari.net>
Date: Thu, 3 Mar 2022 11:01:13 -0500
Message-ID: <CAHw9_i+dikUSVvLOXxyqJ5Q=umA3gO1sVYBGeJE5WP_aYicdEQ@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: SIDR Operations WG <sidrops@ietf.org>, draft-ietf-sidrops-rpki-has-no-identity@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000602b505d95284b6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/qiuceORRUEs76RxzPCc411PexFQ>
Subject: Re: [Sidrops] AD Review of: draft-ietf-sidrops-rpki-has-no-identity
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: Thu, 03 Mar 2022 16:01:56 -0000

On Thu, Mar 3, 2022 at 10:52 AM Russ Housley <housley@vigilsec.com> wrote:

> Warren:
>
> Thanks for the review.
>
> > Firstly, thank you very much for this document, and apologies it has
> taken a while for me to review it.
> >
> > I must admit that I *wanted* to / felt I should be able to use the RPKI
> to do things like sign LOAs and similar "the RIR says I'm the 'owner', seem
> mah cert!" type things, and so, even though the document makes me sad, it's
> useful and needed.
> >
> > I do have a number of editorial comments / nits. Addressing these
> > before IETF LC and IESG review should make progressing the document
> > easier and smoother, as well as being politer to the RFC Editor.
> >
> > Please let me know LOUDLY once you'd had a chance to address them, and
> I'll start IETF LC.
> >
> > Issues / comments:
> > Sec 1:
> > O: "Though since, it has grown to include..."
> > C: I don't have suggested text, but "Though since" is difficult to
> > parse -- it's not clear from the prior sentence what the "though" or
> > "since" refer to. Perhaps "Since publication of [RFC6480], the term has
> grown
> > to include ..."? Actually, I'm not really sure what the sentence was
> trying to
> > say though, so I have no idea if my suggestion works...
>
> I suggest: "Since initial deployment, the RPKI has grown to include ..."
>

Perfect.


>
> > Nits:
> > Sec 1:
> > O: "In security terms the phrase "Public Key"... "
> > P: "In security terms, the phrase "Public Key"  ..."
> > C: Comma.
> >
> > O: "But in reality, the RPKI certificate is only an
> >    authorization to speak for for the explicitly identified INRs;"
> > P: "But in reality, the RPKI certificate is only an
> >    authorization to speak for the explicitly identified INRs;"
> > C: Repeated 'for'
> >
> > Sec 2:
> > O: "Registries such as the Regional Internet Resistries (RIRs)"
> > P: "Registries such as the Regional Internet Registries (RIRs)"
> > C: Typo
> >
> > O: "That the RPKI does not authenticate real world identity is a feature
> >    not a bug."
> > P: "That the RPKI does not authenticate real world identity is a feature,
> >    not a bug "
> > C: Comma
>
> The above suggestions seem fine to me.
>

Thanks!


>
> > O: "Note that, if there is sufficient external, i.e. non-RPKI,
> >    verifcation of authority"
> > P: Note that, if there is sufficient external, i.e. non-RPKI,
> >    verification of authority"
> > C: Typo
>
> Suggestion for the whole paragraph:
>
>    Given sufficient external, i.e. non-RPKI, verification of authority,
>    the use of RPKI-based credentials seems superfluous.
>

Grteat!


>
> > Sec 4:
> > O: "When a document is signed with the private key associated with a RPKI
> >    certificate"
> > P: "When a document is signed with the private key associated with a RPKI
> >    certificate"
> > C: s/a/an/ - grammar
>
> I can see this one either way.
>

Me too; I don't really care / whatever you want...


>
> >
> >  Misc:
> >  s/real world/real-world/g -- I think?
>
> If you mean in Sec 2:
>         s/real world identity/real-world identity/
>         s/real world documents/real-world documents/


There are 12 "real world" instances -- I think that the hyphenated version
is cleaner (and some random grammar tool seems to agree), but again, I
don't really care. Whatever y'all think.
W


>
> Russ
>
>

-- 
The computing scientist’s main challenge is not to get confused by the
complexities of his own making.
  -- E. W. Dijkstra