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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 11 March 2015 14:19 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 57E991ACDD3 for <rtcweb@ietfa.amsl.com>; Wed, 11 Mar 2015 07:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level:
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, 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 rnFkCwyBvEhP for <rtcweb@ietfa.amsl.com>; Wed, 11 Mar 2015 07:19:37 -0700 (PDT)
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 543B31ACDCC for <rtcweb@ietf.org>; Wed, 11 Mar 2015 07:19:37 -0700 (PDT)
X-AuditID: c1b4fb30-f79c86d000000fc0-5c-55004ef7fcd2
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id E8.C7.04032.7FE40055; Wed, 11 Mar 2015 15:19:35 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.214]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0210.002; Wed, 11 Mar 2015 15:19:35 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Iñaki Baz Castillo <ibc@aliax.net>, Roman Shpount <roman@telurix.com>
Thread-Topic: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples
Thread-Index: AQHQVqbHfYSbCv5RRE+VguSZdJaU4Z0MmygAgAACNQCAAB9EuP//8M8AgAASNNj//+/xAIAADFaAgAAlg8SAABtygIAAeWFLgAAf7wCAAAYfgIAAVgeAgAZK9ICAAInMAIACfsqQ///+kYAAAkFGAP//9aSAgAABLgD//+6+AA==
Date: Wed, 11 Mar 2015 14:19:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D736A70@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> <CALiegfmjqaV9oHe9RMFVGNs+jVN6rZaY6boY9iCwe8HExGtCSw@mail.gmail.com>
In-Reply-To: <CALiegfmjqaV9oHe9RMFVGNs+jVN6rZaY6boY9iCwe8HExGtCSw@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.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42KZGfG3Rve7H0OoQft8FYuOyWwW0/fZWOxf fJ7ZYsaFqcwWa/+1szuwepxreM/uMeX3RlaPJUt+MnncmlLg0fbsDnsAaxSXTUpqTmZZapG+ XQJXxsZ1k1kKZvBW7Fnyk62B8Q1PFyMHh4SAicTuo+ldjJxAppjEhXvr2boYuTiEBI4wSkzY sIcJwlnCKPH38TUmkAY2AQuJ7n/aIA0iAokSS2bOZgexmQWKJU6eO8kEYgsLGEt8m/mEEaLG RGLj8+dgc0QEdjFKPJp+CSzBIqAqsf/SFmYQm1fAV+Lv7RYwW0jgHJfEziZvEJtTIFDi78ID YPWMQNd9P7WGCWKZuMStJ/OZIK4WkFiy5zwzhC0q8fLxP1YIW0li0e3PYDczC2hKrN+lD9Gq KDGl+yE7xFpBiZMzn7BMYBSbhWTqLISOWUg6ZiHpWMDIsopRtDi1OCk33chIL7UoM7m4OD9P Ly+1ZBMjMOIObvltsIPx5XPHQ4wCHIxKPLwb1v8PEWJNLCuuzD3EKM3BoiTOa2d8KERIID2x JDU7NbUgtSi+qDQntfgQIxMHp1QDY59rWditfsMn4oUyG1M+SV1a0bzZwzBNNIHvb2aJeEGO QtSNJofGfcYvnjFWTm0V33pcynuZm9n07pqoabpXt5YoZF49vibi0sKdpguXlPNbWXB+NHk/ 9Xy1yfpCHduIC3wmzy5xaOyq77hyddvao/vvcYfEVBVIqX9yyY3+yCxu9/niRm1bJZbijERD Leai4kQAX7OkepkCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/MoV7ZBS69jCHQXEU0Xp7u5147eI>
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: Wed, 11 Mar 2015 14:19:39 -0000

Hi,

>> I think there is some confusion between the underlying link protocol 
>> used by candidates and the protocol running on top of ICE. I do not 
>> think TCP is defined as a protocol that can operate on top of ICE. It 
>> is defined in RFC
>> 6544 using framing from RFC 4571, as a protocol for underlying links.
>> Whatever protocol is defined on top of ICE should support operation on 
>> top of packetized communication protocol provided by ICE and should 
>> define how its packets can be demuxed from STUN packets used for ICE 
>> connectivity checks. So far things like RTP, DTLS, and SCTP fit such 
>> requirements. 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.
>
> Exactly. Please Christer, don't go to layer 4 protocols. Neither IPv6 can run over an ICE initiated "virtual transport" ;)

I am not the one saying "whatever protocol" :)  

My point is that we need to be more clear about the scope - we can't just say "Take whatever protocol and do a "5-tuple"/"virtual connection" search-replace." :)

Regards,

Christer