Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Mar 2008 21:41:40 +1100
From:      Peter Jeremy <peterjeremy@optushome.com.au>
To:        Ruben van Staveren <ruben@verweg.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: INET6 -- and why I don't use it
Message-ID:  <20080306104139.GX68971@server.vk2pj.dyndns.org>
In-Reply-To: <CECD0714-5625-49A6-BC2A-0DEF0AB56A98@verweg.com>
References:  <20080306061339.3CE2C4500E@ptavv.es.net> <CECD0714-5625-49A6-BC2A-0DEF0AB56A98@verweg.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--2O+9B+xSKalj/wdD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 06, 2008 at 09:51:11AM +0100, Ruben van Staveren wrote:
>The interesting thing, to stay on topic, is that people are willing to=20
>explore a feature called "SCTP" which to my knowledge is younger than=20
>"IPv6". This makes the whole discussion sort of moot, right ?

In my case, I have a use for SCTP at work (we are using various
protocols that run on top of SCTP) but we don't have any IPv6 networks
in use.  Personally, I find the IPv6 data reported in things like
netstat are annoying.

>had TCP/UDP for many years and they are still serving their purpose well,=
=20
>so why change ?

TCP isn't sufficiently robust for some Telco purposes:  They can't
accept the time it takes TCP to detect or recover from a link failure.

>So give it a chance, only then there will be feedback and only then we can=
=20
>fix the problems. Otherwise it will stay just theoretical.

Agreed.  But at this stage I can't justify the effort to do anything
more than have a very cursory glance it at.  What benefit would I
derive from setting up an IPv6 network and attempting to experiment
with it?  My ISP won't support IPv6 and I'm reasonably certain my
cable-modem doesn't either so IPv6 connectivity would entail some
sort of tunnel.

--=20
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.

--2O+9B+xSKalj/wdD
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHz8pj/opHv/APuIcRApYJAKC8IMrjVoQE/OSsEqd1hUgCsiwfSACgvTqe
lM7FzzhyVJewpXZkEGKqqIU=
=3Rt4
-----END PGP SIGNATURE-----

--2O+9B+xSKalj/wdD--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080306104139.GX68971>