Re: [nemo] About Test Specification in IPv6 Ready Logo

"K.Kawaguchi" <kawaguti@ysknet.co.jp> Tue, 21 November 2006 10:41 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmT3t-0001C0-22; Tue, 21 Nov 2006 05:41:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmT3r-0001Bu-QU for nemo@ietf.org; Tue, 21 Nov 2006 05:41:07 -0500
Received: from yskfw1.ysknet.co.jp ([210.169.255.3] helo=ksns.ks.ysknet.co.jp) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GmT3p-0001VA-7r for nemo@ietf.org; Tue, 21 Nov 2006 05:41:07 -0500
Received: (qmail 6728 invoked from network); 21 Nov 2006 19:41:03 +0900
Received: from (HELO MIP6-236) (@) by with SMTP; 21 Nov 2006 19:41:03 +0900
To: keiichi@iijlab.net
Subject: Re: [nemo] About Test Specification in IPv6 Ready Logo
From: "K.Kawaguchi" <kawaguti@ysknet.co.jp>
References: <7892795E1A87F04CADFCCF41FADD00FC030C3A82@xmb-ams-337.emea.cisco.com> <200611202052.HAJ17677.BHBLJXVU@ysknet.co.jp> <4561A83F.20807@motorola.com> <200611211830.ICF21007.ULVJBHXB@ysknet.co.jp> <F6F35ADE-D2B1-4F55-A130-E51DE4F05B20@iijlab.net>
In-Reply-To: <F6F35ADE-D2B1-4F55-A130-E51DE4F05B20@iijlab.net>
Message-Id: <200611211941.EFI30733.UVJBBLXH@ysknet.co.jp>
X-Mailer: Winbiff [Version 2.43 PL1]
X-Accept-Language: ja,en
Date: Tue, 21 Nov 2006 19:41:02 +0900
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
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>
Errors-To: nemo-bounces@ietf.org

Hi,

I do the supplementation explanation of Logo NEMO.
We will divide the category of Logo NEMO.
It is the following when enumerating it in the example based on
draft-ietf-nemo-home-network-models-06.txt.


models          | Home address from   | Home address from
                | Home network Prefix | Mobile network prefix
----------------------------------------------------------------
NEMO Extended   |           1         |         2
Home Network    |                     |
----------------------------------------------------------------
NEMO Aggregated |           3         |         4
Home Network    |                     |
----------------------------------------------------------------


The product of each area doesn't have the interconnectivity. Moreover,
there is not default either. Therefore, we divide separately on NEMO LOGO.
(A rich product will cover two or more areas.)

Because routing protocol is not necessary in area-1, routing protocol is
not put under the area-1 test condition.
Because routing protocol is necessary in area-2, one routing protocol is
decided under the area-2 test condition.
I'm sorry, we are examining many about area-3 and area-4.


Best regards
---
Kiyoaki KAWAGUCHI



Keiichi SHIMA wrote:

> On 2006/11/21, at 18:30, K.Kawaguchi wrote:
> 
> > I understand NEMO doesn't provide for the routing protocol.
> > On the other hand, the test condition of IPv6 Ready Logo NEMO will be
> > fixed to the one routing protocol. However, please understand we don't
> > intend that one routing protocol be 'MUST'. Because the same routing
> > protocol is necessary to connect, we have to choose one routing  
> > protocol
> > for the test.
> 
> If I remember correctly, running a routing protocol between a mobile  
> router and a home agent is not a MUST item.
> 
> Some implementations may not implement the dynamic routing part, but  
> we can still call them RFC3963 compliant.  The dynamic routing  
> protocol test may be in the advanced test spec, but should not be in  
> the basic test spec, I think.
> 
> ---
> Keiichi SHIMA
> IIJ Research Laboratory <keiichi@iijlab.net>
> WIDE Project <shima@wide.ad.jp>