Re: [shim6] AD review of draft-ietf-shim6-multihome-shim-api

Shinta Sugimoto <shinta@sfc.wide.ad.jp> Wed, 20 October 2010 09:52 UTC

Return-Path: <shinta@sfc.wide.ad.jp>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 922113A684A for <shim6@core3.amsl.com>; Wed, 20 Oct 2010 02:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.1
X-Spam-Level: **
X-Spam-Status: No, score=2.1 tagged_above=-999 required=5 tests=[AWL=1.196, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GKPTGzKz3ADk for <shim6@core3.amsl.com>; Wed, 20 Oct 2010 02:52:45 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id B777A3A683F for <shim6@ietf.org>; Wed, 20 Oct 2010 02:52:45 -0700 (PDT)
Received: from localhost.localdomain (unknown [IPv6:2001:380:633:2:20b:cdff:fefb:2a8]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id B6FAC27807F; Wed, 20 Oct 2010 18:54:12 +0900 (JST)
Message-ID: <4CBEBADD.2090409@sfc.wide.ad.jp>
Date: Wed, 20 Oct 2010 18:48:13 +0900
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
User-Agent: Thunderbird 2.0.0.6 (X11/20070809)
MIME-Version: 1.0
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
References: <20100816114202.1241.59079.idtracker@localhost> <4535F52C-8E78-4CBE-8983-DD7195722865@apnic.net> <4C69DE84.8010 7 06@sfc.wide.ad.jp> <4C91D119.5010101@cs.hut.fi> <4C91E946.6080807@sfc.wi de.ad.jp> <4C920431.2090603@cs.hut.fi> <86C69B19-D385-46A9-B116-5EE19827330 5@apnic. n e t> <4CAA425E.2070906@piuha.net> <4CAEB35B.3020107@cs.hut.fi> < 4CAEDEAD.9060407@piuha.net> <4CAF01F6.3030905@cs.hut.fi> <7CC566635CFE364D8 7DC5803D4712A6C4CEC451999@X CH-NW-10V.nw.nos.boeing.com> <4CB53CCC.3080903@ cs.hut.fi> <7CC566635CFE364D87DC5803D4712A6C4CEC4519A4@XCH-NW-10V.nw.nos.bo eing.com> <4CB68883.7070408@cs.hut.fi> <7CC566635CFE364D87DC5803D4712A6C4CE C4519C0@XCH-NW-10V.nw.nos.boeing.com> <4CB6951F.7040103@sfc.wide.ad.jp> <4C B76C19.208@cs.hut.fi><4CB7DB72.4010800@sfc.wide.ad.jp> <4CB982D3.8080904@cs.hut.fi><4CB9BE31.5020501@sfc.wide.ad.jp> <4CBBEB88.4070704@cs.hut.fi> <4CBC1E45.1010608@sfc.wide.ad.jp> <7CC566635CFE364D87DC5803D4712A6C4CEC451A0D@XCH-NW-10V.nw.nos.boeing.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4CEC451A0D@XCH-NW-10V.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Miika Komu <mkomu@cs.hut.fi>, "shim6@ietf.org" <shim6@ietf.org>
Subject: Re: [shim6] AD review of draft-ietf-shim6-multihome-shim-api
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 09:52:46 -0000

Henderson, Thomas R wrote:
>  >
>> To WG members: please note that I had phone discussion with Miika and
>> came to a common understanding that the following text would suffice:
>>
>> There is, however, an exceptional case where the HIP layer
>> SHOULD accept
>> the request provided that the HIP association is in
>> UNASSOCIATED state.
>> In this exceptional case, the socket layer SHOULD accept the request.
>>
> 
> I'm OK with the above wording.  I think it would be clearer to also refer to section 4.6 of the HIP native API draft (as Miika suggested) where this is explained in more detail, but I noticed that you don't already have the native API draft in the list of references.  Are you trying to avoid the draft dependency?

Thanks for your comment. Yes, I agree that we should add a reference to 
the Section 4.6 of HIP native API document. No, I am not trying to avoid 
any dependency.

Now I am updating the document and I will submit it as soon as possible.

Regards,
Shinta