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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 10 September 2010 12:00 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 269873A6830; Fri, 10 Sep 2010 05:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[AWL=0.161, 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 37Sm7FlPBvtP; Fri, 10 Sep 2010 05:00:45 -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 DE7F83A6817; Fri, 10 Sep 2010 05:00:44 -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 o8AC0m8T025565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Sep 2010 14:00:48 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id o8AC0m3o010712; Fri, 10 Sep 2010 14:00:48 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id o8AC0lnx028276; Fri, 10 Sep 2010 14:00:48 +0200
Message-ID: <4C8A1DEF.9050403@gmail.com>
Date: Fri, 10 Sep 2010 14:00:47 +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: <C8B03E68.14FA4%hesham@elevatemobile.com>
In-Reply-To: <C8B03E68.14FA4%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: Fri, 10 Sep 2010 12:00:46 -0000

Le 10/09/2010 11:58, Hesham Soliman a écrit :
>
>
>
> On 10/09/10 7:55 PM, "Alexandru
> Petrescu"<alexandru.petrescu@gmail.com> wrote:
>
>> Le 10/09/2010 11:48, Hesham Soliman a écrit :
>>>
>>>
>>>>>
>>>>> =>    Who cares, specify it in your product description. The
>>>>>  IETF doesn't specify how to build products.
>>>>
>>>> Hmm... to me it is a very IETF sensitive issue the Router vs
>>>> Host. For example, an ND spec says distinctively what a Host
>>>> and what a Router does, e.g. a Host does not respond to Router
>>>>  Solicitation.
>>>
>>> =>   Yes and it does so on a per-interface basis, not on a
>>> per-machine basis.
>>
>> Yes, and the Mobile Router is a Router on its egress interface
>> when connected at home, as per spec.  It is that interface that
>> needs a default route automatically configured.
>
> =>  Ok, so you're happy with it being half host half router when it's
> away from home?

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.

> If so then let it do the same at home. Otherwise, I don't know how
> you want to fix this in this WG.

It would mean to specify it to be a at home, be first a Host (get
default route) then change and become a Router, but still at home.

This behaviour could be set in the DHCPv6-PD-NEMO draft, being under
discussion now.

Alex

>
> Hesham
>
>
>