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

Shinta Sugimoto <shinta.sugimoto@ericsson.com> Tue, 22 December 2009 17:38 UTC

Return-Path: <shinta.sugimoto@ericsson.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 566853A68A2 for <shim6@core3.amsl.com>; Tue, 22 Dec 2009 09:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 kbOuf3MEil8K for <shim6@core3.amsl.com>; Tue, 22 Dec 2009 09:38:06 -0800 (PST)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id 57F8F3A67B5 for <shim6@ietf.org>; Tue, 22 Dec 2009 09:38:06 -0800 (PST)
X-AuditID: c1b4fb24-b7beeae000003a71-ef-4b3103ec10cb
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw5.ericsson.se (Symantec Mail Security) with SMTP id 96.C8.14961.CE3013B4; Tue, 22 Dec 2009 18:37:48 +0100 (CET)
Received: from esessmw0191.eemea.ericsson.se (153.88.115.86) by esessmw0197.eemea.ericsson.se (153.88.115.87) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 22 Dec 2009 18:37:48 +0100
Received: from esgscmw0054.eapac.ericsson.se (146.11.115.120) by esessmw0191.eemea.ericsson.se (153.88.115.84) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 22 Dec 2009 18:37:47 +0100
Received: from ESGSCCMS0002.eapac.ericsson.se ([169.254.1.218]) by esgscmw0054.eapac.ericsson.se ([146.11.115.120]) with mapi; Wed, 23 Dec 2009 01:37:45 +0800
From: Shinta Sugimoto <shinta.sugimoto@ericsson.com>
To: "shim6@ietf.org" <shim6@ietf.org>
Date: Wed, 23 Dec 2009 01:37:10 +0800
Thread-Topic: Unknown destination locator [was: WG Last Call for draft-ietf-shim6-multihome-shim-api]
Thread-Index: AcqDLWN0yo1wFh13Tnug5tCS8pK7hQ==
Message-ID: <541EE6CB2B85BE4389E2910C9B4BC77E01C5081FBC@ESGSCCMS0002.eapac.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [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 17:38:07 -0000

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