Re: [v6ops] New Version Notification for draft-yourtchenko-ra-dhcpv6-comparison-00.txt (fwd)

Nick Hilliard <nick@inex.ie> Thu, 19 December 2013 17:15 UTC

Return-Path: <nick@inex.ie>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB531ADF87 for <v6ops@ietfa.amsl.com>; Thu, 19 Dec 2013 09:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 RKUqE3sbtcTJ for <v6ops@ietfa.amsl.com>; Thu, 19 Dec 2013 09:15:28 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 0F46D1ADDDA for <v6ops@ietf.org>; Thu, 19 Dec 2013 09:15:27 -0800 (PST)
X-Envelope-To: v6ops@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100::126]) (authenticated bits=0) by mail.netability.ie (8.14.7/8.14.5) with ESMTP id rBJHFIRH094575 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 19 Dec 2013 17:15:18 GMT (envelope-from nick@inex.ie)
X-Authentication-Warning: cheesecake.netability.ie: Host [IPv6:2001:4d68:2002:100::126] claimed to be cupcake.foobar.org
Message-ID: <52B329A6.1070309@inex.ie>
Date: Thu, 19 Dec 2013 17:15:18 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <alpine.OSX.2.00.1311271353550.3903@ayourtch-mac> <1386274786.29351.YahooMailNeo@web142501.mail.bf1.yahoo.com> <alpine.OSX.2.00.1312060759220.68814@ayourtch-mac> <1386378082.99914.YahooMailNeo@web161901.mail.bf1.yahoo.com> <alpine.OSX.2.00.1312072028290.68814@ayourtch-mac> <F024FF5B-35A6-4221-952C-4A730A68C59D@delong.com> <D437C864-F276-46A6-A51E-4C57E5CF829E@cisco.com> <52B22828.6080700@inex.ie> <CAKD1Yr3TA9+yDpCRHNMOXNiq0bZ0x-yn=kVotiFD2187GjdnWw@mail.gmail.com> <52B2ED1E.1040108@inex.ie> <CAKD1Yr2hQBB_gsv6=zRLq6SmxF6JG=o2DT=-iDykSz7u=yJVZg@mail.gmail.com> <52B306D7.3030604@inex.ie> <CAKD1Yr2W7v3L+NuVrTv4OvyWxVmbAHhBtVV9tpV_v_9cL-Wb6Q@mail.gmail.com>
In-Reply-To: <CAKD1Yr2W7v3L+NuVrTv4OvyWxVmbAHhBtVV9tpV_v_9cL-Wb6Q@mail.gmail.com>
X-Enigmail-Version: 1.6
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] New Version Notification for draft-yourtchenko-ra-dhcpv6-comparison-00.txt (fwd)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Dec 2013 17:15:30 -0000

On 19/12/2013 16:25, Lorenzo Colitti wrote:
> Fine, but please don't say it's simpler. It's not - it has way more moving
> parts.

No, actually it has a choice of moving parts and creating a priority
mechanism for selecting one over the other is actually simpler than
defining an interaction mechanism between the two.

> We can, but it won't get us anywhere. You've said that you want to run your
> network with DHCPv6 because RAs don't suit your requirements, and I'll say
> that I want to run my network with RAs because DHCPv6 doesn't suit my
> requirements. We will both have valid reasons, and probably we'll even
> concede that in each other's networks the other's solution might be better.

exactly.

> But once we reach that point, we're still stuck. Because the only way
> forward from there is to conclude that we need to define two completely
> autonomous and competing systems to provision the same protocol on the same
> host implementations, and choose one or the other depending on the
> deployment scenario. 

yes, that is the conclusion I have come to too.  And you know what?  It's
actually not a bad solution.

> This is a bad outcome, because hosts that want to work
> everywhere (and what host doesn't?) need to implement both protocols. The
> resulting complexity - which is more than 2x, because in addition to the
> two protocols you have to define and implement rules to deal with their
> interaction - pushes costs up for everyone, because everyone uses hosts,
> including me and you.

at the moment we have a mess which seems to work for some people but not
others, and which people have been complaining about loudly since the day
that dhcp became viable.

> That's why I say this is a dead horse - because there *is* no single
> technically correct answer.

exactly, which is why I think we need to acknowledge that it would be
better for everyone to come to some conclusion to this mess.  Let the
people who want to use and develop SLAAC do what they want to the protocol
and let the people who want to use and develop DHCPv6 do what they want.
We can put in an arbitration mechanism relatively easily.

I completely agree that these endless arguments are stupid.  But they will
continue until the heat death of the universe, or until we come to a
decision to split off the two protocols - whichever comes sooner.

Nick