Re: [OPSAWG] Finding and Using Geofeed Data

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 13 September 2020 18:35 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 240B33A0B53 for <opsawg@ietfa.amsl.com>; Sun, 13 Sep 2020 11:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 Z6Ydb0dtb3Wo for <opsawg@ietfa.amsl.com>; Sun, 13 Sep 2020 11:35:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF8763A0B52 for <opsawg@ietf.org>; Sun, 13 Sep 2020 11:35:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 12218389A5; Sun, 13 Sep 2020 14:14:39 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id i-0pwdhqk64T; Sun, 13 Sep 2020 14:14:34 -0400 (EDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:103c:9eff:fecb:2eac]) by tuna.sandelman.ca (Postfix) with ESMTP id 83E5A389A3; Sun, 13 Sep 2020 14:14:34 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C22FE75; Sun, 13 Sep 2020 14:35:48 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Joe Clarke (jclarke)" <jclarke=40cisco.com@dmarc.ietf.org>
cc: Randy Bush <randy@psg.com>, "opsawg@ietf.org" <opsawg@ietf.org>
In-Reply-To: <C65C82F2-E675-4D2A-A85D-9E3DAF453D77@cisco.com>
References: <8450cc78-8c60-ff7a-19f5-ea7335d262cd@us.ntt.net> <m25z8kdoqb.wl-randy@psg.com> <C65C82F2-E675-4D2A-A85D-9E3DAF453D77@cisco.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 13 Sep 2020 14:35:48 -0400
Message-ID: <17354.1600022148@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/nfmxIHl0AagJbpiUl4EIAGWj3og>
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: Sun, 13 Sep 2020 18:35:57 -0000

Joe Clarke \(jclarke\) <jclarke=40cisco.com@dmarc.ietf.org> wrote:
    > One thing that did stick out to me, though (and I don’t know how to
    > solve it) is when you talk about update frequency in section 5.  Okay,
    > don’t do frequent polls and don’t poll at midnight.  However, in the
    > case of something like the IETF conference network, how would consumers
    > know that this GeoFeed data _is_ likely to change and at a certain
    > periodicity?  The GeoFeed format doesn’t have any parsable way to
    > reflect that.  I don’t know if RPSL does.  Perhaps the remark: could
    > offer some clue as to when one might want to come and retaste?

Yes, I got the impression that Randy doesn't want to fix the geofeed specification.
If one were to do that, then a TTL on each line, or a notAfter date would work.

The problem with the IETF/etc. conference network isn't that we don't update
things, but that caches don't expire sanely.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide