From owner-freebsd-stable@FreeBSD.ORG Thu Mar 6 03:13:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EF2A106566B; Thu, 6 Mar 2008 03:13:57 +0000 (UTC) (envelope-from michael@quuxo.com) Received: from hudson.quuxo.net (hudson.quuxo.net [203.18.245.242]) by mx1.freebsd.org (Postfix) with ESMTP id A00F68FC1E; Thu, 6 Mar 2008 03:13:56 +0000 (UTC) (envelope-from michael@quuxo.com) Received: from [149.171.9.28] ([149.171.9.28]) (authenticated bits=0) by hudson.quuxo.net (8.14.2/8.14.2) with ESMTP id m262kvNd087306 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Mar 2008 13:16:57 +1030 (CST) (envelope-from michael@quuxo.com) From: Michael Gratton To: Jeremy Chadwick In-Reply-To: <20080305160143.GA28941@eos.sc1.parodius.com> References: <20080305083930.Q37745@shell.xecu.net> <20080305160143.GA28941@eos.sc1.parodius.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-zYCMxVkSGGqvNGGO3lFX" Organization: Quuxo Software Date: Thu, 06 Mar 2008 13:46:52 +1100 Message-Id: <1204771612.13169.16.camel@tremelay> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (hudson.quuxo.net [203.18.245.242]); Thu, 06 Mar 2008 13:16:58 +1030 (CST) X-Virus-Scanned: ClamAV 0.92/6143/Thu Mar 6 10:58:27 2008 on hudson.quuxo.net X-Virus-Status: Clean Cc: Vadim Goncharov , freebsd-stable@freebsd.org Subject: Re: INET6 -- and why I don't use it X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2008 03:13:57 -0000 --=-zYCMxVkSGGqvNGGO3lFX Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Jeremy, On Wed, 2008-03-05 at 08:01 -0800, Jeremy Chadwick wrote: > * I'm not familiar with the intricacies of the protocol.=20 No better time (or way) to learn! Get going! > * The last I read about IPv6 in mainstream news, there were major > concerns cited over some of the security aspects of the protocol. When was the last time you heard anything about IPv4 in the mainstream news (that wasn't related the approaching address space armageddon)? > * I have never liked how IPv6 denotes its addresses by using colon- > delimited hexadecimal strings. The glib answer would be "and this is why we have the DNS". Yes it is more typing and/or talking, but that's the price to pay for a larger address space. Anyway, just do what we do when relating v4 addresses: don't pronounce the delimiter. Bonus points to the first person who coins the name of the double-colon. I vote for "bam": "What's that address again?" "Err, two oh oh one, aye bee oh nine, bam oh oh oh five." > * Consumer ISPs here in the States do not "pass packets" -- you aren't > given a raw pipe; you're given a physical transport with IPv4 service. As others have pointed out, ISPs over there are staring to get in on the act, behind Asia. As I said, no better time to learn!=20 > * The "we're running out of address space" argument doesn't hold > much ground with me. Yes, it's getting tight, but it's not THAT tight. Only because of NAT, and... > * NAT with IPv4 appears to be "solving" most of the address space issues > in this day and age. No. NAT is evil. If you have ever been at a site that uses the same private range as on the other side of the VPN you're using, you know what I mean. There's plenty of other reasons why NAT is a terrible kluge that needs to go away ASAP. I think you mentioned many of them. > * None of my employers (sans my current, Microsoft) have ever bothered > implementing IPv6 on their networks. For many, many reasons, which are slowly going away. > Sufficient? I'd argue otherwise. :) /Mike --=20 Michael Gratton =20 Quuxo Software --=-zYCMxVkSGGqvNGGO3lFX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHz1sbn1mVFlYUR84RAqxbAJsE3VhAT2e7fcrt9jKtQKChNxGQ3QCeID5z beilnAndJrnH3JIFfNA1tQs= =C/y2 -----END PGP SIGNATURE----- --=-zYCMxVkSGGqvNGGO3lFX--