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

Hesham Soliman <hesham@elevatemobile.com> Sat, 11 September 2010 23:03 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 91D333A6802; Sat, 11 Sep 2010 16:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 78LRAZ3Smzpv; Sat, 11 Sep 2010 16:03:09 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id AB5003A677E; Sat, 11 Sep 2010 16:03:08 -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 1OuZ6W-0003Ah-Qm; Sun, 12 Sep 2010 09:03:29 +1000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Sun, 12 Sep 2010 09:03: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: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <C8B247DB.150B3%hesham@elevatemobile.com>
Thread-Topic: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix Delegation for NEMO) to Proposed Standard
Thread-Index: ActSBYiVXnNWoVO6mUaJsnhbRS1zAw==
In-Reply-To: <4C8B7486.9050405@gmail.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: Mon, 13 Sep 2010 11:52:52 -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: Sat, 11 Sep 2010 23:03:10 -0000

>> =>  I thought we were discussing the specific issue of how to solve this
>> problem in _this_WG_ as I mentioned in my first email. I know what the RFC
>> says and I wouldn't have done it this way but given this, I don't know how
>> else you can solve it _here_.
> 
> I am open to solve it here and I have suggestion :
> 
> - make DHCPv6-PD-NEMO assign a default route to the Mobile Router at
>    home.
> 
> What do you think?

=> That can work but I don't understand why you don't like the host on
egress interface behaviour. The RFC seems inconsistent on its requirements
for the egress interface at home, but it's been a long time since I read it
so I may have forgotten some of the reasons. I think it can work and at
least it will lead to a consistent implementation.
Extending DHCP can work but whether it's done here or in dhc or mif is not
really important to me.

Hesham

> 
> I also followed advice and went asking to DHC WG.  I got redirected to
> MIF soon-Charter DHCP options route table, and got mentioned
> draft-ietf-v6ops-ipv6-cpe-router req W-3 talking DHCPv6-PD and default
> route.
> 
> Alex
> 
> 
>> 
>> Hesham
>> 
>> 
>> 
>> 
>> 
>