Re: [mif] Route option for DHCPv6 - next steps?

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 05 April 2012 11:18 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76A9D21F86DC for <mif@ietfa.amsl.com>; Thu, 5 Apr 2012 04:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.591
X-Spam-Level:
X-Spam-Status: No, score=-101.591 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEzKJ0AO5vRC for <mif@ietfa.amsl.com>; Thu, 5 Apr 2012 04:18:43 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id AEF9421F8668 for <mif@ietf.org>; Thu, 5 Apr 2012 04:18:36 -0700 (PDT)
Received: by werb10 with SMTP id b10so940377wer.31 for <mif@ietf.org>; Thu, 05 Apr 2012 04:18:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=R8xPx0b0iwOR4O419ms/74SAz5wJUA8FYpqqzdIpJpE=; b=twORhMmQuRWCAfGWeKr75cIIkBCEmZBc/ao6SmZ9aaVrZwTgzdHHWEDnc3Jcb5UohU 7rjAaxJeA+lGLY0mdMa0EQU+gGvRFW0VvysStFblxgfkmaV5pDPzdjjDJ0ZHoXBP7KwQ aUaG0nVlrIRNTjyU4s3d2nPWDGBClgd4RnRKN5ptfzXZ8p6X9UaqXLSAvVkr03yxj2Ic ZlwwzstIKQ2cVB9/ZGklbIOokrKrbQvh0wjJ7pt7gaYA87VEctgP9mtm5yQ/4qwuZW7z SdV6t8oDlwRh19jpYHnATQ9HYIbSm//XbVi/61rEdzyKxEKZNI2MtfN1PFK2sss0kQRK xCVQ==
Received: by 10.180.89.130 with SMTP id bo2mr3951395wib.17.1333624715902; Thu, 05 Apr 2012 04:18:35 -0700 (PDT)
Received: from [192.168.1.69] (host-2-102-217-51.as13285.net. [2.102.217.51]) by mx.google.com with ESMTPS id ea6sm12827780wib.5.2012.04.05.04.18.33 (version=SSLv3 cipher=OTHER); Thu, 05 Apr 2012 04:18:34 -0700 (PDT)
Message-ID: <4F7D7F82.9050405@gmail.com>
Date: Thu, 05 Apr 2012 12:18:26 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <75459BC2-E733-45C0-BC1C-25A19BBA1137@gmail.com> <4F744831.3070406@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307472D4175@mbx-01.win.nominum.com> <4F7453FC.3010502@gmail.com> <4F74546D.4060808@gmail.com>, <72C42575-6BE2-4F27-B7F4-AA4539DA7EF9@lilacglade.org> <8D23D4052ABE7A4490E77B1A012B6307472D43A1@mbx-01.win.nominum.com>, <069301cd0dd2$5954df00$0bfe9d00$@tndh.net> <8D23D4052ABE7A4490E77B1A012B6307472D45F6@mbx-01.win.nominum.com> , <075201cd0f8e$94cb81 7 0$be628450$@tndh.net> <8D23D4052ABE7A4490E77B1A012B6307472D5C5B@mbx-01.win.nominum.com>, <00c301cd10ec$46f39ff0$d4dadfd0$@tndh.net> <8D23D4052ABE7A4490E77B1A012B6307472D608D@mbx-01.win.nominum.com> <01a601cd11b6$34522090$9cf661b0$@tndh.net> <3B8389FE-8FE4-4AC8-B1F2-D2FD924EAC8A@nominum.com> <00a501cd129a$ace0f560$06a2e020$@tndh.net> <E527F5B8-C34F-4147-9D33-371E41057B1B@nominum.com> <4F7D4650.7040108@gmail.com> <E48A66BE-47CF-4F84-8FB9-E1194ECD21F9@nominum.com>
In-Reply-To: <E48A66BE-47CF-4F84-8FB9-E1194ECD21F9@nominum.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "<mif@ietf.org>" <mif@ietf.org>
Subject: Re: [mif] Route option for DHCPv6 - next steps?
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2012 11:18:43 -0000

On 2012-04-05 11:42, Ted Lemon wrote:
> On Apr 5, 2012, at 3:14 AM, Brian E Carpenter <brian.e.carpenter@gmail.com>
>  wrote:
>> My understanding is that IT departments who currently manage layer 3
>> aspects of hosts via whatever database tool configures their DHCP[v6]
>> servers wish to continue doing so, rather than having to use a
>> different (or updated) tool to configure their RAs. The reason of
>> course is to reduce operational complexity and expense.
> 
> But *why*?   Please stop talking about feelings.   Please say why. 
> 
> For example, if using DHCPv6 instead of RA reduces operational complexity and expense, you should be able to say *why* it does so.

Because using one method of configuring hosts is less complex
and therefore cheaper than using two. It's clear that small simple
networks (the dentist's office scenario in the terminology we used
around 1995) can get by with RA alone, and it's clear that more
complex networks need much more flexibility. MIF and homenet are
both considering complex scenarios by this standard.

I now think that detailing use cases is beside the point. It's
simply a fact that above a certain level of complexity, operators
need the flexibility of DHCPv6 or RADIUS, and in that case, it is
less complex if everything configurable can be configured with the
same tool.

   Brian