[174212] in North American Network Operators' Group
Re: Prefix hijacking, how to prevent and fix currently
daemon@ATHENA.MIT.EDU (Randy Bush)
Fri Aug 29 09:08:56 2014
X-Original-To: nanog@nanog.org
Date: Fri, 29 Aug 2014 22:08:45 +0900
From: Randy Bush <randy@psg.com>
To: Wes George <wesley.george@twcable.com>
In-Reply-To: <D025D6ED.2CE75%wesley.george@twcable.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
>> The long term solution is to deploy RPKI and only use
>> transits which use RPKI. No RPKI support => no business.
>> Additionally make RPKI a peering requirement.
> WG] So should we ask for that before, or after we get everyone to roll
> out IPv6 everywhere by voting with our wallets?
considering that measured rpki registration (which has a very tragic
side) is ten time ipv6 penetration, i think we ask for rpki first.
but keep shoveling. it's a good week for twt.
randy
