Re: [mif] Review requested: draft-ietf-mif-dhcpv6-route-option

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 31 October 2011 17:16 UTC

Return-Path: <alexandru.petrescu@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 E123021F8D61 for <mif@ietfa.amsl.com>; Mon, 31 Oct 2011 10:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.742
X-Spam-Level:
X-Spam-Status: No, score=-0.742 tagged_above=-999 required=5 tests=[AWL=-0.571, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
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 TwgxsiSxaC1Y for <mif@ietfa.amsl.com>; Mon, 31 Oct 2011 10:16:28 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id E15BA21F8CFC for <mif@ietf.org>; Mon, 31 Oct 2011 10:16:26 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr (Postfix) with ESMTP id 700C09401E5; Mon, 31 Oct 2011 18:16:20 +0100 (CET)
Message-ID: <4EAED7E1.2040506@gmail.com>
Date: Mon, 31 Oct 2011 18:16:17 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <4EAAA9FE.9030600@innovationslab.net> <CAD06408.17DC0D%wbeebee@cisco.com>, <5B6B2B64C9FE2A489045EEEADDAFF2C3032A71C3@XMB-RCD-109.cisco.com> <COL118-W380DB46BD2C899FA745788B1D30@phx.gbl> <4EAD833E.1020204@gmail.com> <A28D1C9D-0227-48E8-A9B0-EDB769AFD5AA@nominum.com>
In-Reply-To: <A28D1C9D-0227-48E8-A9B0-EDB769AFD5AA@nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 111031-0, 31/10/2011), Outbound message
X-Antivirus-Status: Clean
Cc: "<mif@ietf.org>" <mif@ietf.org>
Subject: Re: [mif] Review requested: draft-ietf-mif-dhcpv6-route-option
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: Mon, 31 Oct 2011 17:16:29 -0000

Le 30/10/2011 18:24, Ted Lemon a écrit :
> On Oct 30, 2011, at 1:02 PM, Alexandru Petrescu wrote:
>> The question one raised on 6man is about coexistence with RA about
>> default route. One is aware that a similar situation (alternate
>> mechanism DHCP-vs-RA for default route) appeared recently when DNS-in-RA
>> was proposed (DHCP existed doing DNS). RFC6106 proposes to do
>> DNS-in-RA but has a section explaining coexistence with DHCP about DNS
>> address - and gives the latter precedence over.
>
> This is a very good point, which should be addressed in the route option
> draft. I think the right thing is to give RA precedence over DHCP for
> routing information, but am curious to know if others disagree.

I do not disagree: in the default route case, if RA offers such data 
then give it preference over the default route obtained from DHCP.

(the preference mechanism can be specified by using the lifetime mechanism).

Alex

>
>> In some cases this recommendation may be inappropriate - there may exist
>> cases where routing protocol software _and_ DHCP software should be used
>> on the same machine (e.g. use DHCP to get DNS address, and use OSPF to
>> do routing). At that point it may be hard to prevent some particular
>> option of DHCP (route-option) being physically available on the machine.
>> Accidentally misconfiguration may happen.
>
> Fortunately, this is not a very serious problem: the router and the DHCP
> server are both under control of the administrator, so they can simply
> configure them correctly, and the right thing will happen. It is always
> possible, if the network administrator sets things up wrong, for the
> network to not work, and there is nothing the IETF can do to eliminate
> this risk. Since the default case is for the network administrator not
> to configure DHCP, I think it's pretty safe to assume that we won't get
> a bad route configuration without some kind of positive action on the
> part of the administrator.
>