IETF Logo Mail Archive

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

Hesham Soliman <hesham@elevatemobile.com> Thu, 09 September 2010 06:01 UTC

Return-Path: <hesham@elevatemobile.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 F11103A695D; Wed, 8 Sep 2010 23:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ibRBHfdjn7PJ; Wed, 8 Sep 2010 23:01:08 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id F37FA3A6980; Wed, 8 Sep 2010 23:01:07 -0700 (PDT)
Received: from [203.219.211.243] (helo=[192.168.0.6]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1OtaCP-00053X-Az; Thu, 09 Sep 2010 16:01:29 +1000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Thu, 09 Sep 2010 16:01:23 +1000
Subject: Re: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix Delegation for NEMO) to Proposed Standard
From: Hesham Soliman <hesham@elevatemobile.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <C8AEB553.14F15%hesham@elevatemobile.com>
Thread-Topic: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix Delegation for NEMO) to Proposed Standard
Thread-Index: ActP5G4wmhuksKcbiE214+NbOC+BIg==
In-Reply-To: <B1762FEA-D894-4D15-82B1-2D6A3AFFF481@ericsson.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-User: hesham@elevatemobile.com
X-Mailman-Approved-At: Thu, 09 Sep 2010 08:15:42 -0700
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:01:09 -0000

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

v2.23.0 | Report a Bug | By Email