Re: [nemo] WG Last Call on draft-ietf-nemo-terminology

Alexandru Petrescu <alexandru.petrescu@motorola.com> Mon, 21 November 2005 10:48 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ee9E8-0002tI-Tv; Mon, 21 Nov 2005 05:48:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ee9E5-0002tA-Dm for nemo@megatron.ietf.org; Mon, 21 Nov 2005 05:48:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20208 for <nemo@ietf.org>; Mon, 21 Nov 2005 05:48:07 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ee9WU-0006qu-4C for nemo@ietf.org; Mon, 21 Nov 2005 06:07:48 -0500
Received: from az33exr03.mot.com ([10.64.251.233]) by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id jALB19o4006591; Mon, 21 Nov 2005 04:01:09 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8]) by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id jALAwrPl012365; Mon, 21 Nov 2005 04:58:54 -0600 (CST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by zfr01srv02.crm.mot.com (Postfix) with ESMTP id 9B12A865980; Mon, 21 Nov 2005 11:48:30 +0100 (CET)
Message-ID: <4381A5FE.7070801@motorola.com>
Date: Mon, 21 Nov 2005 11:48:30 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Thierry Ernst <ernst@sfc.wide.ad.jp>
Subject: Re: [nemo] WG Last Call on draft-ietf-nemo-terminology
References: <E1EV94s-0000Iv-L1@newodin.ietf.org> <20051028155154.719167e5.ernst@sfc.wide.ad.jp> <43796DA7.3090507@kddilabs.jp> <20051117191448.461c9854.ernst@sfc.wide.ad.jp> <437DEE35.2020703@motorola.com> <20051121114732.45c25787.ernst@sfc.wide.ad.jp>
In-Reply-To: <20051121114732.45c25787.ernst@sfc.wide.ad.jp>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Sender: nemo-bounces@ietf.org
Errors-To: nemo-bounces@ietf.org

Hi Thierry,

Thierry Ernst wrote:
>>>What I didn't like in the term "MNP" is the wording "mobile network"
>>>(many people are still confused with cellular networks for mobile 
>>>devices),
>>
>>Probably use "moving network" instead of "mobile network"?
> 
>>MNP: moving network prefix?
> 
> This term cannot be changed. (see RFC 3753)

Ok.

>>>VMN: assigned to a home link that doesn't belong to the mobile
>>>network
>>
>>VMN: its HA is different than MR's and is not on any link of that MR.
> 
> Not necessarily.  The VMN and the MR can be on the same home link, and
> in this case the VMN doesn't belong to the MR-administered area. In any
> case, as long as the MNN does need to obtain a CoA, it is considered a
> VMN.

Ok.

>>draft nit:
>>
>>>Its address is located within an MNP.
>>
>>"Derived from the MNP"?
> 
> 
> Do you propose a new definition ? If yes, can you state is fully, and
> can we get people to agree / disagree ? Before you do this, is this
> needed, I mean please think to yourself how much it does improve the
> definition (if it does).

It's not a new definition, it's a draft nit.  Within the draft the
phrase "Its address is located within an MNP" appears.  It could be
re-phrased into "Its address is derived from the...".

Alex