Re: [TLS] [sasl] [CHANNEL-BINDING] Updates to draft-altman-tls-channel-bindings (PLEASE REVIEW)

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 18 March 2010 19:16 UTC

Return-Path: <lunohod.baikonur@googlemail.com>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86B283A6974; Thu, 18 Mar 2010 12:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.847
X-Spam-Level:
X-Spam-Status: No, score=-0.847 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, FM_FORGED_GMAIL=0.622]
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 5vkTDAk8xauD; Thu, 18 Mar 2010 12:16:05 -0700 (PDT)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id 804AA3A6AF0; Thu, 18 Mar 2010 12:16:01 -0700 (PDT)
Received: by fxm5 with SMTP id 5so49282fxm.29 for <multiple recipients>; Thu, 18 Mar 2010 12:16:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=wMlXHm8kOizxbDNS9rmVM1U8f3K+RE+7rCmi0n90BsY=; b=lX1Gy3/LarT1CG6dDhuNMrnirV0nX1zS4Eu/02fFUbqNYJvF6QTN0kmZgdFzyK5aQp AXyshnfHoq9nKop8ptIhmfl8oNNNJPHxZIvWDko2p03E7Wu9CvjGtvB+6Gt2P++xc3I7 za4iIRmkZWmlMBLbJNxrkvAqXoQMISWN99n8I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=ispk4CsUed8tQ5V1Vj3FDtRA/7Z1yFX7z++S7A643lW4zG88/Vf7Se9fHWOQz7KO2j SFRrMYHtjwYfXjgSnWe7Ql8A03Y6oLTCyMTwweLAADOqskpddpwf/EpnCGjdAaRTDZWy aGdkGorgwbLtiHOV/VmHJGsAQa5uZkMkDIAKw=
MIME-Version: 1.0
Sender: lunohod.baikonur@googlemail.com
Received: by 10.103.48.21 with SMTP id a21mr2114727muk.98.1268939767376; Thu, 18 Mar 2010 12:16:07 -0700 (PDT)
In-Reply-To: <877hp98xjn.fsf@mocca.josefsson.org>
References: <20100317231522.GA18167@Sun.COM> <808FD6E27AD4884E94820BC333B2DB775848524D7A@NOK-EUMSG-01.mgdnok.nokia.com> <2462.1268919913.457533@puncture> <877hp98xjn.fsf@mocca.josefsson.org>
Date: Thu, 18 Mar 2010 19:16:07 +0000
X-Google-Sender-Auth: 9b2fb7bae7b97ab8
Message-ID: <29d3c4cb1003181216q7b4d28f5iaa27f650d8af574@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Simon Josefsson <simon@josefsson.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 18 Mar 2010 13:40:22 -0700
Cc: "channel-binding@ietf.org" <channel-binding@ietf.org>, "tls@ietf.org" <tls@ietf.org>, SASL Working Group <sasl@ietf.org>, Dave Cridland <dave@cridland.net>
Subject: Re: [TLS] [sasl] [CHANNEL-BINDING] Updates to draft-altman-tls-channel-bindings (PLEASE REVIEW)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Mar 2010 19:16:06 -0000

On Thu, Mar 18, 2010 at 3:22 PM, Simon Josefsson <simon@josefsson.org> wrote:

 [...]

> Changing the IANA specification for tls-unique long after it has been
> registered and published seems bad to me.  Bad enough to make me think
> that it is a mistake for GS2/SCRAM to reference the IANA specification
> normatively -- if the IANA registry is not immutable, interop is not
> possible.
>
> There is always the option of making GS2/SCRAM reference 'tls-unique2'
> and specify that clearly and stable once and for all.  Then we can let
> 'tls-unique' be the interop mess that it appears to be right now.

+1.