Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 28 March 2014 18:25 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44D3E1A0713 for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 11:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
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 pY9r1ZUVpZbN for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 11:25:41 -0700 (PDT)
Received: from sesbmg21.mgmt.ericsson.se (sesbmg21.ericsson.net [193.180.251.49]) by ietfa.amsl.com (Postfix) with ESMTP id 766A01A06CB for <mmusic@ietf.org>; Fri, 28 Mar 2014 11:25:40 -0700 (PDT)
X-AuditID: c1b4fb31-b7f888e000000826-36-5335bea1f915
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 14.BA.02086.1AEB5335; Fri, 28 Mar 2014 19:25:37 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.02.0387.000; Fri, 28 Mar 2014 19:25:36 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
Thread-Index: AQHPSGhBkGgOUI/R1UC6/eMZQzB+K5r1Co+AgAA1L2D///WRgIABYMgAgAA+SHo=
Date: Fri, 28 Mar 2014 18:25:36 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D267A12@ESESSMB209.ericsson.se>
References: <5331E601.8070605@cisco.com>, <53344BC7.3040409@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se> <618CB82A-1BDD-4283-B0BA-09DE422A340A@cisco.com>, <53359792.5090603@alum.mit.edu>
In-Reply-To: <53359792.5090603@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyM+Jvje7CfabBBhe+CVvMneJnMXX5YxaL FRsOsDowe/x9/4HJY8rvjaweS5b8ZApgjuKySUnNySxLLdK3S+DKuLGzkaVgo0jFh39lDYw/ +bsYOTkkBEwkPn9ZywZhi0lcuLceyObiEBI4wSjRsvQxlLOEUeLAph+sXYwcHGwCFhLd/7RB GkQE4iXuHmhhBAkzC6hLXF0cBGIKC9hJ3D3DCVFhL3Hg43RmCNtP4uzEiSwgNouAqsS6putg cV4BX4nl/+4yQmy6zyixqPE6O0iCU0BH4szyNWBFjEC3fT+1hgnEZhYQl7j1ZD4TxM0CEkv2 nGeGsEUlXj7+B3alhICixPJ+OYhyHYkFuz+xQdjaEssWvobaKyhxcuYTlgmMYrOQTJ2FpGUW kpZZSFoWMLKsYpQsTi1Oyk03MtTLTc8t0UstykwuLs7P0ytO3cQIjKmDW34b7mCceM3+EKM0 B4uSOC/D9M4gIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYzuTBMVe8TPnC87HHsx7MPDBTle hluTQpv15Crqpdljt/+acDn3W7BgxPzu2p0f717Y+HhHxZozW7TmlEj7+Rxzm3KhqKH22Z7d jMU6ytryyeJ30uRrJn6+HPnHb1bI63ldWR4KKVIH56q4SKsWvChJ3HCI9Qnvs1Vubh/PX7EU 024Uu2pw00CJpTgj0VCLuag4EQBH3/x4dwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/r7YwcFWE886tzEuM0B6O4XtvT8o
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Mar 2014 18:25:42 -0000

Hi,

>>>> If a new DTLS association is to be established, is it well defined when
>>>> to cut over to it? ISTM that some procedures are required here to ensure
>>>> that data isn't lost, or replicated.
>>>
>>> I don't think we can define any exact procedures for that. DTLS-SRTP doesn't define any exact procedures either. RFC 5763 only says:
>>>
>>>   "Once the new session keys are established, the session can switch to using these and abandon the old keys."
>>>
>>> ...and I don't think we can say much more.
>>>
>>> In addition, I assume there are procedures on the fax application layer for avoiding lost data.
>>>
>>> Also, I think it will be rare that the keys and/or transport parameters change during a fax transmission. Or, if they do, perhaps a fax transmission failure is acceptable?
>>
>> Data loss prevention/recovery mechanisms are in place at the fax layer.
>
> The case I'm talking about is: A new O/A results in establishing a new
> connection, replacing a prior one. At some point during that process
> both the old and new connections are usable. Then, at some point the
> sender stops sending to the old connection and starts sending to the new
> one.

Yes.

> For the receiver to get all the data, it must keep reading from the old
> one until it has received the last packet sent there, and must start
> reading on the new connection soon enough to get the first data sent
> there. And there is a possibility that the packets won't arrive in the
> order sent, so ceasing to read from the new one once something has been
> received from the old one could cause something to be lost. (Or course
> these aren't reliable protocols, so something could be lost in the
> network too.)
>
> Are you saying that the fax layer is sufficient to deal with this? (I
> haven't looked at it.)

Yes.

I don't think the receiver should cease to read from the new one if it receives something from the old one.

If it helps, we could add a sentence saying that the receiver needs to be prepared to receive data on both the new and old connections, as long as they are both alive.

> I realize that this problem isn't unique here - it applies any time O/A
> results in a change to the media path. I've wondered about it for a long
> time, but have assumed it has typically been considered acceptable to
> get a "glitch" in an audio or video stream in such a case. But it is
> less acceptable for fax.

It is not even introduced by this draft, as FoIP using SDP O/A has been around for many years.

Regards,

Christer