Re: [mif] Comments on draft-mouton-mif-dhcpv6-drlo-00

maximilien mouton <maximilien.mouton@gmail.com> Mon, 26 September 2011 08:39 UTC

Return-Path: <maximilien.mouton@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 2D21921F8B51 for <mif@ietfa.amsl.com>; Mon, 26 Sep 2011 01:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_LOW=-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 6YPlj2r2rV2m for <mif@ietfa.amsl.com>; Mon, 26 Sep 2011 01:39:52 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB7E21F8B50 for <mif@ietf.org>; Mon, 26 Sep 2011 01:39:52 -0700 (PDT)
Received: by eye4 with SMTP id 4so3509023eye.31 for <mif@ietf.org>; Mon, 26 Sep 2011 01:42:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=hu1exEXxMQCyp/jiEVV72WvNcqVnmFrKmfpzprrwJRY=; b=RkawLr5+rnILtquJosrUAoVwddIUPWx5C4bYs6zHn3aJvbNOkRrsH+Rze8O2PNITbn AMM88V6fYNEPa8H1eBaOMBG7gQFdNk55wRxhcKLlfzoKru2/e1snZnd7XpeHUGhqXZ8E NS/nfIGjGR5WMao48HiromPLZSEWqEULmQ4Jc=
Received: by 10.14.19.144 with SMTP id n16mr1289971een.128.1317026553927; Mon, 26 Sep 2011 01:42:33 -0700 (PDT)
Received: from [127.0.0.1] ([158.64.77.102]) by mx.google.com with ESMTPS id v60sm57755264eev.12.2011.09.26.01.42.32 (version=SSLv3 cipher=OTHER); Mon, 26 Sep 2011 01:42:33 -0700 (PDT)
Message-ID: <4E803AE5.2000203@gmail.com>
Date: Mon, 26 Sep 2011 10:42:13 +0200
From: maximilien mouton <maximilien.mouton@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: Simon Perreault <simon.perreault@viagenie.ca>
References: <3CF88B99A9ED504197498BC6F6F04B81040FBDA9@XMB-BGL-41E.cisco.com> <4E6E7A72.9030208@gmail.com> <4E6EAFC2.5060906@gmail.com> <4E6EDEA8.3080108@gmail.com> <CFDF82EE-052B-4A61-AE1B-152337822B6E@nominum.com> <4E6F825C.3080303@gmail.com> <3D0B3661-8A8F-4BB2-A8EF-25007BEAF66C@nominum.com> <4E6F923F.7090304@gmail.com> <7061CEB8-8084-41D5-B31E-9F8E3B6C7091@nominum.com> <4E6F9B91.7010503@gmail.com> <B987CA14-569C-428C-8D8A-C97A0E42EF48@nominum.com> <4E6FA049.1040309@viagenie.ca>
In-Reply-To: <4E6FA049.1040309@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: mif@ietf.org
Subject: Re: [mif] Comments on draft-mouton-mif-dhcpv6-drlo-00
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, 26 Sep 2011 08:39:53 -0000

Hi Simon and Ted,

Le 13/09/2011 20:26, Simon Perreault a écrit :
> Ted Lemon wrote, on 09/13/2011 02:22 PM:
>> Could you please clearly articulate a use case where this option is
>> necessary, and the existing proposed option is not adequate?
>> Please do not mention operating system data structures.   Please do
>> not say "I find it to be the case that.."   Without a use case, I
>> just don't see the point in discussing this further.
>
> +1

First, I think we can say that there is a consensus on the fact that
DHCP should have an option including default router.

Second, why a specific option for default route rather than specify it
in route option?

You can notice that router option and static route option (the stateful
one) are defined separately since rfc 2132 (DHCP Options).
Moreover, rfc 3442 (Route Option for DHCP version 4) has a similar point
of view than what we propose with DRLO.

But beside this history point here is a scenario explaining the need of
specific option for default route:
Imagine a realistic network in which in the same prefix is, a limited
resource device not able to carry more than a default route (see
previous discussion with Alex), a classic device like a laptop with one
interface and a MIF device which want to run route option.
A reasonable configuration is DRLO for 2 the two first type of device
and DRLO+route option for the third (less frequent case).

In the opposit specify specific routes without default route may be
useful for instance for security or accounting reasons.

Maximilien


>
> Simon