Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 28 March 2014 20:16 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 2A1801A0344 for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 13:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 L68bAIMB_HIf for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 13:16:04 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2E11A0303 for <mmusic@ietf.org>; Fri, 28 Mar 2014 13:16:04 -0700 (PDT)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta12.westchester.pa.mail.comcast.net with comcast id j1dN1n0010SCNGk5C8G28n; Fri, 28 Mar 2014 20:16:02 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta09.westchester.pa.mail.comcast.net with comcast id j8G21n0023ZTu2S3V8G2eb; Fri, 28 Mar 2014 20:16:02 +0000
Message-ID: <5335D881.4@alum.mit.edu>
Date: Fri, 28 Mar 2014 16:16:01 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mmusic@ietf.org
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> <7594FB04B1934943A5C02806D1A2204B1D267A12@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D267A12@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1396037762; bh=PLsdgJZ+TSCThVn0yr+u736WkDmMkovDamgH/9zmx1k=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=qdq8uPl/v7BmmuIOXX6/R/Egrg4jznHXJGY8qx+FjBV3x7FOKXhIY3nqoWgifZhCi vgABMBAXK+WW3zV1aP6tE0H8B2w/Oa+BliwILQ+Iy+gdXLTgkfGNFXL2oOUh3C50A2 EtDyUg8PCkI4wxVx5D/1CXXaEllsGIf3FlWAp8d91bcGyEXY18uHxsCU3PUveCYpgE 6tbcKHNtu7yoIibPZTT7XG8bXBHMaByEjn8p6o/uGTaoIfHL5XQtcsqDWmUKSECMex 64o+4CiGPpy7gayKuKBatRT3c43muc+jzJSVqkUwcrDsY/j02NB++aCDyo1XBzBOnF ry1iT380oV9oA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/kPQlUZxpWxB8CAu8kHdzR8KTjMg
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 20:16:07 -0000
I've had my say on this. I'll be satisfied with whatever you decide to do about it, including nothing. Thanks, Paul On 3/28/14 2:25 PM, Christer Holmberg wrote: > > 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 > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic >
- [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06 Flemming Andreasen
- Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtl… Paul Kyzivat
- Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtl… David Hanes (dhanes)
- Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtl… Adam Gensler (agensler)
- Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtl… Christer Holmberg
- Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtl… Gonzalo Salgueiro (gsalguei)
- Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtl… Paul Kyzivat
- Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtl… Christer Holmberg
- Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtl… Paul Kyzivat
- Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtl… Christer Holmberg