Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer
Martin Rex <Martin.Rex@sap.com> Thu, 01 October 2009 19:06 UTC
Return-Path: <Martin.Rex@sap.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 C7CF728C1A2 for <tls@core3.amsl.com>; Thu, 1 Oct 2009 12:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.037
X-Spam-Level:
X-Spam-Status: No, score=-6.037 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 7evcYSODNma8 for <tls@core3.amsl.com>; Thu, 1 Oct 2009 12:06:44 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.171]) by core3.amsl.com (Postfix) with ESMTP id CDBF628C19A for <tls@ietf.org>; Thu, 1 Oct 2009 12:06:43 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id n91J85jh029972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Oct 2009 21:08:05 +0200 (MEST)
From: Martin Rex <Martin.Rex@sap.com>
Message-Id: <200910011908.n91J84gC018022@fs4113.wdf.sap.corp>
To: jsalowey@cisco.com
Date: Thu, 01 Oct 2009 21:08:04 +0200
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE508D3C853@xmb-sjc-225.amer.cisco.com> from "Joseph Salowey" at Oct 1, 9 09:17:02 am
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Scanner: Virus Scanner virwal08
X-SAP: out
Cc: simon@josefsson.org, tls@ietf.org
Subject: Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: martin.rex@sap.com
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, 01 Oct 2009 19:06:44 -0000
Joseph Salowey wrote: > > For option 2 I would prefer text that explains the SHOULD, maybe > something like: > > "Since it is possible for a client to present a different server_name in > the application protocol, application server implementations that rely > upon these names being the same MUST check to make sure the client did > not present a different name in the application protocol." OK. +1 -Martin
- Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (… Blumenthal, Uri
- Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (… Blumenthal, Uri
- Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (… Martin Rex
- Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (… Simon Josefsson
- Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (… Joseph Salowey (jsalowey)
- Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (… Peter Saint-Andre
- Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (… Simon Josefsson
- Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (… Blumenthal, Uri
- Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (… Martin Rex