Re: [btns] Minor connection-latch problem in AUTH48

"Laganier, Julien" <julienl@qualcomm.com> Tue, 20 October 2009 16:30 UTC

Return-Path: <julienl@qualcomm.com>
X-Original-To: btns@core3.amsl.com
Delivered-To: btns@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 930E828C140 for <btns@core3.amsl.com>; Tue, 20 Oct 2009 09:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.771
X-Spam-Level:
X-Spam-Status: No, score=-103.771 tagged_above=-999 required=5 tests=[AWL=-1.172, BAYES_00=-2.599, 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 ZZ8jYu5rqvZT for <btns@core3.amsl.com>; Tue, 20 Oct 2009 09:30:17 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 52A523A6A1F for <btns@ietf.org>; Tue, 20 Oct 2009 09:30:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1256056211; x=1287592211; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20Nicolas=20Williams=20<Nicolas.Williams@sun.com> |CC:=20"btns@ietf.org"=20<btns@ietf.org>|Date:=20Tue,=202 0=20Oct=202009=2009:30:08=20-0700|Subject:=20RE:=20[btns] =20Minor=20connection-latch=20problem=20in=20AUTH48 |Thread-Topic:=20[btns]=20Minor=20connection-latch=20prob lem=20in=20AUTH48|Thread-Index:=20AcpRDDZrzgFh5vQsTaCUrmT D0p/xMQAlhE9Q|Message-ID:=20<BF345F63074F8040B58C00A186FC A57F1C648C9FA4@NALASEXMB04.na.qualcomm.com>|References: =20<20091015221608.GC907@Sun.COM>=0D=0A=20<BF345F63074F80 40B58C00A186FCA57F1C2A67DF98@NALASEXMB04.na.qualcomm.com> =0D=0A=20<20091016203953.GQ892@Sun.COM>=0D=0A=20<BF345F63 074F8040B58C00A186FCA57F1C2A67DFC1@NALASEXMB04.na.qualcom m.com>=0D=0A=20<20091016211652.GV892@Sun.COM>=0D=0A=20<BF 345F63074F8040B58C00A186FCA57F1C2A67DFD7@NALASEXMB04.na.q ualcomm.com>=0D=0A=20<20091019164014.GF892@Sun.COM>=0D=0A =20<BF345F63074F8040B58C00A186FCA57F1C648C9F4D@NALASEXMB0 4.na.qualcomm.com>=0D=0A=20<20091019221410.GN892@Sun.COM> |In-Reply-To:=20<20091019221410.GN892@Sun.COM> |Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"us-as cii"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5777"=3B=20a=3D"25670561"; bh=xcr2rse8bzRZ1vmfEijCzm5h5KcN2DTrsgUJn+Jw/9I=; b=gxiCAGUSqf2fAJZBW7sUVn1WGw/XBDSX2CzOL4e2WwG9pZV/n48k85B/ 4erz3HfX28Wtv3kci4M6nEcuQ57s4AWnz8FBu3vUl49zpIPpSAJC3BoF4 mMK90JhPqp3Ce1KmHWqeVU3fRJsRYM0r/aNfXJQ6glFkpW2Ip4AmurJGb 4=;
X-IronPort-AV: E=McAfee;i="5300,2777,5777"; a="25670561"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Oct 2009 09:30:11 -0700
Received: from msgtransport01.qualcomm.com (msgtransport01.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n9KGUAL0018922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 20 Oct 2009 09:30:10 -0700
Received: from nasanexhub04.na.qualcomm.com (nasanexhub04.qualcomm.com [129.46.134.222]) by msgtransport01.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n9KGU99n014189 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Oct 2009 09:30:09 -0700
Received: from nalasexhub02.na.qualcomm.com (10.47.130.89) by nasanexhub04.na.qualcomm.com (129.46.134.222) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 20 Oct 2009 09:30:09 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhub02.na.qualcomm.com ([10.47.130.89]) with mapi; Tue, 20 Oct 2009 09:30:08 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Date: Tue, 20 Oct 2009 09:30:08 -0700
Thread-Topic: [btns] Minor connection-latch problem in AUTH48
Thread-Index: AcpRDDZrzgFh5vQsTaCUrmTD0p/xMQAlhE9Q
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C648C9FA4@NALASEXMB04.na.qualcomm.com>
References: <20091015221608.GC907@Sun.COM> <BF345F63074F8040B58C00A186FCA57F1C2A67DF98@NALASEXMB04.na.qualcomm.com> <20091016203953.GQ892@Sun.COM> <BF345F63074F8040B58C00A186FCA57F1C2A67DFC1@NALASEXMB04.na.qualcomm.com> <20091016211652.GV892@Sun.COM> <BF345F63074F8040B58C00A186FCA57F1C2A67DFD7@NALASEXMB04.na.qualcomm.com> <20091019164014.GF892@Sun.COM> <BF345F63074F8040B58C00A186FCA57F1C648C9F4D@NALASEXMB04.na.qualcomm.com> <20091019221410.GN892@Sun.COM>
In-Reply-To: <20091019221410.GN892@Sun.COM>
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: "btns@ietf.org" <btns@ietf.org>
Subject: Re: [btns] Minor connection-latch problem in AUTH48
X-BeenThere: btns@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Better-Than-Nothing-Security Working Group discussion list <btns.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/btns>, <mailto:btns-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/btns>
List-Post: <mailto:btns@ietf.org>
List-Help: <mailto:btns-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/btns>, <mailto:btns-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2009 16:30:19 -0000

> -----Original Message-----
> From: Nicolas Williams [mailto:Nicolas.Williams@sun.com]
> Sent: Monday, October 19, 2009 3:14 PM
> To: Laganier, Julien
> Cc: btns@ietf.org
> Subject: Re: [btns] Minor connection-latch problem in AUTH48
> 
> On Mon, Oct 19, 2009 at 02:59:31PM -0700, Laganier, Julien wrote:
> > Nicolas Williams wrote:
> > > OK, this way the changes are much smaller and localized -- only the
> > > description of CREATE_CONNECTION_LATCH() changes, to:
> >
> > Hmm. Better, but somehow I'd rather take the 2 last paragraphs about
> > the "larval" state completely out, because right now it IMHO says
> > either too much or too less. It's not precise enough to tell an
> > implementer who hasn't followed that discussion what to do yet it
> > outlines at alternative to the key manager establishing the SA
> > straight and the ULP latching the connection on the SA.
> 
> I really want to leave the MAY in, as well as the note that that
> implies
> a state that we're not describing.  I'm willing to remove the
> parenthetical note, since that's really informative of something that
> implementors, who chose to implement that MAY, would figure out on
> their
> own anyways.
> 
> > If you want to keep the "larval" text in, I've did some wordsmithing
> > below that you might want to consider:
> 
> I can't tell what's particularly different in your text.  You did split
> a sentence, but I think I'll just re-write that sentence this way:

I added some words saying that the larval state is transient, and the connection is latched is latched pending establishement of the SA, see below:
 
> "Such an implementation may require an additional state in the
> connection latch state machine: a "LARVAL" state, so to speak, that is
> not described herein."
> 
> I think the colon helps more than either the comma I had written
> originally, or than a period.

So how about:

Such an implementation may require an additional transient state in the connection latch state machine: a "LARVAL" state, so to speak, to which the connection is latched pending
establishment of the SA. Such a "LARVAL" state is not described further herein.

--julien