Re: [rtcweb] Network times . was SDP Security Descriptions (RFC 4568) and RTCWeb

Tim Panton <tim@phonefromhere.com> Wed, 01 May 2013 11:41 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 42CDD21F8606 for <rtcweb@ietfa.amsl.com>; Wed, 1 May 2013 04:41:54 -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=[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 pNb0PPyqSbgf for <rtcweb@ietfa.amsl.com>; Wed, 1 May 2013 04:41:46 -0700 (PDT)
Received: from smtp003.apm-internet.net (smtp003.apm-internet.net [85.119.248.52]) by ietfa.amsl.com (Postfix) with ESMTP id CC24C21F84F9 for <rtcweb@ietf.org>; Wed, 1 May 2013 04:41:45 -0700 (PDT)
Received: (qmail 64666 invoked from network); 1 May 2013 11:41:44 -0000
X-AV-Scan: clean
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp003.apm-internet.net with SMTP; 1 May 2013 11:41:44 -0000
Received: from zimbra003.verygoodemail.com (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id BF63118A0520; Wed, 1 May 2013 12:41:44 +0100 (BST)
Received: from [192.67.4.33] (unknown [192.67.4.33]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id 9A6D118A0313; Wed, 1 May 2013 12:41:44 +0100 (BST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="iso-8859-1"
From: Tim Panton <tim@phonefromhere.com>
In-Reply-To: <02d001ce465c$bf00f690$3d02e3b0$@stahl@intertex.se>
Date: Wed, 01 May 2013 12:41:47 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E831D6E7-35D6-4289-871A-6620AC7EF866@phonefromhere.com>
References: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca> <20130425202238.74EF321F96A5@ietfa.amsl.com> <AE1A6B5FD507DC4FB3C5166F3A05A48416281FDB@tk5ex14mbxc272.redmond.corp.microsoft.com> <03FBA798AC24E3498B74F47FD082A92F3BB8FAF7@US70UWXCHMBA04.zam.alcatel-lucent.com> <9F33F40F6F2CD847824537F3C4E37DDF0E6C04AF@MCHP04MSX.global-ad.net> <CAErhfrx6xi7rNmc6CZc5iyKiYv+oZbi3sBa5QywB7dUKtms2Aw@mail.gmail.com> <C643F355C8D33C48B983F1C1EA702A450B49EA@ESESSMB301.ericsson.se> <4AA3A95D6033ED488F8AE4E45F47448742B13620@WABOTH9MSGUSR8B.ITServices.sbc.com> <CALiegfmpZZigigQtaadsXup6VfWgJAF8--TJpbUwSJMmar7fRA@mail.gmail.com> <CAD5OKxv2d2DemnjHQdB8XU8NKfK-Uu913DLPq9JUT4z9kvFfTQ@mail.gmail.com> <829F9A35-5F23-4A0F-9831-80478F70965E@phonefromhere.com> <517E2F6A.30905@alvestrand.no> <C5E08FE080ACFD4DAE31E4BDBF944EB1134B0090@xmb-aln-x02.cisco.com> <02d001ce465c$bf00f690$3d02e3b0$@stahl@intertex.se>
To: Karl Stahl <karl.stahl@intertex.se>
X-Mailer: Apple Mail (2.1283)
Cc: "'Cullen Jennings (fluffy)'" <fluffy@cisco.com>, rtcweb@ietf.org
Subject: Re: [rtcweb] Network times . was SDP Security Descriptions (RFC 4568) and 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: Wed, 01 May 2013 11:41:54 -0000

> 
> 2) Are packet drops during TLS-setup more likely over the UDP channel
> between browsers (as for DTLS) than over the signaling channel (for
> SRTP/DES). And are there more packets that safely need to arrive with DTLS
> setup?
> 
> 3) SRTP/DES setup rely on TCP retransmission if packets are lost (correct me
> if I am wrong), while DTLS must rely on some other higher level
> retransmission mechanisms. Are there longer timers involved then? I think
> this may be the real explanation for reports of slow DTLS setup, isn't it?
> 
> The only cure against dropped UPD packets is IP-level QoS, such as traffic
> shaping in firewalls/routers (but they need to be aware of traffic type) and
> diffserv or reservation over the transport network- but that is (currently)
> not enabled over the Internet, where all traffic is best effort class.


If we are seeing variability in DTLS setup times that don't seem to be justified 
by ping times it may be due to MTU issues.

DTLS has some rules (which I don't yet clearly understand) about how much
one can stuff into a packet based on an assumed/derived/calculated MTU. 
Guess too high and your packet will be dropped - forcing a retry with the data
broken over multiple packets. 

I suspect we may have a little learning to do in the implementations to select
an optimum MTU for the wild internet.

In these cases I'm sure packet captures set to the implementors would be most welcome.

Tim.