Re: [Hipsec] Completing 5201 state machine

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Tue, 19 October 2010 14:03 UTC

Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E51E3A6813 for <hipsec@core3.amsl.com>; Tue, 19 Oct 2010 07:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.204
X-Spam-Level:
X-Spam-Status: No, score=-106.204 tagged_above=-999 required=5 tests=[AWL=0.395, 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 zHQ8AakYVSMj for <hipsec@core3.amsl.com>; Tue, 19 Oct 2010 07:03:15 -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 029A03A680A for <hipsec@ietf.org>; Tue, 19 Oct 2010 07:03:13 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o9JE4YGE004157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 19 Oct 2010 07:04:35 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o9JE4YCj003335; Tue, 19 Oct 2010 07:04:34 -0700 (PDT)
Received: from XCH-NWHT-07.nw.nos.boeing.com (xch-nwht-07.nw.nos.boeing.com [130.247.25.111]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o9JE4YDY003322 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 19 Oct 2010 07:04:34 -0700 (PDT)
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; Tue, 19 Oct 2010 07:04:34 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: 'Tobias Heer' <heer@cs.rwth-aachen.de>
Date: Tue, 19 Oct 2010 07:04:32 -0700
Thread-Topic: [Hipsec] Completing 5201 state machine
Thread-Index: Actvclr7apmJuL+MQ06xHdXO6qwUNAAI/bqw
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CEC451A0B@XCH-NW-10V.nw.nos.boeing.com>
References: <917A9DF6-17C4-4AAF-9132-1A865D0A824B@cs.rwth-aachen.de><7CC5666 35CFE364D87DC5803D4712A6C4CEC451A09@XCH-NW-10V.nw.nos.boeing.com> <BA13FE85-80E4-470C-BAD7-7348E1F7816A@cs.rwth-aachen.de>
In-Reply-To: <BA13FE85-80E4-470C-BAD7-7348E1F7816A@cs.rwth-aachen.de>
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: HIP WG <hipsec@ietf.org>
Subject: Re: [Hipsec] Completing 5201 state machine
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 14:03:16 -0000

> -----Original Message-----
> From: Tobias Heer [mailto:heer@cs.rwth-aachen.de]
> Sent: Tuesday, October 19, 2010 2:45 AM
> To: Henderson, Thomas R
> Cc: HIP WG
> Subject: Re: [Hipsec] Completing 5201 state machine
>
> Hi Tom,
>
> thanks for your review of this!
>
> Am 19.10.2010 um 01:41 schrieb Henderson, Thomas R:
>
> > Tobias, I reviewed the OpenHIP behavior to these white spots, below:
> >
> >> -----Original Message-----
> >> From: hipsec-bounces@ietf.org
> >> [mailto:hipsec-bounces@ietf.org] On Behalf Of Tobias Heer
> >> Sent: Wednesday, October 13, 2010 9:13 AM
> >> To: HIP WG
> >> Subject: [Hipsec] Completing 5201 state machine
> >>
> [...]
> >>
> >> 1.) Receive CLOSE in state I2-sent:
> >> ------------------------------
<snip>
> >
> > OpenHIP allows CLOSE in states ESTABLISHED, CLOSING,
> CLOSED, and R2_SENT, but does not process it in this state.
> >

<snip>

>
> Above you said that OpenHIP wouldn't process CLOSE messages
> in state R2_SENT. What do you mean by that? Isn't sending a
> CLOSE_ACK (as you mention for 2.) such processing? Am I
> confusing something here?
>

Sorry for not being clear; the "this state" in the above explanation refers to state I2-sent, not R2-sent.

- Tom