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] geofeed issue: can't add geofeed attribute to PI /48
- Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
- Next message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Hessler
phessler at theapt.org
Fri Feb 25 07:48:24 CET 2022
On 2022 Feb 24 (Thu) at 16:48:57 +0100 (+0100), Edward Shryane via db-wg wrote: :i.e. for inetnum do *not* allow geofeed on assignments smaller than /24 (given the minimum allocation size), and for inet6num do *not* allow on (more specific, not top-level) assignments equal to or smaller than /48. I don't understand why /24 and /48 are different. In my view, they need to be the same. Alternatively, I propose we *drop* the geofeed: attribute and remove it from the database. -- Nothing cures insomnia like the realization that it's time to get up.
- Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
- Next message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]