IETF Logo Mail Archive

Re: [OAUTH-WG] TLS 1.2

"Lu, Hui-Lan (Huilan)" <huilan.lu@alcatel-lucent.com> Thu, 18 August 2011 20:48 UTC

Return-Path: <huilan.lu@alcatel-lucent.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 2E06921F8B5B for <oauth@ietfa.amsl.com>; Thu, 18 Aug 2011 13:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.561
X-Spam-Level:
X-Spam-Status: No, score=-5.561 tagged_above=-999 required=5 tests=[AWL=-1.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 u3crtTde235J for <oauth@ietfa.amsl.com>; Thu, 18 Aug 2011 13:48:32 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 8551B21F8B53 for <oauth@ietf.org>; Thu, 18 Aug 2011 13:48:32 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p7IKnMl8001918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Aug 2011 15:49:22 -0500 (CDT)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p7IKnMJX032090 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 18 Aug 2011 15:49:22 -0500
Received: from USNAVSXCHMBSB3.ndc.alcatel-lucent.com ([135.3.39.135]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Thu, 18 Aug 2011 15:49:22 -0500
From: "Lu, Hui-Lan (Huilan)" <huilan.lu@alcatel-lucent.com>
To: 'Rob Richards' <rrichards@cdatazone.org>, Eran Hammer-Lahav <eran@hueniverse.com>
Date: Thu, 18 Aug 2011 15:49:22 -0500
Thread-Topic: [OAUTH-WG] TLS 1.2
Thread-Index: Acxd34CB0oEnV9g8ToOcDofXxwJRzgACMq2w
Message-ID: <0E96A74B7DFCF844A9BE2A0BBE2C425F058F244273@USNAVSXCHMBSB3.ndc.alcatel-lucent.com>
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> <90C41DD21FB7C64BB94121FBBC2E72345029DFAA9D@P3PW5EX1MB01.EX1.SECURESERVER.NET> <4E4D6BFF.8080102@cdatazone.org>
In-Reply-To: <4E4D6BFF.8080102@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
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 20:48:33 -0000

+1

Huilan


> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Rob
> Richards
> Sent: Thursday, August 18, 2011 3:46 PM
> To: Eran Hammer-Lahav
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG] TLS 1.2
> 
> On 8/18/11 2:31 PM, Eran Hammer-Lahav wrote:
> >> -----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
> >
> >
> 
> That works
> 
> Rob
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email