Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples
"Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com> Thu, 05 March 2015 13:02 UTC
Return-Path: <Raju.Makaraju@alcatel-lucent.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 54D641A1A02 for <rtcweb@ietfa.amsl.com>; Thu, 5 Mar 2015 05:02:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.61
X-Spam-Level:
X-Spam-Status: No, score=-6.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, 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 sXyX2-JQL7dV for <rtcweb@ietfa.amsl.com>; Thu, 5 Mar 2015 05:01:56 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-01.alcatel-lucent.com [135.245.210.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CF381A01A9 for <rtcweb@ietf.org>; Thu, 5 Mar 2015 05:01:56 -0800 (PST)
Received: from us70tusmtp2.zam.alcatel-lucent.com (unknown [135.5.2.64]) by Websense Email Security Gateway with ESMTPS id A82D61A67F82D; Thu, 5 Mar 2015 13:01:52 +0000 (GMT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id t25D1q8X003936 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Mar 2015 08:01:52 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.56]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.03.0195.001; Thu, 5 Mar 2015 08:01:52 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Iñaki Baz Castillo <ibc@aliax.net>, Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples
Thread-Index: AQHQVqbPY/4BaRkZfUWL2bRYyondfJ0M/70AgAACNQCAAA6BAIAAAZIAgAABcAD///pPYIAAvE4AgAAwswCAAAYfgIAABG+AgAAGSwD//8v1EA==
Date: Thu, 05 Mar 2015 13:01:51 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E726EEC@US70UWXCHMBA02.zam.alcatel-lucent.com>
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> <7594FB04B1934943A5C02806D1A2204B1D728297@ESESSMB209.ericsson.se> <CALiegf=uPN+g546Ucv9s89z14cUTEme55y7B1siXZe97yj7Lig@mail.gmail.com>
In-Reply-To: <CALiegf=uPN+g546Ucv9s89z14cUTEme55y7B1siXZe97yj7Lig@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.17]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/6xNt9SpIjHtgRPw4jGz2hpiaTgw>
Cc: "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, 05 Mar 2015 13:02:01 -0000
> >>When was it agreed that DTLS ClientHello can be sent before the > >> connectivity check succeeded? I understand >that this will increase the > >> connection setup time, but I though that no data should be sent before > the > >> >connectivity check response (consent) from the remote party. > > > > > > > > And, if the ClientHello reaches the server BEFORE the connectivity check > > STUN, how does the server know that it is associated with a given “virtual > > connection”? > > It just ignores it. Client retransmissions will fix that. > > Anyhow, I'm sorry but I no longer remember whether DTLS (which is just > media from the ICE point of view) can be sent before receiving the > STUN response or not. From the point of view of the peer performing > aggressive ICE nomination, it is sending USE-CANDIDATE Binding > requests so I can understand that it assumes a "valid-pair" (even if > it's not replied/confirmed yet by the remote) so media can begin (and > DTLS is just media). <Raju> Aggressive nomination is to avoid 2nd round of checks with USE-CANDIDATE, but not to send media before the nomination is complete. Per [1], nomination is complete only when checks on all valid pairs are complete. A pair becomes "valid" only when you get response. That means, you can't send media (DTLS ClientHello) before you get STUN response. [1] http://tools.ietf.org/html/rfc5245#section-8.1.1.2 8.1.1.2. Aggressive Nomination With aggressive nomination, the controlling agent includes the USE- CANDIDATE attribute in every check it sends. Once the first check for a component succeeds, it will be added to the valid list and have its nominated flag set. When all components have a nominated pair in the valid list, media can begin to flow using the highest priority nominated pair. However, because the agent included the USE- CANDIDATE attribute in all of its checks, another check may yet complete, causing another valid pair to have its nominated flag set. ICE always selects the highest-priority nominated candidate pair from the valid list as the one used for media. Consequently, the selected pair may actually change briefly as ICE checks complete, resulting in a set of transient selections until it stabilizes. </Raju> BR raju
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Paul Kyzivat
- [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Simon Perreault
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Simon Perreault
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Simon Perreault
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Eric Rescorla
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Lorenzo Miniero
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Jonathan Lennox
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Paul Kyzivat
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Bernard Aboba
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Simon Perreault
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Simon Perreault
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Paul Kyzivat
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Paul Kyzivat
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Cullen Jennings
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Justin Uberti
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Eric Rescorla
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Justin Uberti
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Harald Alvestrand
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Schwarz, Albrecht (Albrecht)
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Justin Uberti
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Harald Alvestrand
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Simon Perreault
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Justin Uberti
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Harald Alvestrand
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Justin Uberti
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Simon Perreault
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Roman Shpount
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Iñaki Baz Castillo
- Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples Christer Holmberg