Agoston,
I think that it's fine to help push adoption ahead of the IETF process.
The proposal is not super complicated (which is good). While possibly
the authentication details within the feed will change I don't think the
RPSL attribute will need to be modified from the current draft.
Cheers,
--
Shane
On 06/01/2021 17.59, Horváth Ágoston János via db-wg wrote:
Would it make sense to wait with implementation until the the ietf draft
comes out of draft status? Seems like jumping into beta waters to me.
Agoston
On Sun, Jan 3, 2021 at 8:22 PM Randy Bush via db-wg <db-wg@ripe.net
<mailto:db-wg@ripe.net>> wrote:
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/
<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
