Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 12 March 2015 10:13 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 283C51A8F3A for <rtcweb@ietfa.amsl.com>; Thu, 12 Mar 2015 03:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 HU6Rs-mmoZTE for <rtcweb@ietfa.amsl.com>; Thu, 12 Mar 2015 03:13:03 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E12EB1A90DC for <rtcweb@ietf.org>; Thu, 12 Mar 2015 03:13:02 -0700 (PDT)
X-AuditID: c1b4fb2d-f79aa6d00000359d-b9-550166aa9ddf
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id F9.75.13725.AA661055; Thu, 12 Mar 2015 11:12:59 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.214]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0210.002; Thu, 12 Mar 2015 11:12:58 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Justin Uberti <juberti@google.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples
Thread-Index: AQHQVqbHfYSbCv5RRE+VguSZdJaU4Z0MmygAgAACNQCAAB9EuP//8M8AgAASNNj//+/xAIAADFaAgAAlg8SAABtygIAAeWFLgAAf7wCAAAYfgIAAVgeAgAZK9ICAAInMAIACfsqQ///+kYAAAkFGAP//9aSA///silCAABmMAIAAEUGA//63n9A=
Date: Thu, 12 Mar 2015 10:12:57 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D737A76@ESESSMB209.ericsson.se>
References: <54F74B02.1070902@jive.com> <CAD5OKxs8JYG3-Vvndi59ZrdPE7UTj22ozD4tcWTHgzWrHv=q7Q@mail.gmail.com> <54F756B2.60408@jive.com> <7594FB04B1934943A5C02806D1A2204B1D726AD8@ESESSMB209.ericsson.se> <CAD5OKxu7py3HbrFjxTDZS5ECFzx7vd=wpjve-gT6gWwksjEu+g@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D726B71@ESESSMB209.ericsson.se> <CABcZeBO1O6sA8MqvWkCDu3RPLz5-P2G65Us28i0baOavDnRT7Q@mail.gmail.com> <CAD5OKxuWCdgMR5Kxjv9BSwZ3Jm9kGXx9Pi-9FrfsnuQZ_91jAA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D726DC1@ESESSMB209.ericsson.se> <CALiegfkipJhsy7-40+=d9xMUf4RJGdn3_fABL3NN2KuFNvS2BA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D727570@ESESSMB209.ericsson.se> <CALiegfmfvz3NWSjcovGBytiOTbR6kFfyh0vx5cXoMJtytfGzRA@mail.gmail.com> <CAD5OKxsu3D0xHY-zYbDu1hyH_+4=3mWDvW2i98WCVZ+29BpKCw@mail.gmail.com> <CA5E97EE-99F8-44D8-B05B-C9EFDED1A9BB@vidyo.com> <2F467A7E-7A6C-4B1B-985A-0D9C089BE973@cisco.com> <CAOJ7v-1TjZOZ5G31vy_Gt73ADGLRay1RHVeMi=H6Q4=N1b6HLA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D7367A0@ESESSMB209.ericsson.se> <CALiegfmyp=v6thk4eLz7nL1BHh2Qj7jmC84tdG7ufg8HPXsVKA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D7369C9@ESESSMB209.ericsson.se> <CAD5OKxtCswToNzoZnnqJ5M66mjNjKJoA++WYNqN5155n+CWXsA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D736AC0@ESESSMB209.ericsson.se> <CAD5OKxs1grSqAG32mf__wtsjpo68jZmKonbd+EsJmYNsDHUbFQ@mail.gmail.com> <CAOJ7v-3YypG1s9KXOCA+Fo58SuVuUk5-thcSc0k3N2j=4ZmJoA@mail.gmail.com>
In-Reply-To: <CAOJ7v-3YypG1s9KXOCA+Fo58SuVuUk5-thcSc0k3N2j=4ZmJoA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGfG3Rnd1GmOowcpzvBYdk9ks9i8+z2yx daqQxYwLU5kt1v5rZ3dg9ZjyeyOrx4JNpR5Llvxk8rg1pcCj7dkd9gDWKC6blNSczLLUIn27 BK6M5e9OsRTM4KvYP/UOYwPjC94uRk4OCQETiTOvLjFB2GISF+6tZ+ti5OIQEjjCKLHh8jxm CGcJo8Tpr5+AMhwcbAIWEt3/tEEaRAQ8JeaseQAWZhYolnj6wQYkLCxgLPFt5hNGiBITiY3P nzOBjBEROMYosWXtaaCZ7BwsAqoSD1JASngFfCWuPP3GCmILCdzklnjUCTaGUyBQYtnvRjYQ mxHotO+n1oCdySwgLnHryXyokwUkluw5zwxhi0q8fPyPFcJWlNh5tp0Z4jJNifW79CFaFSWm dD9kh1grKHFy5hOWCYxis5BMnYXQMQtJxywkHQsYWVYxihanFhfnphsZ66UWZSYXF+fn6eWl lmxiBMbawS2/dXcwrn7teIhRgINRiYfXkJExVIg1say4MvcQozQHi5I4r53xoRAhgfTEktTs 1NSC1KL4otKc1OJDjEwcnFINjPzf31/nXuT541IUz0E5D+WnDnayqR9DV1iar9rAJf/zcuvV ut4ym+3vyzW4uN/LpczQbzrg9KriD+NS1Va+PYJfNhT/3+l1kfOr5YPOI7GSTHOPMRdPq/K1 +tebfmXJLu5P90Plz+xvyi1hLd+8T8h74Qy5y/ITfv/aKOjecIrx+A5Px+R+FyWW4oxEQy3m ouJEAIfyH3KWAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/UZw2rK6GqtZVLiSbJ5aUM6BQYn0>
Cc: Cullen Jennings <fluffy@cisco.com>, Jonathan Lennox <jonathan@vidyo.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples
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, 12 Mar 2015 10:13:05 -0000

Hi,

>>>> New things can be defined in the future. When they do, they should treat ICE a virtual communication channel that
>>>> provides unreliable packet transport with no order guarantees which can span multiple 5-tuples.
>>>
>>> Then the scope of what we discuss now should not be "whatever protocol" - it should be the specific protocols we are discussing.
>>
>> I think ICE-bis should define protocol requirements for the protocols that can run on top of ICE, which includes:
>> 1. Ability to run over unreliable packet based transport with no order guarantees
>> 2. Ability to demux with STUN packets
>> 3. Not make any assumption about IP addresses, ports, or other transport level protocols attributes such as TOS. 
>
> I think these are good criteria. Note that TCP would meet these criteria, and I see no problem running TCP atop ICE (we used to do this in an old version of our data channel code).

I don't think a TCP connection can span over multiple 5-tuples - each TCP connection will be bound to one 5-tuple.

Perhaps the protocol running on top of TCP can switch between different TCP connections, though. For example, would it be possible to span a TLS connection over multiple TCP connections?

> HTTP, on the other hand, would not meet criterion #1.

Agree.

Regards,

Christer