Hi John,
Thanks for the review.
On 13/02/2024 21:36, John Scudder via Datatracker wrote:
In RFC 9092 you have,
Any particular inetnum: object MUST have, at most, one geofeed
reference, whether a remarks: or a proper geofeed: attribute when it
is implemented. If there is more
No, I'm not aware of any IPR that applies to this draftMassimoOn Aug 7, 2023 15:20, "Joe Clarke (jclarke)" wrote:
Ahead of a call for WG adoption of draft-ymbk-opsawg-9092-update, we’d like to poll for known IPR.
Authors and contributors on the To: line, please respond on-list as to whether or
On 01/02/2021 20:16, Job Snijders wrote:
Conclusion
==
I believe with the above I've independently implemented all aspects of
draft-ietf-opsawg-finding-geofeeds in one way or another, demonstrating
the described procedures are correct, verifyable, and somewhat
understandable.
The
On 22/01/2021 22:47, Joe Clarke (jclarke) wrote:
Authors, contributors, and WG members, as we are in WGLC for this
document, we want to solicit knowledge of any IPR that may pertain to
the draft-ietf-opsawg-finding-geofeeds work.
Please state either, "no, I am not aware of any IPR that
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
Hi all,
IP geolocation is often essential but hard to correct when wrong, mostly
due to the lack of a unified way to provide geolocation data.
Internet operators may wish to publish the location of some
of their IP addresses. RFC 8805 (geofeeds) allows network operators
to publish "a mapping of
