This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[db-wg] proposal: new attribute 'geofeed:'

Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
Next message (by thread): [db-wg] proposal: new attribute 'geofeed:'

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Randy Bush randy at psg.com
Wed Oct 7 16:03:23 CEST 2020

> - RIPE Database is set up to contain hierarchical data already. With this
> proposal, we would take some of this data outside the database in a manner
> that does not guarantee consistency with the database itself. For example,
> 192.168/16 specifies a geofeed file that has different prefixes in it than
> the children of said inetnum (or cover a range that is not even listed in
> the RIPE Database).

from the i-d

   When using data from a geofeed file, one MUST ignore data outside of
   the inetnum: object's inetnum: attribute's address range.

please read the draft

randy

Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
Next message (by thread): [db-wg] proposal: new attribute 'geofeed:'

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]