I just reviewed rev -02. Other than noticing two ’s’ in “objects” in section 5, I didn’t notice any other issues.
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? Joe > On Sep 11, 2020, at 16:48, Randy Bush <[email protected]> wrote: > > would appreciate review prior to calling for wg adoption > > thanks > > randy > > A new version of I-D, draft-ymbk-opsawg-finding-geofeeds-02.txt > has been successfully submitted by Randy Bush and posted to the > IETF repository. > > Name: draft-ymbk-opsawg-finding-geofeeds > Revision: 02 > Title: Finding and Using Geofeed Data > Document date: 2020-09-11 > Group: Individual Submission > Pages: 16 > URL: > https://www.ietf.org/id/draft-ymbk-opsawg-finding-geofeeds-02.txt > Status: > https://datatracker.ietf.org/doc/draft-ymbk-opsawg-finding-geofeeds/ > Htmlized: > https://datatracker.ietf.org/doc/html/draft-ymbk-opsawg-finding-geofeeds > Htmlized: > https://tools.ietf.org/html/draft-ymbk-opsawg-finding-geofeeds-02 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-ymbk-opsawg-finding-geofeeds-02 > > Abstract: > This document describes how to find and authenticate geofeed data. > > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
