Re: [mif] Announcing draft-mouton-mif-dhcpv6-drlo-00 about default route with DHCPv6

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 18 August 2011 14:28 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 72E5021F8B5D for <mif@ietfa.amsl.com>; Thu, 18 Aug 2011 07:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.179
X-Spam-Level:
X-Spam-Status: No, score=0.179 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, GB_ABOUTYOU=0.5, 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 nfSKdNeV6FMj for <mif@ietfa.amsl.com>; Thu, 18 Aug 2011 07:28:04 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id AAD6A21F8B42 for <mif@ietf.org>; Thu, 18 Aug 2011 07:28:02 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr (Postfix) with ESMTP id E1AC59400C4; Thu, 18 Aug 2011 16:28:48 +0200 (CEST)
Message-ID: <4E4D219F.6070906@gmail.com>
Date: Thu, 18 Aug 2011 16:28:47 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Wojciech Dec <wdec.ietf@gmail.com>
References: <4E381663.7070109@gmail.com> <CAFFjW4g4p59O1xPzBcOiveK4rZ2T8Ya4atqf1=dq6Lvxjw_0zQ@mail.gmail.com>
In-Reply-To: <CAFFjW4g4p59O1xPzBcOiveK4rZ2T8Ya4atqf1=dq6Lvxjw_0zQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 110817-1, 17/08/2011), Outbound message
X-Antivirus-Status: Clean
Cc: mif <mif@ietf.org>
Subject: Re: [mif] Announcing draft-mouton-mif-dhcpv6-drlo-00 about default route with DHCPv6
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: Thu, 18 Aug 2011 14:28:04 -0000

Le 18/08/2011 14:11, Wojciech Dec a écrit :
> Hello Alex,
>
> reading through the draft, other than it proposing a new option with
> a different format, could you elaborate on why/what is the issue in
> http://tools.ietf.org/html/draft-ietf-mif-dhcpv6-route-option-02 for
> conveying the default router info (which the draft already covers)?

Hello Wojciech,

Thank you for reading our draft.

With respect to your draft: indeed I believe there may some issues with
the way it proposes to convey the default router info.

For example, if I am not mistaken, your draft does not communicate the
MAC address of the default router.  Some times communicating the MAC
address could speed up the process (avoid the subsequent NS/NA to solve
the MAC address).

Also, it does not treat of lifetime of this default route (although it
does treat of DHCP lifetimes).  An ND-lifetime could be necessary
sometimes to the ND structures in the Default Router List.

Your draft communicates the default route as 128 0 bits, which may be
too long in certain constrained environments (it adds around half to
size of the entire message).

There may be other issues about your draft that I would like to discuss.

On another hand, what do you think about our draft, other than just
being a different format than yours?

Then, do you think it may be useful to communicate MAC and ND-lifetime
of default route?

Thanks,

Alex

>
> Thanks, Wojciech.
>
> On 2 August 2011 17:23, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>>
> wrote:
>
> Dear MIF,
>
> We would like to announce a new draft focusing to offer default route
> with DHCPv6:
>
> "Default Router List Option for DHCPv6 (DRLO)"
> draft-mouton-mif-dhcpv6-drlo-__00.txt
> http://tools.ietf.org/html/__draft-mouton-mif-dhcpv6-drlo-__00.txt
> <http://tools.ietf.org/html/draft-mouton-mif-dhcpv6-drlo-00.txt>
>
> Thank you in advance for commenting on this draft.
>
> Alex and Maximilien
>
> ------------------------------__------------------------------__--------
>
>
>
Implementation Details
>
> A prototype linux implementation is ongoing, and modifies ISC Client
> and Server; Relay works unmodified.
>
> A wireshark capture is attached (dissector code available upon
> request).
>
> Server uses a new pattern of 'format codes' "6SmMoA", and the conf
> file says: [...]
>
> option dhcp6.default-router 2002:c130:13c1:11f::ff 8400
> 00:07:32:06:7e:72,2002:c130:__13c1:11f:13c1:11f::fe 88
> 00:07:32:06:7e:73 ,2002:c130:13c1:11f::f5 8300 ;
>
> [...]
>
> Client conf file says:
>
> interface "eth0"{ request
> dhcp6.domain-search,dhcp6.__name-servers,dhcp6.default-__router; }
>
> Client says:
>
> RCV:  X-- Server ID: 00:01:00:01:15:67:c9:7d:00:12:__3f:1c:a2:95
> RCV: | | X-- TEST_AJOUT eth0 et 0 et 2. RCV:  | | X--
> DEFAULT_ROUTER_ADDR 2002:c130:13c1:11f::ff. RCV:  | | | X--
> Default_router_lifetime 8000. RCV:  | | | X--
> Default_router_link_layer_addr 00:22:68:17:59:ae. RCV:  | | X--
> TEST_AJOUT eth0 et 0 et 2. RCV:  | | X-- DEFAULT_ROUTER_ADDR
> 2002:c130:13c1:11f::fe. RCV:  | | | X-- Default_router_lifetime 8400.
> RCV:  | | | X-- Default_router_link_layer_addr 00:07:32:06:7e:72.
> RCV:  Advertisement recorded.
>
>
> After execution of the DHCP exchange, the neigh cache is (note
> "expires" corresponding to the lifetime):
>
> # ip -6 route show
>
> [...]
>
> default via 2002:c130:13c1:11f::ff dev eth0  proto kernel metric 1024
> expires 7752sec mtu 1500 advmss 1440 hoplimit 0
>
> [...]
>
> Thank you for considering this draft.
>
> Alex
>
> _______________________________________________ mif mailing list
> mif@ietf.org <mailto:mif@ietf.org>
> https://www.ietf.org/mailman/listinfo/mif
>
>