[75006] in North American Network Operators' Group
Re: IPv6 support for com/net zones on October 19, 2004
daemon@ATHENA.MIT.EDU (Joe Abley)
Wed Oct 27 16:02:58 2004
In-Reply-To: <20041027194308.GA19240@srv01.cluenet.de>
Cc: nanog@merit.edu
From: Joe Abley <jabley@isc.org>
Date: Wed, 27 Oct 2004 16:01:45 -0400
To: Daniel Roesen <dr@cluenet.de>
Errors-To: owner-nanog-outgoing@merit.edu
On 27 Oct 2004, at 15:43, Daniel Roesen wrote:
>
> On Wed, Oct 27, 2004 at 03:21:44PM -0400, Joe Abley wrote:
>> Maybe Verisign needs more (reliable) v6 transit.
>
> Something is broken in several colors here. I'm seeing AS_PATHs
> like 6830 6175 109 7018 26415 (Sprint, Cisco, AT&T, Verisign) but
> a traceroute is going straight from 6830 to AT&T and dying there
> with !P.
>
> That you have no route for A is most probably a filtering issue
> somewhere... I'm seeing it being propagated by Sprint.
Since I mailed that, 3557 started receiving a covering /48 for A. Maybe=20=
there's some operational/maintenance-induced stability issues for those=20=
paths.
We've had reports before of F's covering /48 (2001:500::/48) being=20
filtered by some people, based on the conviction that /48s were always=20=
bad and should never be accepted by anybody. It's possible that this is=20=
biting Verisign, too.
For the record, ARIN assign critical-infrastructure /48s which it is=20
important to accept:
http://www.arin.net/registration/ipv6/micro_alloc.html
Gert D=F6ring maintains an excellent summary of current good practice =
for=20
v6 filtering (including cisco and JUNOS configuration examples, and=20
filters of various degrees of strictness) here:
http://www.space.net/~gert/RIPE/ipv6-filters.html
Operators who are currently blocking any prefix covered by 2001::/16=20
which is longer than 32 bits are encouraged to review that page, and=20
fix their routers.
Joe=
