IETF Logo Mail Archive

Re: [rtcweb] Question about support for RFC 6520 DTLS heartbeat

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 15 January 2015 04:45 UTC

Return-Path: <christer.holmberg@ericsson.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 9304D1ACEE6 for <rtcweb@ietfa.amsl.com>; Wed, 14 Jan 2015 20:45:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 KpcRwdgE2kxz for <rtcweb@ietfa.amsl.com>; Wed, 14 Jan 2015 20:45:52 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F0141ACEE8 for <rtcweb@ietf.org>; Wed, 14 Jan 2015 20:45:51 -0800 (PST)
X-AuditID: c1b4fb30-f79106d000001184-6f-54b745fd6069
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 6C.07.04484.DF547B45; Thu, 15 Jan 2015 05:45:49 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.175]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0195.001; Thu, 15 Jan 2015 05:45:48 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [rtcweb] Question about support for RFC 6520 DTLS heartbeat
Thread-Index: AQHQL5UtWHqcwktsB0yKryagMbLO8Zy/PiwAgACNzgCAAC9fgIAAIwMAgAAHyQCAAHbzWA==
Date: Thu, 15 Jan 2015 04:45:47 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D63922A@ESESSMB209.ericsson.se>
References: <CAOW+2dsaAOmOS=VZe8VTRoSSjN0TAQzY2kXaOqHUCAf9jaA5Mw@mail.gmail.com> <DD273892-F62C-423C-A4FF-0BA8288A5454@lurchi.franken.de> <CABkgnnU9D7kq9R_QtLcyw58jiyYLrvLjK==X=ur1=btesdpVCw@mail.gmail.com> <1C5B610D-DA15-4DC6-82B3-E518748B1222@lurchi.franken.de> <54B6E9BC.2060203@alvestrand.no>, <7CEBA9FD-CCAE-473B-92FC-7E951317CEF4@lurchi.franken.de>
In-Reply-To: <7CEBA9FD-CCAE-473B-92FC-7E951317CEF4@lurchi.franken.de>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D63922AESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPLMWRmVeSWpSXmKPExsUyM+Jvje5f1+0hBo8WSlsc6+tis7jYtITR Yu2/dnYHZo8rE66weixZ8pPJY0PLDqYA5igum5TUnMyy1CJ9uwSujIbGHYwFk10q1h7vYW5g XGHdxcjJISFgItHz7CUbhC0mceHeeiCbi0NI4AijxJTpt5lAEkICSxgl1rxW6mLk4GATsJDo /qcNEhYRSJQ49vYPK4jNLKAucWfxOXYQW1jAQ+LdmtWsEDWeEi0Tp7FB2GESczYeZwMZwyKg KtF1yRUkzCvgKzFt3VJWiLUvmST+/DjKClLDKeAqsXASI0gNI9Bp30+tYYJYJS7R9GUlK8TJ AhJL9pxnhrBFJV4+/gfWyiyQLzGpTRVivKDEyZlPWCYwisxC0j0LoWoWkiqIEgOJL+9vQ9na EssWvmaGsPUlut+fZkIWX8DIvopRtDi1OCk33chIL7UoM7m4OD9PLy+1ZBMjMMYObvltsIPx 5XPHQ4wCHIxKPLwbbm8NEWJNLCuuzD3EKM3BoiTOm+ewIURIID2xJDU7NbUgtSi+qDQntfgQ IxMHp1QD48LW+/WlZRuqOU8+12eVTFOuClrE8ZDJ0Jf/1UkVzkteotvqXu49/9W2TbzziG9q NE/LzDd3bbZe4zpUXStQXRQ6rfj/l97YUr5VKx4uqH2YleUSsSamJsdVoUKsrfBW6SrrJZva N79+fOB1unHSxvqKL087Z/f93ePzpctb4PVbj7bIovtmSizFGYmGWsxFxYkA/7daoJICAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/jYTFYjslyEa2d7eRPkWYp8U8_ec>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [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: Thu, 15 Jan 2015 04:45:54 -0000

Hi,

I don't think the sctp-dtls-encaps draft shall contain data channel specific procedures.

I agree with Martin that the best place is the data channel draft.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Michael Tuexen<mailto:Michael.Tuexen@lurchi.franken.de>
Sent: ‎15/‎01/‎2015 00:40
To: Harald Alvestrand<mailto:harald@alvestrand.no>
Cc: rtcweb@ietf.org<mailto:rtcweb@ietf.org>
Subject: Re: [rtcweb] Question about support for RFC 6520 DTLS heartbeat

On 14 Jan 2015, at 23:12, Harald Alvestrand <harald@alvestrand.no> wrote:
>
> Den 14. jan. 2015 21:06, skrev Michael Tuexen:
>> On 14 Jan 2015, at 18:17, Martin Thomson <martin.thomson@gmail.com> wrote:
>>>
>>> On 14 January 2015 at 00:49, Michael Tuexen
>>> <Michael.Tuexen@lurchi.franken.de> wrote:
>>>> * DTLS does the PMTUD using DTLS heartbeats
>>>> * SCTP does the PMTUD using SCTP HEARTBEAT and PADDING chunks
>>>>
>>>> My understanding is the RTCWeb uses the second option as described in
>>>> http://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-13#section-5
>>>
>>> SGTM.  That means we don't need to reference the DTLS heartbleed extension.
>> It is not referenced in the RTCWeb documents, only in
>> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-07
>> which allows both options.
>
> So which document should we put it in that we use the second option?
> -transport, or a post-last-call update of -datachannel?
Do we really need a change? We have in
https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-13#section-5
   Incoming ICMP or ICMPv6 messages can't be processed by the SCTP
   layer, since there is no way to identify the corresponding
   association.  Therefore SCTP MUST support performing Path MTU
   discovery without relying on ICMP or ICMPv6 as specified in [RFC4821]
   using probing messages specified in [RFC4820].  The initial Path MTU
   at the IP layer SHOULD NOT exceed 1200 bytes for IPv4 and 1280 for
   IPv6.

In the next revision of
https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-07#section-4
there will be the sentence:
   The path MTU discovery is performed by SCTP when SCTP over DTLS is
   used for data channels (see Section 4 of
   [I-D.ietf-rtcweb-data-channel]).

Best regards
Michael
>
>>
>> Best regards
>> Michael
>>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email