[2078] in SIPB IPv6
Re: IPv6 at MIT
daemon@ATHENA.MIT.EDU (Daniel Jared Dominguez)
Thu Apr 13 19:02:52 2006
Date: Thu, 13 Apr 2006 19:02:40 -0400
From: Daniel Jared Dominguez <danjared@MIT.EDU>
To: Ken Raeburn <raeburn@mit.edu>, jis@mit.edu
Cc: sipbv6@mit.edu, Gregory D Troxel <gdt@mit.edu>
In-Reply-To: <9686B3B7-0841-4DC2-89A8-0BCE7816990B@mit.edu>
--E39vaYmALEf/7YXx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
(I'm cc'ing Jeff on this in case he has any more input.)
What technical obstacles to campus-wide IPv6 deployment exist? It seems
that--given the recent upgrades to the campus backbone a few weeks ago
and the measures needed to protect MITnet from the IPv6 exploit on Cisco
routers last year--that MITnet's backbone is IPv6 capable.
Are there many non-backbone routers on MITnet that aren't IPv6-ready? Is
IPv6 already carried on the NoX? Are there layer 9 issues?
Also, by tunnels, I'm assuming you mean only IPv6 tunnels and not those
in the 18.101/16 address space as well.
--Jared
On Thu, Apr 13, 2006 at 04:18:13PM -0400, Ken Raeburn wrote:
> So, I pinged Jeff again about what happens to IPv6 on campus when the =20
> 6bone goes away. Still no news, but he said (again) that he'd try to =20
> go talk to people about it.
>=20
> That's not to say that nothing's going to happen, but the possibility =20
> is certainly there. And my guess is, pretty likely, at least for =20
> 6/6/6. Also, even if IPv6 starts getting carried on the campus =20
> backbone by the network group, its official status may mean that the =20
> private off-campus tunnels that some of us have been playing with may =20
> simply go away.
>=20
> So I'd suggest that, if you care, you start looking elsewhere for a =20
> tunnel provider, or start playing with 6to4. (If you haven't given =20
> up on our 6bone setup and done so already, that is.)
>=20
> Ken
--=20
Daniel Jared Dominguez 617.368.0509 danjared@mit.edu
pika, 69 Chestnut Street, Cambridge Massachusetts 02139-4835
--E39vaYmALEf/7YXx
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (SunOS)
iEYEARECAAYFAkQ+2I8ACgkQfA6WwJdNltIyVACeJkOmm67HAz2m202XlryZCUWT
/mMAn2DTMvRhCTcA1ew1UY70RcPIqh31
=CAoe
-----END PGP SIGNATURE-----
--E39vaYmALEf/7YXx--
