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

Sri Gundavelli <sgundave@cisco.com> Fri, 10 November 2006 22:03 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GieTW-0003Am-Mk; Fri, 10 Nov 2006 17:03:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GieTT-0002eB-CK for nemo@ietf.org; Fri, 10 Nov 2006 17:03:47 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GieH8-0002Z7-Ow for nemo@ietf.org; Fri, 10 Nov 2006 16:51:04 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-5.cisco.com with ESMTP; 10 Nov 2006 13:51:03 -0800
X-IronPort-AV: i="4.09,410,1157353200"; d="scan'208"; a="342738643:sNHT53329432"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kAALp2qc030002; Fri, 10 Nov 2006 13:51:02 -0800
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kAALp1W5024764; Fri, 10 Nov 2006 13:51:02 -0800 (PST)
Date: Fri, 10 Nov 2006 13:51:01 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: Romain KUNTZ <kuntz@sfc.wide.ad.jp>
Subject: Re: [nemo] About Test Specification in IPv6 Ready Logo
In-Reply-To: <45544E8F.5090509@sfc.wide.ad.jp>
Message-ID: <Pine.GSO.4.63.0611101340510.16866@irp-view7.cisco.com>
References: <452ABB53.3020104@azairenet.com><200610311000.FAE39546.XHBVJBLU@ysknet.co.jp><FC43BE09-C254-4B5C-8FD3-6CF9D88B9131@iijlab.net><20061105174404.1b42e076.thierry.ernst@inria.fr><454E1A8B.4090607@azairenet.com> <200611081513.ADD60469.HJVBULBX@ysknet.co.jp> <455230C6.4080507@kniveton.com> <4B609BE4-A018-408D-B057-3530699C4566@gmail.com> <45544E8F.5090509@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3002; t=1163195462; x=1164059462; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sgundave@cisco.com; z=From:=20Sri=20Gundavelli=20<sgundave@cisco.com> |Subject:=20Re=3A=20[nemo]=20About=20Test=20Specification=20in=20IPv6=20R eady=20Logo |Sender:=20; bh=o6ygzBx4oMaYdr3t9ZP1t3umm6BEOSZ9HM7zlgcsD9Y=; b=upE+SADw5SkXIbYcsxY5u2UwRNTpgcUP3bqWqepGj45fyWVpUQaQq1Nl62cOpHTMR+pyBwYB aXvlWgi94zSUgEMmXBu6kJXvD+GyJWW2Gpc8LMC9dr/vfCLh7VUgy+I2;
Authentication-Results: sj-dkim-2; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
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 Romain,


On Fri, 10 Nov 2006, Romain KUNTZ wrote:

> Hi,
>
> Being able to register an HoA from a MNP may be more important on the HA
> than on the MR, for interoperability purposes. This could bring a new
> option: being a basic feature on the HA, and a advanced one on the MR.
>

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.



> I personally like this way of configuring the MR, as the HA does not
> need to deal with 2 prefixes anymore (one to build the MR's HoA, and one
> MNP to delegate to the MR), and just need to delegate an MNP to the MR.
>

But, at a cost of configuration complexity. If are clear as how the
routing/configuration looks when the MR is at home, in this scenario,
I'm ok with this.


> FYI the NEPL implementation is designed to support also HoA from MNP,
> although a small bug prevents to do so in the current version (could get
> it working with a small fix).
>
> Regards,
>
> -- 
> Romain KUNTZ
> kuntz@sfc.wide.ad.jp
>
>
> RYUJI WAKIKAWA wrote:
>>  Hi TJ
>>
>>  On 2006/11/09, at 4:32, T.J. Kniveton wrote:
>> 
>> >  K.Kawaguchi wrote:
>> > >  Hi Chairs and all,
>> > > 
>> > >  I explain the selection and the classification of test item on the 
>> > >  Logo
>> > >  test specification in section 7 more. And I add the Idea-5 in section 
>> > >  5.
>> > > 
>> > >  We want the evidence of the consensus/Idea that IETF NEMO WG agreed.
>> > >  If possible, please consolidate it at the meeting.
>> > > 
>> >  Hi,
>> > 
>> >  The list of items to go into your testing program is not a work item for 
>> >  NEMO, and although you can gather informal opinions from the list, there 
>> >  would not be working group consensus provided to any Logo or testing 
>> >  program run by an independent entity. It would be up to you to decide 
>> >  what features you want to certify for your Logo program.
>>
>>  Regardless of logo, it is true that the RFC 3963 is vague on this.
>>  MR can support either one or both configurations.
>>  I'm not sure whether 3963 will take "Hoa from home prefix" as a default
>>  configuration in future revision,
>>
>>  Regarding to the logo, you can pick one of configuration as a default.
>>  But before making such decision, you should check the below document too.
>>  Aggregated home network is one example to support HoA from MNP.
>>  http://www.ietf.org/internet-drafts/draft-ietf-nemo-home-network-models-06.txt
>>
>>  The current SHISA implementation supports only HoA from the home prefix,
>>  but we knew it's easily extend to support both case.
>>
>>  regards,
>>  ryuji
>> 
>
>