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] 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
Sun Jan 3 20:22:25 CET 2021
hi cynthia >> Why not use the RPKI to distribute geofeed information? > > I think using RPKI for this will make it needlessly complicated for people > to use. I think we want to make this as simple as possible for someone to > find. as i said to job over on the dark side of the force, the ietf, hammer seeks nails, eh? :) geoseekers already mine whois. so we are putting the keys under the streetlight (excuse what may be an american-only idiom). asking someone who wants to publish their geofeed location to first deal with rpki is an artifical barrier to deployment. asking someone who wants to find geofeed data to first deal with rpki is an artificial barrier to deployment. is the rpki to be the next dns/bgp, a place to dump data? have we all looked at https://datatracker.ietf.org/doc/draft-ietf-opsawg-finding-geofeeds/ it's all pretty much layed out there, i hope. improvements solicited, of course. 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 ]