Re: [shim6] Unknown destination locator [was: WG Last Call for draft-ietf-shim6-multihome-shim-api]

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 22 December 2009 19:34 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 218AB3A68AA for <shim6@core3.amsl.com>; Tue, 22 Dec 2009 11:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.627
X-Spam-Level:
X-Spam-Status: No, score=-2.627 tagged_above=-999 required=5 tests=[AWL=-0.027, BAYES_00=-2.599]
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 8O0NbUjNthyb for <shim6@core3.amsl.com>; Tue, 22 Dec 2009 11:34:54 -0800 (PST)
Received: from mail-yw0-f185.google.com (mail-yw0-f185.google.com [209.85.211.185]) by core3.amsl.com (Postfix) with ESMTP id 3F5C33A657C for <shim6@ietf.org>; Tue, 22 Dec 2009 11:34:54 -0800 (PST)
Received: by ywh15 with SMTP id 15so6763562ywh.5 for <shim6@ietf.org>; Tue, 22 Dec 2009 11:34:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=FsDMJz4FaMD65WEIdN6RuBZBLsdAcGwgAfks19bf7iQ=; b=Z316QlQ/i5zkEaT8yYRRb8HD38ktoB67FRmGtwVmtr3d6rnfBvLvqfG8wtgmM8vsXj xqgHKnu//buKtdkDOCS8LYOBGMVp2qwx8aBWxQf+qy9Jsj/W6+txCav47r4iE6p0Ni/t Y7d4/QnNM/kix38u3Pyr2zY+wn2gpTyz7/kk4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=En68QjKdSK4XHCbCFZmpCSXj65HHfrRk2S73P1xUpkgYM2utfPsTHVexRvWdm5J6r0 1iVTOD8UOZKrJRijW7gw4D34PIc+swQp0dkzI8aM2eDY+4hS+LiNIRWzm3SXwQY5D9Xm ISxU712ghonUSCYt01RSMe+U5sVzuNaxGnoPA=
Received: by 10.150.24.34 with SMTP id 34mr13831543ybx.239.1261510475206; Tue, 22 Dec 2009 11:34:35 -0800 (PST)
Received: from ?10.1.1.4? ([121.98.142.15]) by mx.google.com with ESMTPS id 21sm2502737ywh.16.2009.12.22.11.34.33 (version=SSLv3 cipher=RC4-MD5); Tue, 22 Dec 2009 11:34:34 -0800 (PST)
Message-ID: <4B311F41.3010902@gmail.com>
Date: Wed, 23 Dec 2009 08:34:25 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Shinta Sugimoto <shinta.sugimoto@ericsson.com>
References: <541EE6CB2B85BE4389E2910C9B4BC77E01C5081FBC@ESGSCCMS0002.eapac.ericsson.se>
In-Reply-To: <541EE6CB2B85BE4389E2910C9B4BC77E01C5081FBC@ESGSCCMS0002.eapac.ericsson.se>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "shim6@ietf.org" <shim6@ietf.org>
Subject: Re: [shim6] Unknown destination locator [was: WG Last Call for 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: Tue, 22 Dec 2009 19:34:55 -0000

Cases 1 and 3 make sense to me. Maybe for case 2 it should be SHOULD
reject the request (because we might have some future shim design
that works differently). Or add a note that the rules may need to be
modified for some future shim design.

Thanks
   Brian

On 2009-12-23 06:37, Shinta Sugimoto wrote:
> Hi all,
> 
> As pointed out by HIP experts (Thomas and Miika), we need to consider exceptional case for HIP when the application sets unknown destination locator for the socket.  Such an exceptional handling will allow application to provide the destination locator to the HIP.
> 
> 1. The multihoming shim sub-layer checks if address family of the socket is AF_INET6 (all the SHIM6 cases would fall into this case).  If so, the shim must reject the request.
> 2. Otherwise, the shim checks if there is any multihome shim context associated with the socket.  If there is any, the shim must reject the request.
> 3. If there is none, and the multihome shim sub-layer turns out to be HIP, the shim SHOULD accept the request (accordingly, the shim being HIP implementation will probably initiate HIP basic exchange by sending I1 packet to the requested locator)
> 
> Does the above make sense?  Please comment.
> 
> Regards,
> Shinta
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6
>