[76023] in North American Network Operators' Group
Re: who gets a /32 [Re: IPV6 renumbering painless?]
daemon@ATHENA.MIT.EDU (Owen DeLong)
Mon Nov 29 22:33:59 2004
Date: Mon, 29 Nov 2004 19:31:08 -0800
From: Owen DeLong <owen@delong.com>
To: Barney Wolff <barney@databus.com>
Cc: Andre Oppermann <nanog-list@nrg4u.com>,
Paul Vixie <vixie@vix.com>, nanog@merit.edu
In-Reply-To: <20041130022319.GA72279@pit.databus.com>
Errors-To: owner-nanog-outgoing@merit.edu
--==========5BA504A2F15BEECAFB58==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
>
> But old-style tcp apps don't work with ipv6 either. So if you're going
> to demand binary compatibility, all the mechanics need to get done below
> the app anyway.
>
Actually, on some systems, the appear to work just fine, or, at least the
authors have already coded v6 support in. In an ideal world, yes, the app.
shouldn't have to know anything below layer 4.
> It would have been nice to make sctp be the standard stream protocol for
> ipv6. For most nanog customers, there's still time. Those places that
> have already seen significant ipv6 adoption may need to upgrade again.
> If we wait much longer, of course, the opportunity will be lost. To
> argue that it's already too late, when ipv6 is a small fraction of all
> traffic and an infinitesmal fraction of future traffic is, imho, foolish.
May not be too late, but, doesn't appear to be catching on well enough to
prevent it.
Owen
--==========5BA504A2F15BEECAFB58==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFBq+l8n5zKWQ/iqj0RAvZSAJ0fKDmCjyv5TdP1hyCogelbBy4j+ACfeVjA
FPlR23yhh8mP614LEj4RwZY=
=t0X9
-----END PGP SIGNATURE-----
--==========5BA504A2F15BEECAFB58==========--
