Re: [OAUTH-WG] TLS version requirements in OAuth 2.0 base

Barry Leiba <barryleiba@computer.org> Fri, 20 January 2012 20:44 UTC

Return-Path: <barryleiba@gmail.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 7873B21F86FA for <oauth@ietfa.amsl.com>; Fri, 20 Jan 2012 12:44:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.855
X-Spam-Level:
X-Spam-Status: No, score=-102.855 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 j-GzTMqIvOPw for <oauth@ietfa.amsl.com>; Fri, 20 Jan 2012 12:44:20 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8D91D21F86F9 for <oauth@ietf.org>; Fri, 20 Jan 2012 12:44:20 -0800 (PST)
Received: by obbwc12 with SMTP id wc12so1415851obb.31 for <oauth@ietf.org>; Fri, 20 Jan 2012 12:44:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.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; bh=9JcP84/5OL9cQIWLjrvy23WD1GOcW1sDfNQdjIhgOjU=; b=P4ft7jI3c11YHXmGlgidc6ue3bvpYcXyW4CQ5+gAL0bNNlxAwgZ9b3AJWN4ZuJbfLj rrAQ0Nx7i0k6XKe66eopgS+1Tk2DFbDDv8BrURPFcZxcnR09SnCNGsUC7epc58QeddW8 fS+Mecs/CwXlqz9VpDWzO7Rc8c3zFHsMbptaQ=
MIME-Version: 1.0
Received: by 10.182.41.5 with SMTP id b5mr25062050obl.79.1327092250412; Fri, 20 Jan 2012 12:44:10 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.60.55.137 with HTTP; Fri, 20 Jan 2012 12:44:10 -0800 (PST)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723453AAB964D3@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <CALaySJJcPPSU5PAtk9GNL9iFBXj1HfWjkN32GeHsV_Ry2t+o=A@mail.gmail.com> <CAC4RtVABZSo2VXZ4pTGw9P+fdRrUWQajXm+SngQw6Ng9qK+NNQ@mail.gmail.com> <CAC4RtVBHwtuo6+-mZLkH-1VNs0DM2WXrVGGjY08AR05UocKM_Q@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723453AAB964D3@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Fri, 20 Jan 2012 15:44:10 -0500
X-Google-Sender-Auth: RTY5lLvwg_VmIUps9yXSTr1L9Js
Message-ID: <CALaySJKS+bnpS=EuaO3aV2ip1v7XifStsj78c89U-tC2Um9PiQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Eran Hammer <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: oauth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] TLS version requirements in OAuth 2.0 base
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: Fri, 20 Jan 2012 20:44:21 -0000

> Added to section 1:
>
>   TLS Version
>
>          Whenever TLS is required by this specification, the appropriate version (or versions) of
>          TLS will vary over time, based on the widespread deployment and known security
>          vulnerabilities. At the time of this writing, TLS version 1.2 <xref target='RFC5246' />
>          is the most recent version, but has a very limited deployment base and might not be
>          readily available for implementation. TLS version 1.0 <xref target='RFC2246' /> is the
>          most widely deployed version, and will provide the broadest interoperability.
>
>          Implementations MAY also support additional transport-layer mechanisms that meet their
>          security requirements.
>
> And referenced this section when TLS requirements were previously defined.

That seems like a very sensible way to organize it; thanks.

Barry