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 06:13 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 E02AD3A6838; Fri, 10 Sep 2010 23:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level:
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116, 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 vdFx4COazCRx; Fri, 10 Sep 2010 23:13:35 -0700 (PDT)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id A52AD3A6837; Fri, 10 Sep 2010 23:13:34 -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 1OuJLY-0000qq-O3; Sat, 11 Sep 2010 16:13:57 +1000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Sat, 11 Sep 2010 16:13:51 +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: <C8B15B3F.15082%hesham@elevatemobile.com>
Thread-Topic: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix Delegation for NEMO) to Proposed Standard
Thread-Index: ActReIDbcKGjpMrzp0+1d0U1zBD8XA==
In-Reply-To: <4C8A41ED.40402@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: Mon, 13 Sep 2010 11:52:15 -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 06:13:37 -0000

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_.

Hesham