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

RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com> Wed, 08 November 2006 22:32 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhvyY-0005CU-Ea; Wed, 08 Nov 2006 17:32:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhvyX-0005CK-FD for nemo@ietf.org; Wed, 08 Nov 2006 17:32:53 -0500
Received: from ug-out-1314.google.com ([66.249.92.172]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhvyW-0003Cz-4f for nemo@ietf.org; Wed, 08 Nov 2006 17:32:53 -0500
Received: by ug-out-1314.google.com with SMTP id 72so41652ugd for <nemo@ietf.org>; Wed, 08 Nov 2006 14:32:51 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=EmRrMWnjNRstEAKytmaScAxyGNqvkotdjaJMgLiCP3zxgtsBo3wVBIey/fHhZ4xx/rSrb5wFwiu8wu6jvdHedy8GtTlmsWlGHNjRrcmzghXtD/LfDT0Df14B2ZYCsj3C3FXWHHOWfCq+EeH9spjBDXpBr4nngDYbgLRIdwafDj4=
Received: by 10.78.166.7 with SMTP id o7mr188592hue.1163025170675; Wed, 08 Nov 2006 14:32:50 -0800 (PST)
Received: from ?130.129.65.179? ( [130.129.65.179]) by mx.google.com with ESMTP id 39sm10681253hui.2006.11.08.14.32.48; Wed, 08 Nov 2006 14:32:50 -0800 (PST)
In-Reply-To: <455230C6.4080507@kniveton.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>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <4B609BE4-A018-408D-B057-3530699C4566@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [nemo] About Test Specification in IPv6 Ready Logo
Date: Thu, 09 Nov 2006 07:32:37 +0900
To: "T.J. Kniveton" <tj@kniveton.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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 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