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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 13 September 2011 20:57 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 3E5EE11E80E5 for <mif@ietfa.amsl.com>; Tue, 13 Sep 2011 13:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.357
X-Spam-Level:
X-Spam-Status: No, score=-2.357 tagged_above=-999 required=5 tests=[AWL=1.242, BAYES_00=-2.599, 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 jkFCy+0Q7AiQ for <mif@ietfa.amsl.com>; Tue, 13 Sep 2011 13:57:12 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 77BDA11E80DB for <mif@ietf.org>; Tue, 13 Sep 2011 13:57:12 -0700 (PDT)
Received: by fxd18 with SMTP id 18so1035463fxd.31 for <mif@ietf.org>; Tue, 13 Sep 2011 13:59:19 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=wkTWLW6mYufLoYkVxwodz/6HJ3Leg4DRBeJ7NOS5ocU=; b=NDnz9pYa99npYdbIqruztSCIaZhTcnSzGnIol5K6DsmXWLMFKA+4KX5rwd3XsYy0m6 TGSA794eXRXBRzzo1/CkbIvcPySrrh/d44fGtYuP8hHfz5TYneA6DCyBj2cZtGJDhCWh RKcgqO2jwl3pu0cZ+HTgctPovrMjX3np0Sj0I=
Received: by 10.223.48.141 with SMTP id r13mr252792faf.115.1315947559069; Tue, 13 Sep 2011 13:59:19 -0700 (PDT)
Received: from [127.0.0.1] (bur91-3-82-239-213-32.fbx.proxad.net. [82.239.213.32]) by mx.google.com with ESMTPS id b10sm1444016fam.1.2011.09.13.13.59.16 (version=SSLv3 cipher=OTHER); Tue, 13 Sep 2011 13:59:16 -0700 (PDT)
Message-ID: <4E6FC41E.6010002@gmail.com>
Date: Tue, 13 Sep 2011 22:59:10 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: mif@ietf.org
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
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: Tue, 13 Sep 2011 20:57:13 -0000

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

-1

One particular use case is:

DHCP communicates a default route without lifetime to Client.

Client inserts the default route without lifetime.

Some implementations may set that mandatory ND local field to arbitrary
values- some will expire it some won't.

Some Clients will run RS after that time others won't.

One other case is the following, for WiFi hotspot:

DHCP communicates the default route wihtout MAC address

Client will receive the defualt route and install it.

When it first uses it it will necessarily generate an NS-NA in order to
solve the default router's address into the MAC address.  This
additional NS-NA is noise on wire, compared to if the MAC address were
communicated in the first place.

Alex

>
> Simon