Re: draft-bourbaki-6man-classless-ipv6-00

Simon Hobson <linux@thehobsons.co.uk> Sat, 03 June 2017 10:16 UTC

Return-Path: <linux@thehobsons.co.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65835128616 for <ipv6@ietfa.amsl.com>; Sat, 3 Jun 2017 03:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level:
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-CbNxHw-4Bq for <ipv6@ietfa.amsl.com>; Sat, 3 Jun 2017 03:16:08 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83F891279EB for <ipv6@ietf.org>; Sat, 3 Jun 2017 03:16:08 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [IPv6:2001:470:1f09:baa:d69a:20ff:fec4:bbf6] (unknown [IPv6:2001:470:1f09:baa:d69a:20ff:fec4:bbf6]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 88F441BC37 for <ipv6@ietf.org>; Sat, 3 Jun 2017 10:15:46 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <CAKD1Yr1zvyVbcQjFNDV7SzcLsG2igpSg+jst4AR9KbYstPWjTg@mail.gmail.com>
Date: Sat, 03 Jun 2017 11:15:45 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <723E4B25-B932-412D-8369-448703DAA21A@thehobsons.co.uk>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <20170602141259.GD30896@gir.theapt.org> <CAKD1Yr0DtQYvCYLQexhXe_nhb5rjeyhnB4bCveqyO5Xbuwdg1A@mail.gmail.com> <20170602145655.msfjw35qhoev4sm2@Vurt.local> <CAKD1Yr3gqFgq3dxFaBEV++q5cgx1AHzFLGRJ50DYJjVE69C7iA@mail.gmail.com> <f2260ee557014429a1fef32de040547b@XCH15-06-11.nw.nos.boeing.com> <C6696427-E3BD-4C5A-9A2F-A979CE063C45@google.com> <CAKD1Yr1zvyVbcQjFNDV7SzcLsG2igpSg+jst4AR9KbYstPWjTg@mail.gmail.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/s1FemHUGZjK01n_lxjGG9Q7C_ec>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jun 2017 10:16:10 -0000

Lorenzo Colitti <lorenzo@google.com> wrote:

> When all the applications have built NAT traversal mechanisms, anything more than one IP address per location becomes worth nothing. At that point the extra rent is gone, and everybody loses because the system is less capable, less robust, and harder to configure than it would have been without NAT.
> 
> And in fact, that's what happens in IPv4 today.

Agreed - but that is typically out of necessity as there just aren't the IP addresses to go round.

Having had the luxury of managing a network with a whole /24 to play with, and looked at the underlying problems making SIP phones work through NAT, I fully agree that NAT is to be avoided due to the amount of brokenness* it creates. Trying to persuade those who see things "just work" (because of all the wasted effort put in to make things work - would have been much better spent getting IPv6 adopted sooner) is a different matter.

BUT, I cannot see the logic behind your earlier comment that DHCP makes NAT inevitable for IPv6.


* PS - I have a special place in hell for the ******** ******** at Zyxel who think that randomising port translations on every connection, and "no you can't turn that off, we don't care if it breaks things, it adds security" (yes, that's the response I got from them !) is a good idea.