Re: [TLS] Last Call: RFC 2818 (HTTP Over TLS) to Proposed Standard

Peter Saint-Andre <stpeter@stpeter.im> Fri, 01 June 2012 20:43 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 998DD11E8097 for <tls@ietfa.amsl.com>; Fri, 1 Jun 2012 13:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level:
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, 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 ljEZfTB+IFkQ for <tls@ietfa.amsl.com>; Fri, 1 Jun 2012 13:43:51 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 2218011E808A for <tls@ietf.org>; Fri, 1 Jun 2012 13:43:51 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C463A40075; Fri, 1 Jun 2012 15:00:25 -0600 (MDT)
Message-ID: <4FC92985.2050809@stpeter.im>
Date: Fri, 01 Jun 2012 14:43:49 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Eric Rescorla <ekr@rtfm.com>
References: <20120601164205.25357.54620.idtracker@ietfa.amsl.com> <4FC8F1AF.2040409@stpeter.im> <CABcZeBN4rwJuL8_vvYfPZJyE_WU_+tmSzLf2njPeqx0Ewgx64g@mail.gmail.com> <op.we8nss1yqrq7tp@acorna.invalid.invalid> <CABcZeBMFAXeXBK1Cs5jnvbTmJms7NUqhrmJd4x2N2DxedQUk=A@mail.gmail.com>
In-Reply-To: <CABcZeBMFAXeXBK1Cs5jnvbTmJms7NUqhrmJd4x2N2DxedQUk=A@mail.gmail.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: tls@ietf.org
Subject: Re: [TLS] Last Call: RFC 2818 (HTTP Over TLS) to Proposed Standard
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
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/options/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: Fri, 01 Jun 2012 20:43:51 -0000

On 6/1/12 1:45 PM, Eric Rescorla wrote:
> On Fri, Jun 1, 2012 at 12:15 PM, Yngve N. Pettersen (Developer Opera
> Software ASA) <yngve@opera.com> wrote:
>
>> - Update sec. 3.1 to use RFC 6125 for the server identity.
> 
> I'm not sure I agree with this. 2818 is intended to document HTTPS client
> behavior. This may or may not be what we recommend for other protocols

I see two approaches:

1. Profile 6125 in 2818bis, as we've done for email and XMPP.

2. Define something 6125-ish (but shorter) in 2818bis.

> (and indeed, the terms under which 6125 was approved included that
> it not override 2818 for HTTPS).

Indeed.

Another topic it would be good to clarify (or affirm) in 2818bis is
wildcards.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/