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

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Wed, 13 October 2010 14:22 UTC

Return-Path: <thomas.r.henderson@boeing.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 433663A6954 for <shim6@core3.amsl.com>; Wed, 13 Oct 2010 07:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.273
X-Spam-Level:
X-Spam-Status: No, score=-106.273 tagged_above=-999 required=5 tests=[AWL=0.326, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 dGjfpPUIunc6 for <shim6@core3.amsl.com>; Wed, 13 Oct 2010 07:22:18 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 4B7523A6959 for <shim6@ietf.org>; Wed, 13 Oct 2010 07:22:18 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o9DENDLl004358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 13 Oct 2010 07:23:14 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o9DENDhn007520; Wed, 13 Oct 2010 09:23:13 -0500 (CDT)
Received: from XCH-NWHT-07.nw.nos.boeing.com (xch-nwht-07.nw.nos.boeing.com [130.247.25.111]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o9DENCNl007502 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 13 Oct 2010 09:23:13 -0500 (CDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-07.nw.nos.boeing.com ([130.247.25.111]) with mapi; Wed, 13 Oct 2010 07:23:12 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Miika Komu'" <mkomu@cs.hut.fi>
Date: Wed, 13 Oct 2010 07:23:12 -0700
Thread-Topic: [shim6] AD review of draft-ietf-shim6-multihome-shim-api
Thread-Index: Actqk0Kke8BFlpCqQQ21u2oKcr2YKQATmH6Q
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CEC4519A4@XCH-NW-10V.nw.nos.boeing.com>
References: <20100816114202.1241.59079.idtracker@localhost> <4C692876.60802@ cs.hut.fi> <4535F52C-8E78-4CBE-8983-DD7195722865@apnic.net> <4C69DE84.8010 7 06@sfc.wide.ad.jp> <4C91D119.5010101@cs.hut.fi> <4C91E946.6080807@sfc.wide.ad.jp> <4C920431.2090603@cs.hut.fi> <86C69B19-D385-46A9-B116-5EE198273305@apnic.n e t> <4CAA425E.2070906@piuha.net> <4CAEB35B.3020107@cs.hut.fi> <4CAEDEAD.9060407@piuha.net> <4CAF01F6.3030905@cs.hut.fi> <7CC566635CFE364D87DC5803D4712A6C4CEC451999@XCH-NW-10V.nw.nos.boeing.com> <4CB53CCC.3080903@cs.hut.fi>
In-Reply-To: <4CB53CCC.3080903@cs.hut.fi>
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
Cc: shim6 <shim6@ietf.org>, "kristian.slavov@ericsson.com" <kristian.slavov@ericsson.com>
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, 13 Oct 2010 14:22:19 -0000

> -----Original Message-----
> From: Miika Komu [mailto:mkomu@cs.hut.fi]
> Sent: Tuesday, October 12, 2010 10:00 PM
> To: Henderson, Thomas R
> Cc: Jari Arkko; shim6; kristian.slavov@ericsson.com
> Subject: Re: [shim6] AD review of draft-ietf-shim6-multihome-shim-api
>
> Hi,
>
> On 12/10/10 20:54, Henderson, Thomas R wrote:
>
> >> -----Original Message----- From: Miika Komu
> >> [mailto:mkomu@cs.hut.fi] Sent: Friday, October 08, 2010 4:35 AM To:
> >> Jari Arkko Cc: Shinta Sugimoto; shim6;
> >> kristian.slavov@ericsson.com; Henderson, Thomas R Subject: Re:
> >> [shim6] AD review of draft-ietf-shim6-multihome-shim-api
> >>
> > <snip>
> >
> >>> However, IIRC in HIP you cannot propose a locator for the other
> >>> side, only for yourself. Or is your plan that you move the
> >> session to
> >>> another locator and that if that node happens to be the
> >> wrong one, then
> >>> it cannot decrypt the traffic anyway, so there's no damage?
> >>
> >> (There has to be a successful return routability check before any
> >> traffic is transported)
> >>
> >> There's two use cases:
> >>
> >> 1. No HIP session (i.e. SHIM context) yet and application knows the
> >> IP address of the peer. 2. An existing HIP session, connectivity
> >> lost but the application (with the assistance from the user) can
> >> help to rediscover the peer.
> >>
> >> Now remembering this "unknown" part again, I think the MAY was
> >> referring to the first case described above. It should be ok for
> >> the application give a hint especially in the absence of better
> >> knowledge from the SHIM.
> >
> > I agree; that was my understanding of the main intent of this clause
> > (to allow the application to provide the shim with a hint of the
> > binding to IP address).
> >
> > However, in reviewing section 6.2, it seems like this would fail
> > since there is no shim context for the socket.  If I'm not mistaken,
> > the draft seems to forbid applications running in opportunistic HIP
> > mode because this API requires that shim context be associated with
> > the socket for the ancillary data to be accepted.
>
> right:
>
> http://tools.ietf.org/html/draft-ietf-hip-native-api-12#section-4.6
>
> "Another use case is to use the opportunistic mode.."

Yes, but the HIP native API draft does not say anything about
overriding the rules in the shim6 API specification concerning
the need for shim context.  Maybe that should be clarified in
the HIP API draft.

- Tom