[arin-ppml] IPv4 Transfer Policy Change to Keep Whois Accurate
owen at delong.com
Tue May 24 12:37:18 EDT 2011
On May 24, 2011, at 8:31 AM, Matthew Kaufman wrote:
> On May 24, 2011, at 5:17 PM, Kevin Kargel wrote:
>> All the talk of ARIN controlling netblocks and routing is really obfuscation. If anyone doesn't like the way ARIN manages the database all they really have to do is maintain their own database. (Sounds simple, doesn't it..)
> It would be easier if ARIN bulk transfer rules didn't prohibit bulk transfer for this purpose.
Ah, but, why should ARIN make it easier to hijack the community's resources, which is the
net effect of allowing such bulk transfers?
>> So long as you and all the parties you wish to communicate with are using the same database life is good.
>> What I suspect would be the biggest problem if a network did maintain their own database is that when their non-aligned peers discover they are using a different database then those non-aligned peers will stop accepting routing advertisements from the network. This has happened to networks in the past when network operators have had incorrect routes in their tables whether by intention or typo. To keep life simple and reduce my workload I choose to be represented in the ARIN database and follow the rules that go along with that.
> This will get much much more interesting if/when RPKI happens. And even more interesting if some jurisdiction requires the use of it.
Yep. I don't expect that to be at all likely, and, there's nothing dictating which trust anchors any given
network does or does not accept even when they do RPKI.
> Matthew Kaufman
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.
More information about the ARIN-PPML