Re: [TLS] Text for draft-ietf-tls-rfc4366-bis

Michael D'Errico <mike-list@pobox.com> Thu, 20 May 2010 15:36 UTC

Return-Path: <mike-list@pobox.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 45BAF3A6C84 for <tls@core3.amsl.com>; Thu, 20 May 2010 08:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.691
X-Spam-Level:
X-Spam-Status: No, score=-0.691 tagged_above=-999 required=5 tests=[AWL=-0.692, BAYES_50=0.001]
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 44iqoEIVmd9c for <tls@core3.amsl.com>; Thu, 20 May 2010 08:36:42 -0700 (PDT)
Received: from sasl.smtp.pobox.com (a-pb-sasl-quonix.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id 59FA23A6C4F for <tls@ietf.org>; Thu, 20 May 2010 08:36:41 -0700 (PDT)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id 5D803B5AC7; Thu, 20 May 2010 11:36:34 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=tuo8RacPUhpt 7/JCFUuwII1exxs=; b=QP+q69J0qyo5pYqauaYFfHpWW1vA6zSO1aMD8e4pL2qY ehWEORvfWOmV+x++EuFWiZQ4oXkkNOUsLRg1CJ8iHDcdXxmFlPzdxKJigmlyehio qVwgDWL4A1xQJnv7kN2j0L2/5wFnlpDlJRiKeQFy/skFbDo5ttMsg85lCPwpwUU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sasl; b=itrKHS ZSUv8ezyS0fA6vU5c31zTho0nJT/BhNhJ0GvUOGetovVBhi/gMTSM2BjnoyKnC/b P/Os9JB0BGX87/j/BRWPK3lxZwErbyjQVYsUNGA7yQ6A/b0NP+vZmV+sV/IN85xX bqEqlPRn/7Sfqw62YMBdwfBZccOWiEyHcPflA=
Received: from a-pb-sasl-quonix. (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id 3A39FB5AC5; Thu, 20 May 2010 11:36:32 -0400 (EDT)
Received: from administrators-macbook-pro.local (unknown [24.234.114.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTPSA id EA851B5AC0; Thu, 20 May 2010 11:36:25 -0400 (EDT)
Message-ID: <4BF556F8.60206@pobox.com>
Date: Thu, 20 May 2010 08:36:24 -0700
From: Michael D'Errico <mike-list@pobox.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE50A67D09A@xmb-sjc-225.amer.cisco.com> <003701caf817$b4754140$4001a8c0@gateway.2wire.net> <AC1CFD94F59A264488DC2BEC3E890DE50A67D0FA@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE50A67D0FA@xmb-sjc-225.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 774688A4-6425-11DF-BFC1-D033EE7EF46B-38729857!a-pb-sasl-quonix.pobox.com
Cc: tls@ietf.org
Subject: Re: [TLS] Text for draft-ietf-tls-rfc4366-bis
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, 20 May 2010 15:36:43 -0000

Joe - the new text looks good to me.

Mike



Joseph Salowey (jsalowey) wrote:
> Good suggestion, thanks for the text, here is the text reworked:
> 
> "When the server is deciding whether or not to accept a request to
> resume
>  a session, the contents of a server_name extension may be used in 
>  the lookup of the session in the session cache.  The client SHOULD 
>  include the same server_name extension in session resumption 
>  request as it did in the full handshake that established the
>  session.  If the server_name extension contains a different name, 
>  the server MUST NOT accept the request to resume the session. 
>  Instead, it proceeds with a full handshake to establish a new 
>  Session.  The client MAY omit the extension, in which case, if 
>  the server chooses to resume the session, it must use the server 
>  name cached from the original full handshake. When resuming a 
>  session, the server MUST NOT include a server_name extension in
>  the server hello."
> 
> Changes to section 1.1
> 
> "Note also that all the extensions defined in this document are
>  relevant only when a session is initiated.  When a client includes
>  one or more of the defined extension types in an extended client
>  hello while requesting session resumption:
> 
> 	-  The server name indication extension MAY be used by the 
>          server when deciding whether or not to resume a session 
>          as described in section 3.
> 
>       -  If the resumption request is denied, the use of the extensions
>          is negotiated as normal.
> 
>       -  If, on the other hand, the older session is resumed, then the
>          server MUST ignore the extensions and send a server hello
>          containing none of the extension types.  In this case, the
>          functionality of these extensions negotiated during the
>          original session initiation is applied to the resumed session."
>