Colleagues
The discussion and agreement of the text for a new purpose for the
RIPE Database covering geolocation was done by the RIPE NCC and it's
executive board. They refused to publish the text in advance, didn't
announce that the board had agreed to it or that the T&C document has
been updated
Hello all,
As you may have seen in the minutes from the RIPE NCC Executive Board's
most recent meeting (on 6 October 2023), the Executive Board approved
the amendments to the RIPE Database Terms and Conditions.
The RIPE Database Working Group had reached consensus that the provision of
geolocati
Hi Denis,
That text seems fine to me. I think the key point is "publishing
geolocation information", which allows the wider public to get access.
My main question is basically: once the new T&C is announced are we
then allowed to add geolocation information, specifically the geofeed
attribute, t
I agree with Peter.
I assume the NCC legal team thinks this is what is needed to allow for
geofeeds for /48s and such, and if so I am happy with that.
-Cynthia
On Thu, Nov 2, 2023 at 10:03 PM Peter Hessler via db-wg wrote:
>
> Hi Denis,
>
> That text seems fine to me. I think the key point is "
Colleagues
As Maria said, we now have a new defined purpose explicitly related to
geofeed. Ed has confirmed that the prefix size restrictions have been
removed. Does anyone think there is still anything outstanding
regarding the implementation, deployment and use of geofeed? In
particular regardin
