Re: [OPSAWG] Finding and Using Geofeed Data

Randy Bush <randy@psg.com> Sat, 12 September 2020 06:02 UTC

Return-Path: <randy@psg.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D96F3A0D8E for <opsawg@ietfa.amsl.com>; Fri, 11 Sep 2020 23:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=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 HU0pUNqlrrm2 for <opsawg@ietfa.amsl.com>; Fri, 11 Sep 2020 23:02:01 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [198.180.150.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 41EAD3A0D8C for <opsawg@ietf.org>; Fri, 11 Sep 2020 23:02:01 -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 1kGybm-0005hI-CQ; Sat, 12 Sep 2020 06:01:58 +0000
Date: Fri, 11 Sep 2020 23:01:57 -0700
Message-ID: <m2pn6rcz3e.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Erik Kline <ek.ietf@gmail.com>
Cc: Massimo Candela <massimo@us.ntt.net>, opsawg@ietf.org
In-Reply-To: <CAMGpriXQ40z0secjMho1RCUcXWzbrL4u6CH5eK+YvugPtN4zLg@mail.gmail.com>
References: <8450cc78-8c60-ff7a-19f5-ea7335d262cd@us.ntt.net> <m25z8kdoqb.wl-randy@psg.com> <CAMGpriXQ40z0secjMho1RCUcXWzbrL4u6CH5eK+YvugPtN4zLg@mail.gmail.com>
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: multipart/mixed; boundary="Multipart_Fri_Sep_11_23:01:56_2020-1"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/eofLjvq3ggM0zPTFYzG3i_wLUDg>
Subject: Re: [OPSAWG] Finding and Using Geofeed Data
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2020 06:02:05 -0000

thanks for review!  proposed diff attached.

>   If the comments change, the signature changes?

yep.  otherwise vast complexity lurks.  but is there a text change you
want?  i may be naïve expecting that "a digest of the main body of the
file" is sufficient.

>     [a] the source of the geofeed claims is authoritative to make said
>         claims for the contained prefixes, and

iff you trust the rpki crypto chain

>     [b] the correctness of the claims themselves (i.e. that the location of
>         2001:db8::/32 really is "Shire, Middle Earth").

above my pay grade

do you have suggested text?

>   The text from section 4 provides a suggestion: perhaps replace
>   "authenticate" with "verify the authority of", or some such
>   formulation?

hmmmm.  hacked a bit.

> [ section 1 ]
> 
> * Probably the intro should hint at the authentication awesomeness contained
>   within.  I think, actually, the last paragraph of section 2 can just be
>   relocated to the end of this section and it will flow well.

ok

> [[ nits ]]

thanks!

randy