Re: [rtcweb] DTLS version for RTCweb

Tim Panton <tim@phonefromhere.com> Fri, 10 May 2013 09:08 UTC

Return-Path: <tim@phonefromhere.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF51921F88EA for <rtcweb@ietfa.amsl.com>; Fri, 10 May 2013 02:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 FGhYvKPkysVO for <rtcweb@ietfa.amsl.com>; Fri, 10 May 2013 02:08:52 -0700 (PDT)
Received: from smtp003.apm-internet.net (smtp003.apm-internet.net [85.119.248.52]) by ietfa.amsl.com (Postfix) with ESMTP id 4B94E21F884F for <rtcweb@ietf.org>; Fri, 10 May 2013 02:08:51 -0700 (PDT)
Received: (qmail 2897 invoked from network); 10 May 2013 09:08:49 -0000
X-AV-Scan: clean
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp003.apm-internet.net with SMTP; 10 May 2013 09:08:49 -0000
Received: from zimbra003.verygoodemail.com (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id E46FA18A0663; Fri, 10 May 2013 10:08:49 +0100 (BST)
Received: from [192.67.4.33] (unknown [192.67.4.33]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id CE47C18A062D; Fri, 10 May 2013 10:08:49 +0100 (BST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Tim Panton <tim@phonefromhere.com>
In-Reply-To: <518C1921.1010606@acm.org>
Date: Fri, 10 May 2013 10:08:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CEDD7FB9-8183-41D7-B771-DF38A747D4A0@phonefromhere.com>
References: <518C1921.1010606@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
X-Mailer: Apple Mail (2.1283)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] DTLS version for RTCweb
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 09:09:01 -0000

On 9 May 2013, at 22:46, Marc Petit-Huguenin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> I read the various security drafts and it looks like they all reference DTLS
> 1.0 (RFC 4347), but RFC 4347 was obsoleted by RFC 6247.  So will the
> references being updated to use DTLS 1.2 as the base version, or will DTLS 1.0
> stay as the base version, with possibility of negotiation to 1.2 and higher?
I think we should move to 1.2 - There are specific cases where 1.0 doesn't exactly do what we
want. 

e.g. I think for a server to ask for a client cert, technically in 1.0 you are supposed to list the CA's
you are interested in and you'll only receive certs from those CAs. In 1.2 you can leave this
empty and get a list of all certs (effectively a CA wildcard). 

T.