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] Fwd: proposal: new attribute 'geofeed:
- Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
- Next message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
hank at interall.co.il
hank at interall.co.il
Wed Jan 6 07:01:45 CET 2021
I guess I am not understanding something. Why do we need a geofeed attribute? What problem are we trying to solve? I understand why each block of IPs needs to be associated with a country, so that certain language specific auto-customizations will work. But what purpose is there to know that a /24 is in central Amsterdam? Is the purpose to assist marketers in geo-targetted sales? Is the purpose for network engineering (not sure what major problem we have that needs this)? Is the purpose to know where you are so that in the event of an emergency (terror, tornado, etc) you can get emergency targeted alerts? If so, then the geofeed has to be at the /32 level and since many if not most IPs are mobile, and that is where you will get the alert from - from your cellphone provider, I still don't quite understand the reason for a geofeed tag. Can someone clue me in? Thanks, Hank Caveat: The views expressed above are solely my own and do not express the views or opinions of my employer
- Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
- Next message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]