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/db-wg@ripe.net/
[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 ]
Randy Bush
randy at psg.com
Tue Feb 22 20:08:30 CET 2022
> The RFC says "Until such time...". We have a "geofeed:" attribute now > so we are past 'such time'. We should no longer even consider, or > support, "remarks:'' as an option for geofeed. you have the wrong end of the horse. it is the seeker/fetcher of geofeed data who decides whether they look inside remarks: and/or geofeed: attributes. repeat ten times: "remarks are opaque and their interpretation is only in the eye of the beholder." [0] randy 0 - an american legal joke about pornography. quoting bloomberg In a 1964 decision, U.S. Supreme Court Justice Potter Stewart said he would not attempt to define hard-core pornography, and “perhaps I could never succeed in intelligibly doing so.” He famously added, “But I know it when I see it.” --- randy at psg.com `gpg --locate-external-keys --auto-key-locate wkd randy at psg.com` signatures are back, thanks to dmarc header butchery
- 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 ]