Re: IPV4 to IPv6 migration

Jeroen Massar <jeroen-LqLoW1FB7k/[email protected]> Tue, 03 Jun 2008 16:00:35 +0200
Newsgroups gmane.org.apnic.global-v6
Organization Unfix
Message-ID <[email protected]>
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1184826803==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig9D276BE3E12A31661F5A2736"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9D276BE3E12A31661F5A2736
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

David Conrad wrote:
[..]
> It's a bit sad that we didn't take the opportunity to define a new API =
=20
> that would return 'network handles'

SCTP & HIP. Please look at these.

IP is just for sending packets from A to B.

TCP was (afaik, as I am far from old enough ;) created just to send=20
packets to two hosts as long as they can talk to each other. UDP the=20
same. At that time nobody renumbered as as one just got a /8 and=20
expected never to do this.

SCTP was created to avoid all those problems during renumbering as the=20
hosts can notify each other where they are going to (and other cool=20
features).

HIP was created just to avoid the whole debacle completely from the=20
start, using HIP's instead of IP's.


Now the big problem is, how do you get programmers to start adding SCTP=20
and/or HIP support to all their programs... Apache/IIS/Lighttpd don't=20
support SCTP, and Firefox/Safari/IE don't support it either. That is the =

first step to take. But like IPv6, they are adding something new, and=20
that might cause issues and delays when trying to use those protocols,=20
thus they most likely rather not. Also, especially in the case of HTTP,=20
the connections are shortlived and load-balancer work fine already with=20
TCP/HTTP, those and a lot of other gear also needs to start supporting=20
SCTP/HTTP then all of a sudden. Like IPv6 this is another nice=20
chicken/egg issue. One advantage here is that you just have to touch the =

endhosts and not the routing infrastructure.


Oh and indeed before you ask SCTP and/or HIP solve a part of the=20
multihoming riddle too. They just don't solve the "I need this traffic=20
to go this fast and there and here" and other such tricks.

Greets,
  Jeroen


--------------enig9D276BE3E12A31661F5A2736
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFIRU6DKaooUjM+fCMRAm6WAKCmZAFRNNdu/ArqaawirVdCxO1m0wCfQN1P
JIsv3aMhlzShQ+9s1/btcEg=
=io5B
-----END PGP SIGNATURE-----

--------------enig9D276BE3E12A31661F5A2736--

--===============1184826803==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
global-v6 mailing list
[email protected]
http://mailman.apnic.net/mailman/listinfo/global-v6

--===============1184826803==--