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

Hesham Soliman <hesham@elevatemobile.com> Fri, 10 September 2010 09:58 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 06FCC3A67CC; Fri, 10 Sep 2010 02:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level:
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[AWL=0.175, 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 WGKwRXIZ5CBn; Fri, 10 Sep 2010 02:58:12 -0700 (PDT)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id 36EAE3A6359; Fri, 10 Sep 2010 02:58:11 -0700 (PDT)
Received: from [203.219.211.243] (helo=[192.168.0.6]) by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1Ou0NP-0004qS-Gs; Fri, 10 Sep 2010 19:58:35 +1000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Fri, 10 Sep 2010 19:58:32 +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: <C8B03E68.14FA4%hesham@elevatemobile.com>
Thread-Topic: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix Delegation for NEMO) to Proposed Standard
Thread-Index: ActQzrm/JXIoZN00ikGwbKEDHsYB1Q==
In-Reply-To: <4C8A0093.9090906@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-User: hesham@elevatemobile.com
X-Mailman-Approved-At: Fri, 10 Sep 2010 12:06:13 -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: Fri, 10 Sep 2010 09:58:13 -0000

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? If so then let it do the same at home. Otherwise, I don't know
how you want to fix this in this WG.

Hesham