[rtcweb] Question about support for RFC 6520 DTLS heartbeat

Bernard Aboba <bernard.aboba@gmail.com> Wed, 14 January 2015 00:58 UTC

Return-Path: <bernard.aboba@gmail.com>
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 104D81ACE0E for <rtcweb@ietfa.amsl.com>; Tue, 13 Jan 2015 16:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_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 Rb0cba_lYkup for <rtcweb@ietfa.amsl.com>; Tue, 13 Jan 2015 16:58:05 -0800 (PST)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B78F1ACD46 for <rtcweb@ietf.org>; Tue, 13 Jan 2015 16:58:05 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id h11so25033193wiw.1 for <rtcweb@ietf.org>; Tue, 13 Jan 2015 16:58:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=OlYRnPjtk9nPyBfL1waQnQVGSGEKhfjubHGplQrWJaM=; b=adjSZp5oChd4UtvdFBYW7NqDV6zI/Ag87r2SQzdhRh3fbQgrQ4vtBeGk+bZ7ad6WmL Q8RiPkiWtCpLFoU+ymkp4CJQJTTlUUgeAgC0rld1lEvX5vhXEsj+0IiEOcsHC4G3/e7h xDKz6gLd58cypuvXaoEvpbgV9LwLtgd1vAcmusSn1VCy40zJ7PVobibo/6T2QDZR7WJx vpRkz69qrYiA+6Sr1dalUTA0TprtiBvUZNugTONfhOXndBcApJ3xSh9zJfei2GntIcVO +EtG5F/HBhOs0sgG72ebD6WxJwqD9fulzgw3HUC6kEyl6Jc6hOEsBw3fpAWV8bp88aV6 ayKQ==
X-Received: by 10.181.12.17 with SMTP id em17mr45432801wid.45.1421197084085; Tue, 13 Jan 2015 16:58:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.91.65 with HTTP; Tue, 13 Jan 2015 16:57:43 -0800 (PST)
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 13 Jan 2015 16:57:43 -0800
Message-ID: <CAOW+2dsaAOmOS=VZe8VTRoSSjN0TAQzY2kXaOqHUCAf9jaA5Mw@mail.gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary=f46d043893c35a527f050c923ba3
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/zHxrHhpp5B2D6JPs0tZXmqN4uLY>
Subject: [rtcweb] Question about support for RFC 6520 DTLS heartbeat
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: Wed, 14 Jan 2015 00:58:10 -0000

Looking through IETF RTCWEB WG drafts (
https://tools.ietf.org/id/draft-ietf-rtcweb) and dependencies, "DTLS
Heartbeat" RFC 6520 appears to be referenced only in
draft-ietf-tsvwg-sctp-dtls-encaps Section 5, in the context of PMTU
discovery:

   If path MTU discovery is performed by the DTLS layer, the method
   described in [RFC4821 <https://tools.ietf.org/html/rfc4821>] MUST
be used.  For probe packets, the
   extension defined in [RFC6520
<https://tools.ietf.org/html/rfc6520>] MUST be used.


Is it correct to conclude that existing implementations do not use the DTLS
heartbeat other than for PMTU discovery?