[mif] RA vs DHCPv6 config (was Review requested: draft-ietf-mif-dhcpv6-route-option)

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 30 October 2011 20:35 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 B9E6921F8B80 for <mif@ietfa.amsl.com>; Sun, 30 Oct 2011 13:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.224
X-Spam-Level:
X-Spam-Status: No, score=-103.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 WwuhwX9YRB6s for <mif@ietfa.amsl.com>; Sun, 30 Oct 2011 13:35:07 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 140B821F850B for <mif@ietf.org>; Sun, 30 Oct 2011 13:35:07 -0700 (PDT)
Received: by iabn5 with SMTP id n5so8103317iab.31 for <mif@ietf.org>; Sun, 30 Oct 2011 13:35:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=YlUHn+b3LEZ7Y5onMOVhx82P9p7I6ECSCFPTF3ZsEeg=; b=ZHHIyPDmwe/eQJLNlkmxxaL21qrpv1/PnvikBDnvXwgE5Ri3rjejLqgCJcYLwf+5wu XHrIj+g5wCUlKMs8mdTfxUyjiIQCW2E9+NWhQ8X8Cb/rHnzY20jdrZdAONyyGeUbBIOy OQpJU2bUCWeunDQDIG04CYkbkVCS/dajqnBos=
Received: by 10.68.32.2 with SMTP id e2mr18592684pbi.68.1320006906521; Sun, 30 Oct 2011 13:35:06 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id d9sm44113986pbb.13.2011.10.30.13.35.03 (version=SSLv3 cipher=OTHER); Sun, 30 Oct 2011 13:35:05 -0700 (PDT)
Message-ID: <4EADB4F5.3030804@gmail.com>
Date: Mon, 31 Oct 2011 09:35:01 +1300
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: <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="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "<mif@ietf.org>" <mif@ietf.org>
Subject: [mif] RA vs DHCPv6 config (was 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: Sun, 30 Oct 2011 20:35:07 -0000

Ted,

On 2011-10-31 06:24, Ted Lemon wrote:
> 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.

It makes my head hurt a bit to give RA config priority in one context and
DHCPv6 config priority in another context. I think this point requires
a wider discussion; you could find opinions about this in (at least)
6man, v6ops, homenet, and 6renum.

> 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.

Not necessarily, if you think about out-of-the box default behaviour
when someone hooks a few boxes together in an unmanaged network. That's why
I have a feeling that "in case of conflict, DHVPv6 always wins" may turn out
to be the right answer.

    Brian