IETF Logo Mail Archive

[rtcweb] DTLS version

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Mon, 30 June 2014 23:44 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7FAA1A0402 for <rtcweb@ietfa.amsl.com>; Mon, 30 Jun 2014 16:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.802
X-Spam-Level:
X-Spam-Status: No, score=-0.802 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fgh8holILkTB for <rtcweb@ietfa.amsl.com>; Mon, 30 Jun 2014 16:44:45 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFFC01B27AC for <rtcweb@ietf.org>; Mon, 30 Jun 2014 16:44:45 -0700 (PDT)
Received: from [192.168.1.181] (p508F0C46.dip0.t-ipconnect.de [80.143.12.70]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 5F50E1C0B4026 for <rtcweb@ietf.org>; Tue, 1 Jul 2014 01:44:43 +0200 (CEST)
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <A963F527-57EB-4617-9583-6C0D63DDE4BD@lurchi.franken.de>
Date: Tue, 01 Jul 2014 01:44:42 +0200
To: rtcweb@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/Us5fMHbDfo8b8uaMWHWIFiL8Jxg
Subject: [rtcweb] DTLS version
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 30 Jun 2014 23:44:48 -0000

Dear all,

based on a comment from EKR, I would like to bring up a question:
RTCWeb uses DTLS for deriving the keys for SRTP on the one hand and
for transporting SCTP on the other hand.
The SRTP related documents refer to DTLS version 1.0 as specified in
http://tools.ietf.org/html/rfc4347
The SCTP over DTLS document currently refers to DTLS version 1.2 as specified in
http://tools.ietf.org/html/rfc6347

I think we need to use a single version of DTLS for RTCWeb. RFC 4347 is obsoleted
by RFC 6347. Wouldn't that imply that it makes sense to use DTLS 1.2 in all documents?

Best regards
Michael

v2.23.0 | Report a Bug | By Email