[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 ]
Massimo Candela
massimo at ntt.net
Mon Feb 21 16:29:13 CET 2022
Hi Ed, Thanks for the work done. On 21/02/2022 15:56, Edward Shryane via db-wg wrote: > We will also start enforcing the same validation on "remarks: geofeed" as on "geofeed:" for consistency. I think you should not enforce anything on remarks. For what I know, remarks have been a free text field up to now. In my view: (1) RIPE NCC promotes the "geofeed" field for the geofeed purpose, instead, using "remarks" it is not the practice suggested by RIPE NCC and so I don't believe it is RIPE NCC's responsibility; (2) Users can always encode the same information in remarks without geofeed (which would just increase the mess and bypass the check); (3) starting to validate the content of remarks creates a precedent in which RIPE NCC is responsible for checking remarks content (possibly, in the future, not only about geofeeds). But I don't know anything about legal things, so this is just my point of view. Ciao, Massimo > > Please let us know what you think. We would like to implement these changes soon and include them in a new Whois release 1.103. > > Regards > Ed Shryane > RIPE NCC > > >> On 3 Jan 2022, at 13:36, Job Snijders via db-wg <db-wg at ripe.net> wrote: >> >> Dear all, >> >> Like all good netizens, I tried to align information I publish in the >> RIPE database to reality, but there is an obstacle: >> >> https://sobornost.net/~job/geofeed.png >> >> """Adding or modifying the "geofeed:" attribute of an object with a >> prefix length greater or equal to 48 is not allowed.""" >> >> No such restriction exists if you use the 'remarks: Geofeed' approach, >> as demonstrated here: >> >> $ whois -h whois.ripe.net 2001:67c:208c::/48 | grep Geofeed >> remarks: Geofeed https://sobornost.net/geofeed.csv >> >> I appreciate concerns about privacy, but I'm not wholly convinced >> restricting /48s from having a proper 'geofeed:' attribute is the best >> path forward. >> >> How does the working group feel about this restriction? Is it useful? >> Should it be lifted? If the latter, what would be the process? >> >> Kind regards, >> >> Job >> >> -- >> >> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg > >
- 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 ]