Re: IPV4 to IPv6 migration

--===============1146951377==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="tYN2JrZK4u77A6TY"
Content-Disposition: inline


--tYN2JrZK4u77A6TY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Jun 03, 2008 at 08:32:00AM -0700, David Conrad wrote:
> On Jun 3, 2008, at 7:41 AM, Gert Doering wrote:
> >I'm not really sure what point you're trying to make, though...?
>=20
> In this particular context, nothing more complicated than the fact =20
> that the commonly used APIs (derived from the IPv4 APIs) promote and/=20
> or support particular coding patterns that forces applications to deal =
=20
> with renumbering events, thereby making renumbering disruptive.  In =20
> this way, IPv6 is approximately the same as IPv4 in terms of =20
> renumbering, something I find unfortunate.

I'm not sure I agree.  For a many application, I see code more along=20
the lines of

open_connection()
   getaddrinfo()
   while( try all addresss )
       if ( connect works, break loop, return socket )

(which is the sample loop from the getaddrinfo RFC, IIR) - where the=20
application usually does not cache anything.

I'm actually not *that* happy with this loop, as it's not very practical
if there are multiple destination IP addresses, some of which do not=20
return errors right away but need to time out - but *caching* isn't the
problem...

Servers explicitely bind() ing to addresses are a problem indeed, but
there's no hard need to do so, unless for UDP servers.

Gert Doering
        -- NetMaster
--=20
Total number of prefixes smaller than registry allocations:  110584

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

--tYN2JrZK4u77A6TY
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iQCVAwUBSEVoLakuBuNlUUl1AQJt2gP/dx8OOxMW9BmKYXx/Q/gQwudKFmrqzjLH
b1uznZ+MwExbWkqWCL9QWKq5tkPPzP6lXMch+41aEuGAcuslL7dgkQSetTrOpIqc
9zJrV4Mii/ulIYN4Qi1sq2NajjqTkCSnYj4nsW9AhRT2U1ZVTAOA8DJkxU4lLUSK
Mi+/BZ7Co4E=
=P3Gr
-----END PGP SIGNATURE-----

--tYN2JrZK4u77A6TY--

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

--===============1146951377==--