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

"Pascal Thubert \(pthubert\)" <pthubert@cisco.com> Mon, 20 November 2006 10:00 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gm5x4-0006Ee-5V; Mon, 20 Nov 2006 05:00:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gm5x2-0006EY-KQ for nemo@ietf.org; Mon, 20 Nov 2006 05:00:32 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gm5x1-0005ku-7l for nemo@ietf.org; Mon, 20 Nov 2006 05:00:32 -0500
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 20 Nov 2006 11:00:31 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kAKA0Udh022600; Mon, 20 Nov 2006 11:00:30 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kAKA0SxL010734; Mon, 20 Nov 2006 11:00:30 +0100 (MET)
Received: from xmb-ams-337.cisco.com ([144.254.231.82]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Nov 2006 11:00:27 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [nemo] About Test Specification in IPv6 Ready Logo
Date: Mon, 20 Nov 2006 11:00:22 +0100
Message-ID: <7892795E1A87F04CADFCCF41FADD00FC030C3A82@xmb-ams-337.emea.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [nemo] About Test Specification in IPv6 Ready Logo
Thread-Index: AccHy9fpew/r/4nqRni1bGDbsqDdxQEvpWWg
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "K.Kawaguchi" <kawaguti@ysknet.co.jp>, nemo@ietf.org
X-OriginalArrivalTime: 20 Nov 2006 10:00:27.0070 (UTC) FILETIME=[B4251DE0:01C70C8A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1584; t=1164016830; x=1164880830; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pthubert@cisco.com; z=From:=20=22Pascal=20Thubert=20\(pthubert\)=22=20<pthubert@cisco.com> |Subject:=20RE=3A=20[nemo]=20About=20Test=20Specification=20in=20IPv6=20R eady=20Logo |Sender:=20; bh=c6w5L/WGcZ72OWVFZNXtu4/b+Iq/t4DNu6en75rSCYk=; b=ZqdUem1/Mzg+yV/ZneUraoUpBSUMaUCkL7ZnjofDd+pE+TUMhzjSjEbMO1nFhw54HotDADfZ oenpYEpkwCODMyNzVaKqybUs1vC17ZkiDa+RijBVb9pu7GwhcLCRaoDf;
Authentication-Results: ams-dkim-2; header.From=pthubert@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc:
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

Dear all:

I suggest you take a look at 
http://www.ietf.org/internet-drafts/draft-ietf-nemo-home-network-models-
06.txt 
which has considerations for this problem. 

It is quite a bit late by if you think that some text is missing please
let us know. 

Pascal

>-----Original Message-----
>From: K.Kawaguchi [mailto:kawaguti@ysknet.co.jp]
>Sent: Tuesday, November 14, 2006 10:00 AM
>To: nemo@ietf.org
>Subject: Re: [nemo] About Test Specification in IPv6 Ready Logo
>
>Hi,
>
>Romain KUNTZ wrote:
>>
>> Sri Gundavelli wrote:
>> > Using a HoA from MNP introduces some interesting situation, when
>> > the MR returns home. The MNP is anchored at the HA and when the
>> > MR returns home, there is no routing state for that prefix at
>> > the HA. At home, is the MR a bridge ? Is the prefix split between
>> > HA and MR and MR and itself ? If some one case fix the text in
>> > 3963 and address all the issues, I'm ok supporting this. Currently,
>> > we dont support this.
>>
>> When returning home, the MR could configure an autoconfigured address
on
>> its egress interface and send routing protocol messages (section
5.8).
>> Are there any issues with such solution?
>
>If the routing protocol is indispensable, I want to know which routing
>protocol should provide.
>I think that default is necessary to secure the interoperability and
the
>NEMO connection test between many products. I think the default only
now
>to be acceptable, even if the default will be changed in the future.
>
>
>Best regards
>---
>Kiyoaki KAWAGUCHI