[175549] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

ARIN / RIR Pragmatism (WAS: Re: RADB)

daemon@ATHENA.MIT.EDU (Danny McPherson)
Thu Oct 23 14:26:58 2014

X-Original-To: nanog@nanog.org
Date: Thu, 23 Oct 2014 12:26:50 -0600
From: Danny McPherson <danny@tcb.net>
To: <nanog@nanog.org>
In-Reply-To: <CALB2hAcLCKfRXt4ugK_SRNaEddzB7R9bVp7armf9XMjuDXjqOw@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org

<soapbox>

I think the routing system would be in a much happier [less bad] place 
if only had a minor amount of the energy and resources that USG (and 
RIRs) have been put towards RPKI and BGPSEC (i.e., IETF SIDR work) would 
have been redirected to lower hanging fruit and better recognizing / 
leveraging existent systems and operational practices (e.g., more IRR 
usage, training, tools, and better hygiene, perhaps expressly validated 
from resource certification from either RPKI or in-addr.arpa, etc).  
Given that many of the same derived "policies" there could also be 
employed for inter-domain datapath anti-spoofing (BCP38-ish 
inter-domain) and that all the existing machinery and practices already 
deployed could more easily accommodate this in the near term, it seems 
only natural to me.

As for the visionaries playing the long game, they've made progress, 
but surely the only way to get there is with more incremental "putty" 
and small practical steps to fill the gaps at this point.

</soapbox>

I for one would like to see ARIN (as well as other RIRs and the 
adjacent community) invest more pragmatically in this area, particularly 
given the governance climate and other externalities at play these days.

Alas,

-danny



home help back first fref pref prev next nref lref last post