[75007] in North American Network Operators' Group
RE: IPv6 support for com/net zones on October 19, 2004
daemon@ATHENA.MIT.EDU (Hannigan, Martin)
Wed Oct 27 16:28:43 2004
From: "Hannigan, Martin" <hannigan@verisign.com>
To: "'Joe Abley'" <jabley@isc.org>
Cc: nanog@merit.edu
Date: Wed, 27 Oct 2004 16:28:04 -0400
Errors-To: owner-nanog-outgoing@merit.edu
Thanks Joe, great post re the /48's, I was just about to.=20
We're working on this.
-M<
--
Martin Hannigan (c) 617-388-2663
VeriSign, Inc. (w) 703-948-7018
Network Engineer IV Operations & Infrastructure
hannigan@verisign.com
> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf =
Of
> Joe Abley
> Sent: Wednesday, October 27, 2004 4:02 PM
> To: Daniel Roesen
> Cc: nanog@merit.edu
> Subject: Re: IPv6 support for com/net zones on October 19, 2004
>=20
>=20
>=20
>=20
> On 27 Oct 2004, at 15:43, Daniel Roesen wrote:
>=20
> >
> > 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.
>=20
> Since I mailed that, 3557 started receiving a covering /48=20
> for A. Maybe=20
> there's some operational/maintenance-induced stability issues=20
> for those=20
> paths.
>=20
> 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=20
> were always=20
> bad and should never be accepted by anybody. It's possible=20
> that this is=20
> biting Verisign, too.
>=20
> For the record, ARIN assign critical-infrastructure /48s which it is=20
> important to accept:
>=20
> http://www.arin.net/registration/ipv6/micro_alloc.html
>=20
> Gert D=F6ring maintains an excellent summary of current good=20
> practice for=20
> v6 filtering (including cisco and JUNOS configuration examples, and=20
> filters of various degrees of strictness) here:
>=20
> http://www.space.net/~gert/RIPE/ipv6-filters.html
>=20
> 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.
>=20
>=20
> Joe
>=20
