Re: IPV4 to IPv6 migration

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============2000844359==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig7399342E13556B884A26D7E1"

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

Mohsen Souissi wrote:
>  On 03 Jun, Jeroen Massar wrote:
>  | 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'
>  |=20
>  | SCTP & HIP. Please look at these.
>=20
> =3D=3D> Without any intention to revive an old controversy, and without=

> calling it an "API" per se, RFC2874 (A6, made experimental by RFC
> 3363) attempted to address that issue, at least partially.
>=20
> Still today, I don't think that the benefits of A6 outbalance its
> costs.

A6's are very useful to migrate a host quickly in DNS, as it avoids=20
'editting' a lot, but then existing connections would still break.
I don't see how A6 actually solves any problem, except where remote=20
entities are controlling prefixes which they delegate to customers;=20
updating A6 records does not update hosts though.


SCTP and HIP both handle that a host, during a session, renumbers and=20
keep the session alive, completely transparent to the application,=20
(unless it wants to know about it that is).

Greets,
  Jeroen


--------------enig7399342E13556B884A26D7E1
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)

iD8DBQFIRW2RKaooUjM+fCMRAmLBAJ4lL37CkRnWG+zt0vHpiFi15HkDNwCdHeaj
uz1jTL4Db2X5bYxUDa1CIHM=
=u29Y
-----END PGP SIGNATURE-----

--------------enig7399342E13556B884A26D7E1--

--===============2000844359==
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

--===============2000844359==--