Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-03 published
Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 13 September 2011 22:06 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 69E8721F8B3F for <mif@ietfa.amsl.com>; Tue, 13 Sep 2011 15:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.586
X-Spam-Level:
X-Spam-Status: No, score=-103.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, 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 RkR1TXsihJWP for <mif@ietfa.amsl.com>; Tue, 13 Sep 2011 15:06:26 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 73FA821F8B3E for <mif@ietf.org>; Tue, 13 Sep 2011 15:06:26 -0700 (PDT)
Received: by qyk32 with SMTP id 32so3177753qyk.10 for <mif@ietf.org>; Tue, 13 Sep 2011 15:08:29 -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=kfkwuzsFLNPHzvk4fUVbIc6pRviWd4B9srd0CWoYIJw=; b=Eqn0G3IUpqM1PNqs/IRiQmiXcsHnzYZ+Ga6RXjDXes0+5XfK2GQ0myBfWqTMOUzzA/ jh24ET3zDjbUG7DB3h4+VBDoplVb15P1EKLllJfHHEGFj0YYOu4H7EUUF4hvPiwnVIYT GFSgTYmw2VzYo+uNeKyxaMw5sEDhf5bE9pFMI=
Received: by 10.224.180.210 with SMTP id bv18mr2394389qab.171.1315951709511; Tue, 13 Sep 2011 15:08:29 -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 o18sm2832543qaz.3.2011.09.13.15.08.27 (version=SSLv3 cipher=OTHER); Tue, 13 Sep 2011 15:08:28 -0700 (PDT)
Message-ID: <4E6FD459.30303@gmail.com>
Date: Wed, 14 Sep 2011 10:08:25 +1200
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: Simon Perreault <simon.perreault@viagenie.ca>
References: <20110910220345.29077.66749.idtracker@ietfa.amsl.com> <4E6BE7BF.5030501@gmail.com> <4E6C8F4A.308@gmail.com> <4E6E053B.7000305@viagenie.ca> <4E6E097F.8010205@gmail.com> <4E6E0C4A.7030105@viagenie.ca> <4E6E10E0.6010607@gmail.com> <4E6E13E0.2030402@viagenie.ca> <4E6EB0DC.5040102@gmail.com> <4E6F6933.1010908@viagenie.ca>
In-Reply-To: <4E6F6933.1010908@viagenie.ca>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: mif@ietf.org
Subject: Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-03 published
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: Tue, 13 Sep 2011 22:06:27 -0000
On 2011-09-14 02:31, Simon Perreault wrote: > Brian E Carpenter wrote, on 09/12/2011 09:24 PM: >> On 2011-09-13 02:14, Simon Perreault wrote: >>> On 2011-09-12 10:02, Alexandru Petrescu wrote: >>>>> I don't see the use case. Can't the DHCP client on the very small >>>>> platform just install the default route first, then whatever other >>>>> routes it can support, and ignore the rest? >>>> Do you think there exist a DHCP way to say: "install the default route >>>> first and, if you have enough memory, install these specific routes"? >>> Maybe it can be written in the draft. For example: >>> >>> Hosts MUST install routes in the order they are listed. If any routes >>> cannot be installed due to resource constraints, routes MAY be dropped >>> starting from the end. >>> >>> With this, the operator can put the default route first and obtain the >>> behaviour you're describing. >> That won't work if the host also gets a default route from RA. There's >> nothing to stop DHCPv6 and RA being used simultaneously, for different >> prefixes, and providing different default routers. > > I'm not following you. > - That's not a problem I'm trying to solve with the above proposal. > - Even with a separate DHCP option dedicated to the default route, I don't see > how the problem you mentioned gets solved. I agree, it appears insoluble to me too. I think you should mention that as an operational consideration. Brian
- Re: [mif] [dhcwg] I-D draft-ietf-mif-dhcpv6-route… Alexandru Petrescu
- [mif] I-D Action: draft-ietf-mif-dhcpv6-route-opt… internet-drafts
- [mif] I-D draft-ietf-mif-dhcpv6-route-option-03 p… Tomasz Mrugalski
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… maximilien mouton
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… Simon Perreault
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… Alexandru Petrescu
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… Simon Perreault
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… Alexandru Petrescu
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… Simon Perreault
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… Alexandru Petrescu
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… Brian E Carpenter
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… Simon Perreault
- Re: [mif] I-D draft-ietf-mif-dhcpv6-route-option-… Brian E Carpenter