Re: [OPSAWG] Finding and Using Geofeed Data

Massimo Candela <massimo@us.ntt.net> Sun, 13 September 2020 18:09 UTC

Return-Path: <massimo@us.ntt.net>
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 16A943A0B19 for <opsawg@ietfa.amsl.com>; Sun, 13 Sep 2020 11:09:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level:
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.948, SPF_HELO_NONE=0.001, SPF_PASS=-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 CvS4zGamyJT7 for <opsawg@ietfa.amsl.com>; Sun, 13 Sep 2020 11:09:52 -0700 (PDT)
Received: from mail4.dllstx09.us.to.gin.ntt.net (mail4.dllstx09.us.to.gin.ntt.net [128.241.192.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E59F03A0B0E for <opsawg@ietf.org>; Sun, 13 Sep 2020 11:09:51 -0700 (PDT)
Received: from [192.168.2.16] (host-87-21-9-47.retail.telecomitalia.it [87.21.9.47]) by mail4.dllstx09.us.to.gin.ntt.net (Postfix) with ESMTPSA id 138D8EE014C; Sun, 13 Sep 2020 18:09:49 +0000 (UTC)
To: Randy Bush <randy@psg.com>, Joe Clarke <jclarke@cisco.com>
Cc: Ops Area WG <opsawg@ietf.org>
References: <8450cc78-8c60-ff7a-19f5-ea7335d262cd@us.ntt.net> <m25z8kdoqb.wl-randy@psg.com> <C65C82F2-E675-4D2A-A85D-9E3DAF453D77@cisco.com> <m2sgblbngx.wl-randy@psg.com>
From: Massimo Candela <massimo@us.ntt.net>
Message-ID: <f860f867-a8a1-82d0-813a-5d54e2479b3c@us.ntt.net>
Date: Sun, 13 Sep 2020 20:09:48 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <m2sgblbngx.wl-randy@psg.com>
Content-Type: text/plain; charset="iso-2022-jp"; format="flowed"; delsp="yes"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/1fqBx29B5G2MMyvqAUp673gmt4I>
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:09:53 -0000

Hi Joe,

Thanks for your feedback.

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


> 
>    o could there be a signal on the server side, e.g. an expiry or
>      suggested poll frequency in the geofeeds file or in the pointer in
>      the rpsl?  for example, massimo is looking at html tags.

What I'm loking at is http cache max-age headers.
Since the geofeed file is served on http(s), that's free to achieve  
(like for any other file).


Ciao,
Massimo