IETF Logo Mail Archive

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

Harald Alvestrand <harald@alvestrand.no> Fri, 13 March 2015 10:55 UTC

Return-Path: <harald@alvestrand.no>
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 553C91A00F6 for <rtcweb@ietfa.amsl.com>; Fri, 13 Mar 2015 03:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 rSpCJOwSD6LF for <rtcweb@ietfa.amsl.com>; Fri, 13 Mar 2015 03:55:37 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8041A0115 for <rtcweb@ietf.org>; Fri, 13 Mar 2015 03:55:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 66A507C429E; Fri, 13 Mar 2015 11:55:34 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wyuJKIpAxTHG; Fri, 13 Mar 2015 11:55:31 +0100 (CET)
Received: from [10.100.7.83] (220.Red-88-7-178.staticIP.rima-tde.net [88.7.178.220]) by mork.alvestrand.no (Postfix) with ESMTPSA id 8A1557C4292; Fri, 13 Mar 2015 11:55:27 +0100 (CET)
User-Agent: K-9 Mail for Android
In-Reply-To: <CAOJ7v-1baW-jme7pApSFZc7aDXAmVm++p60-c9ZtjFxHSybf=g@mail.gmail.com>
References: <54F74B02.1070902@jive.com> <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> <7594FB04B1934943A5C02806D1A2204B1D737A76@ESESSMB209.ericsson.se> <CAOJ7v-1baW-jme7pApSFZc7aDXAmVm++p60-c9ZtjFxHSybf=g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----48ZPCISQWFEDTESCW100Y8QBQ7TX6Z"
Content-Transfer-Encoding: 8bit
From: Harald Alvestrand <harald@alvestrand.no>
Date: Fri, 13 Mar 2015 10:55:16 +0000
To: Justin Uberti <juberti@google.com>, Christer Holmberg <christer.holmberg@ericsson.com>
Message-ID: <DB34ECFD-26AF-4065-892D-12739258C2D1@alvestrand.no>
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/o_IBwJVB67nAqjzvE_ChEZhGH4c>
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: Fri, 13 Mar 2015 10:55:40 -0000

It's the checksum.

Den 12. mars 2015 16.00.45 WET, skrev Justin Uberti <juberti@google.com>:
>On Thu, Mar 12, 2015 at 3:12 AM, Christer Holmberg <
>christer.holmberg@ericsson.com> wrote:
>
>> 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.
>>
>
>I don't agree. SCTP can be tunneled over UDP, as we know, so why not
>TCP?
>The ports in such a tunnel scenario are just as unnecessary as in SCTP
>over
>UDP.
>
>>
>> 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
>>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

v2.23.0 | Report a Bug | By Email