Re: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix Delegation for NEMO) to Proposed Standard

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 09 September 2010 06:28 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 949603A67D1; Wed, 8 Sep 2010 23:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.073
X-Spam-Level:
X-Spam-Status: No, score=-2.073 tagged_above=-999 required=5 tests=[AWL=0.176, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sYCBbPCHLGYX; Wed, 8 Sep 2010 23:28:11 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.166.172.106]) by core3.amsl.com (Postfix) with ESMTP id 6D2BA3A6403; Wed, 8 Sep 2010 23:28:11 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.0) with ESMTP id o896SVwB030112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Sep 2010 08:28:31 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id o896SV94008283; Thu, 9 Sep 2010 08:28:31 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id o896SVH7015729; Thu, 9 Sep 2010 08:28:31 +0200
Message-ID: <4C887E8E.8010809@gmail.com>
Date: Thu, 09 Sep 2010 08:28:30 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: Hesham Soliman <hesham@elevatemobile.com>
Subject: Re: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix Delegation for NEMO) to Proposed Standard
References: <C8AEB553.14F15%hesham@elevatemobile.com>
In-Reply-To: <C8AEB553.14F15%hesham@elevatemobile.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: IETF Discussion <ietf@ietf.org>, mext <mext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 06:28:12 -0000

Le 09/09/2010 08:01, Hesham Soliman a écrit :
>
>
>
> On 9/09/10 3:54 PM, "Wassim Haddad"<wassim.haddad@ericsson.com>
> wrote:
>
>> On Sep 8, 2010, at 7:58 AM, Alexandru Petrescu wrote:
>>
>>> I agree mainly with the document draft-ietf-mext-nemo-pd.
>>>
>>> It is good and needed to dynamically assign a Mobile Network
>>> Prefix to the NEMO-enabled Mobile Router.
>>>
>>> However, here are a couple of missing points.
>>>
>>> One missing point is about how will the Mobile Router configure
>>> its default route on the home link?  I thought Prefix Delegation
>>>  would bring DHCP in the picture and would allow MR to synthesize
>>>  a default route even though RAs are absent.  But I now realize
>>> that a DHCPv6-PD implementation (and std?) does not allow a
>>> router (MR) to synthesize its default route (neither RA does, nor
>>> DHCPv6-nonPD does).
>
> =>  I think the MR can easily act as a host on its egress interface
> and configure its default/next hop router that way. Of course the
> other alternative is to use routing protocols, but I think using ND
> should be sufficient.

Hesham - when at home, the MR acts  as a router (ip_forward==1,
join all-routers group), as such ND is insufficient to obtain the
default route - it's a Router.

When at home, and using DHCPv-PD, the MR also acquires its Home Address
with DHCPv6.  If so, then it doesn't use SLAAC to auto-configure neither
a Home Address nor a default route.

In implementation it is of course possible to dynamically change MR
behaviour from Host to Router: be at home, first act as host (fwd==0) to
acquire the Home Address and default route, then set fwd=1 and use
DHCPv6-PD to acquire a prefix (but not the Home Address) and take
advantage of the default route acquired previously as a Host.  This is
one way of solving the issue.  However it is not specified.  I am not
sure how clean is it anyways to disregard that 'M' bit of RA anyways.

The alternative to using routing protocols (OSPF?) to communicate a
default route to the MR - I am not sure how this could work, never seen
it in practice.

Alex


>
> Hesham
>
>
>
>
>