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

Owen DeLong <owen@delong.com> Sun, 08 December 2013 19:42 UTC

Return-Path: <owen@delong.com>
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 1467E1AE0AE for <v6ops@ietfa.amsl.com>; Sun, 8 Dec 2013 11:42:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.992
X-Spam-Level:
X-Spam-Status: No, score=-0.992 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=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 Vt0U4X1daN8Q for <v6ops@ietfa.amsl.com>; Sun, 8 Dec 2013 11:42:42 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 5A0591AE0AD for <v6ops@ietf.org>; Sun, 8 Dec 2013 11:42:41 -0800 (PST)
Received: from [IPv6:2620::930:0:ca2a:14ff:fe3e:d024] ([IPv6:2620:0:930:0:ca2a:14ff:fe3e:d024]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id rB8JeRJi015114 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 8 Dec 2013 11:40:27 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com rB8JeRJi015114
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1386531627; bh=4nDTfepdPKVSr8RzUsNRpBKfiPU=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=Ak1gOrHyoZyeG5C400CE44EyAlUa3ltQTBVtT5X7285ZenKM66ziziLArqvVluEKR ZOsaFzKbcPLdJ9x+cUaxXaDpPqBGIlInDHl4Ki8cI95uaus3H2rH32lS9hlogWnDHc m94+HGDAnKCvcCf5lF3LXJKHoAR5YWSABE8QxgpI=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <52A4C6FD.1080504@gmail.com>
Date: Sun, 08 Dec 2013 11:38:41 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <98CACA9B-AD61-460A-93AC-D5EEA1176706@delong.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> <alpine.OSX.2.00.1312080643090.68814@ayourtch-mac> <B561C767-677A-4A37-BA69-EB24951B2817@delong.com> <52A4C6FD.1080504@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1822)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [IPv6:2620:0:930::200:2]); Sun, 08 Dec 2013 11:40:27 -0800 (PST)
Cc: "v6ops@ietf.org" <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: Sun, 08 Dec 2013 19:42:43 -0000

On Dec 8, 2013, at 11:22 , Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> On 08/12/2013 19:40, Owen DeLong wrote:
>> On Dec 7, 2013, at 22:25 , Andrew Yourtchenko <ayourtch@cisco.com> wrote:
> 
> ...
>>> I think you nailed it here: With RA you *discover* the routers available on the link, with DHCP in legacy IP, you *configure* them.
>> 
>> No, with DHCP, you discovered what some remote host rumored them to be.
> 
> I don't think we should be having this argument. We should be
> trying to write down objectively the type of scenarios where
> DHCPv6 is applicable, the type of scenarios where RA-only is
> applicable, and the type of scenarios where both (simultaneously)
> are applicable.
> 
> There's no right or wrong answer here.
> 
>   Brian

In IPv6, as I read the RFCs, there's no valid way for a host to know that it is supposed to get information from a DHCPv6 server unless it receives an RA with the M and/or O bits set.

As such, the options are not DHCPv6 only, RA-only, and Both, but, RA-only and Both.

The scenarios where RA-Only make sense are any scenario where you do not need greater control of the client configuration than Prefix information, routing information, and DNS resolver addresses and search strings.

In any scenario where you need to supply the host with more configuration information on a dynamic basis, DHCPv6 is also required.

Also, if you want dynamic DNS updates, deterministic assigned suffixes, etc., these fall into the DHCPv6 realm.

It's really as simple as that as near as I can tell.

If you want to run without RAs, then you are into the realm of static configuration. I, personally, do not see this as a problem.

Owen