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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 31 October 2011 18:08 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 009B11F0CAD for <mif@ietfa.amsl.com>; Mon, 31 Oct 2011 11:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level:
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[AWL=-0.428, 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 zmWG3XWJpk5B for <mif@ietfa.amsl.com>; Mon, 31 Oct 2011 11:07:59 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 2771F1F0CA8 for <mif@ietf.org>; Mon, 31 Oct 2011 11:07:57 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr (Postfix) with ESMTP id 7BEF59401CD for <mif@ietf.org>; Mon, 31 Oct 2011 19:07:52 +0100 (CET)
Message-ID: <4EAEE3F5.8020605@gmail.com>
Date: Mon, 31 Oct 2011 19:07:49 +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: mif@ietf.org
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> <4EAED7E1.2040506@gmail.com> <4EAEDCFA.6050202@gmail.com>
In-Reply-To: <4EAEDCFA.6050202@gmail.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
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 18:08:00 -0000

Le 31/10/2011 18:38, Tomasz Mrugalski a écrit :
> On 31.10.2011 18:16, Alexandru Petrescu wrote:
>> 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.
>
> Sorry, but I can't parse that sentence. You seem to agree with Ted
> (DHCP preferred over RA), but the later part of the sentence states
> otherwise (RA preferred over RA).

Ted suggested RA to be prefered over DHCP and I agree with it.

(in another email you propose DHCP preferred over RA, and Ted seems to
agree with you as well).

>> (the preference mechanism can be specified by using the lifetime
>> mechanism).
>
> Can you elaborate on that? What has lifetime to do with preference?
> Do you want to somehow prefer longer (or shorter) lifetimes?

YEs, that.  RA has this Router Lifetime field.  When two routers send RA
each with a default default router, the Host could 'prefer' one over the
other based on the longest lifetime.  RFC4861 says 'The Router Lifetime
applies only to the router's usefulness as a default router'.

A similar mechanism could happen to compare a default route obtained
from DHCP, and from RA: prefer the one whith longer lifetime.

> That is rather dangerous and I would like to avoid that. I believe
> that clear statement ("DHCP overrides RA" or "RA overrides DHCP")
> will help a lot here.

Hm, but that's not how DNS-RA RFC does.  DNS-RA RFC6106 does preferences
instead of a yes-no alternative.  RFC4191 "Default Router Preferences"
also works with preferences instead of exclusion.

What do you think?

Alex

>
> Tomek _______________________________________________ mif mailing
> list mif@ietf.org https://www.ietf.org/mailman/listinfo/mif
>