Joe Clarke \(jclarke\) <[email protected]> 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 <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
