Re: [OAUTH-WG] TLS 1.2

Eran Hammer-Lahav <eran@hueniverse.com> Thu, 18 August 2011 18:32 UTC

Return-Path: <eran@hueniverse.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E5E321F86AC for <oauth@ietfa.amsl.com>; Thu, 18 Aug 2011 11:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.521
X-Spam-Level:
X-Spam-Status: No, score=-1.521 tagged_above=-999 required=5 tests=[AWL=-0.999, BAYES_00=-2.599, SUBJ_ALL_CAPS=2.077]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBP5LRHCXbS4 for <oauth@ietfa.amsl.com>; Thu, 18 Aug 2011 11:32:07 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by ietfa.amsl.com (Postfix) with SMTP id 5BAE621F86AA for <oauth@ietf.org>; Thu, 18 Aug 2011 11:32:07 -0700 (PDT)
Received: (qmail 15037 invoked from network); 18 Aug 2011 18:33:02 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.46) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 18 Aug 2011 18:33:01 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT004.EX1.SECURESERVER.NET ([72.167.180.134]) with mapi; Thu, 18 Aug 2011 11:33:01 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Rob Richards <rrichards@cdatazone.org>, Peter Saint-Andre <stpeter@stpeter.im>
Date: Thu, 18 Aug 2011 11:31:44 -0700
Thread-Topic: [OAUTH-WG] TLS 1.2
Thread-Index: AcxcU+p2zNZTfLk8R/uNcaumqDWtvgBgJs0A
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72345029DFAA9D@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <4E458571.1070500@cdatazone.org> <4E4AC6BA.2090007@cdatazone.org> <1313524116.13419.81.camel@ground> <90C41DD21FB7C64BB94121FBBC2E7234502498D1B0@P3PW5EX1MB01.EX1.SECURESERVER.NET> <4E4ACD53.2010404@stpeter.im> <4E4AD454.9040302@cdatazone.org>
In-Reply-To: <4E4AD454.9040302@cdatazone.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] TLS 1.2
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 18:32:08 -0000

> -----Original Message-----
> From: Rob Richards [mailto:rrichards@cdatazone.org]
> Sent: Tuesday, August 16, 2011 1:34 PM

> The authorization server SHOULD support TLS 1.2 as defined in [RFC5246] but
> at a minimum MUST support TLS 1.0 as defined in [RFC2246], and MAY
> support additional transport-layer mechanisms meeting its security
> requirements.

How about:

The authorization server MUST support TLS 1.0 ([RFC2246]), SHOULD support TLS 1.2 ([RFC5246]) and its future replacements, and MAY support additional transport-layer mechanisms meeting its security requirements.

EHL