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

Wassim Haddad <wassim.haddad@ericsson.com> Sat, 11 September 2010 16:50 UTC

Return-Path: <wassim.haddad@ericsson.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 D46603A6875; Sat, 11 Sep 2010 09:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.088
X-Spam-Level:
X-Spam-Status: No, score=-103.088 tagged_above=-999 required=5 tests=[AWL=-0.489, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 rRsjQdFBEv8h; Sat, 11 Sep 2010 09:50:39 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id C4DAD3A6828; Sat, 11 Sep 2010 09:50:34 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id o8BH0iG7014986; Sat, 11 Sep 2010 12:00:45 -0500
Received: from [164.48.125.82] (147.117.20.213) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.2.234.1; Sat, 11 Sep 2010 12:50:48 -0400
Subject: Re: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix Delegation for NEMO) to Proposed Standard
MIME-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/signed; boundary="Apple-Mail-1-973966750"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Wassim Haddad <wassim.haddad@ericsson.com>
In-Reply-To: <4C8B7486.9050405@gmail.com>
Date: Sat, 11 Sep 2010 09:50:44 -0700
Message-ID: <2A7192AA-6EC9-41DC-B32D-A1C8B6798452@ericsson.com>
References: <C8B15B3F.15082%hesham@elevatemobile.com> <4C8B7486.9050405@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: mext <mext@ietf.org>, IETF Discussion <ietf@ietf.org>, Hesham Soliman <hesham@elevatemobile.com>
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 16:50:41 -0000

On Sep 11, 2010, at 5:22 AM, Alexandru Petrescu wrote:

> Le 11/09/2010 08:13, Hesham Soliman a écrit :
>> 
>> 
>> 
>> On 11/09/10 12:34 AM, "Alexandru Petrescu"<alexandru.petrescu@gmail.com>
>> wrote:
>> 
>>> Le 10/09/2010 14:12, Hesham Soliman a écrit :
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> When it is away from home it is fully a Host on the egress
>>>>> interface. When at home fully Router on same.  I am happy with it
>>>>> this way.
>>>>> 
>>>> 
>>>> =>   Ok that doesn't make any sense to me.
>>> 
>>> Well, let me rephrase as the RFC text puts it: when the MR is at home it
>>> joins the all-routers multicast address, otherwise it joins the
>>> all-hosts address.  ND spec says similar.  Similarly, when MR at home it
>>> can send RAs on the egress, if away it MUST NOT send RAs on it.  It must
>>> always send RAs on the ingress.  This is to make sure MR doesn't break
>>> the Internet routing.
>>> 
>>> Does this sound better?
>> 
>> =>  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?
> 
> 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.

=> Then we better wait for this draft to move forward. 


Regards,

Wassim H.