Re: [MMUSIC] Thoughts on draft-ietf-mmusic-dtls-sdp-10 semantics

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 04 March 2016 00:12 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 962111B305A for <mmusic@ietfa.amsl.com>; Thu, 3 Mar 2016 16:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Level:
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_110=0.6, J_CHICKENPOX_111=0.6, 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 r7cAQ1vqrjGv for <mmusic@ietfa.amsl.com>; Thu, 3 Mar 2016 16:12:19 -0800 (PST)
Received: from resqmta-po-01v.sys.comcast.net (resqmta-po-01v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:160]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E0211B3056 for <mmusic@ietf.org>; Thu, 3 Mar 2016 16:12:19 -0800 (PST)
Received: from resomta-po-17v.sys.comcast.net ([96.114.154.241]) by resqmta-po-01v.sys.comcast.net with comcast id RcBU1s0085Clt1L01cCJrS; Fri, 04 Mar 2016 00:12:18 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-po-17v.sys.comcast.net with comcast id RcCJ1s0053KdFy101cCJZq; Fri, 04 Mar 2016 00:12:18 +0000
To: mmusic@ietf.org
References: <CABcZeBNJ6jdL7SfLaatfr28X83dVOafpi=jrM6bSJ-qpmj4RuA@mail.gmail.com> <CAD5OKxuK9wBG47d+SwBH_f8-PgMQJuxFRmMg9E4omjgqO0tNbQ@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <56D8D2E1.2030306@alum.mit.edu>
Date: Thu, 03 Mar 2016 19:12:17 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxuK9wBG47d+SwBH_f8-PgMQJuxFRmMg9E4omjgqO0tNbQ@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1457050338; bh=rPs9uTahQJoVXVRqyrrG/NjtqdZGJF8o0q+siC4JT8o=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=QHDvepIvnCfgKAojd0mG5/hV73MyLMRglXvPKHIho4/OfeFfMyecdtX+e8Sca+c33 8epJMNlVfTAKSyNqh2fp1OT/dkMpcX4fTseHZi396/aF9lx3x1lKVPbNfwSJ57xXBW Ya3gCRrwzKV4yd8idOuLKQCh/Zpgz8kHB81tQFECrYNcIxGx0fe3cSuXTHCleq49cq tzN4vM0d3BiNx+eJ4ZD22C0HOngl8gFeuhiwrWZDxfLsVA+zfevUL7hp/6Is4i1f0T Pn59QU5j1WRbGMS4ttzda8qbQSpzOlzIid8puvVjUuTQH6aKM//l/H13TZwpq2KWr2 Mg8UrUtNnqd8g==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/beZJuFe8W7qRYAGJADwA5WQ8-vU>
Subject: Re: [MMUSIC] Thoughts on draft-ietf-mmusic-dtls-sdp-10 semantics
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Mar 2016 00:12:20 -0000

On 3/3/16 6:23 PM, Roman Shpount wrote:

>     Assuming you are comfortable with the above, I think the indicator
>     we want is some sort of “connection-id” parameter, either as a
>     standalone value or as a value which is unique in association with
>     the fingerprint. This seems cleaner than having a “new” versus
>     “reuse” token. The semantics would be that if you see a new
>     identifier that means you need to form a new association but that
>     multiple replays of the same identifier mean that you reuse the same
>     association (i.e., do not DTLS reconnect).
>
>
>     This resolves the idempotency concern that present with the existing
>     proposal, and also makes backwards compatibility simpler; a change
>     in either a=fingerprint or a=dtls-connection-id will trigger a new
>     DTLS connection.
>
>
> I have actually proposed this very thing (dtls-association-id instead of
> dtls-connection), but people on the list found this to be too complex.
> This has an additional benefit of handling some of the 3pcc use cases
> when in response to empty INVITE it is unknown if generated offer will
> be used in the same session or in the new one. dtls-association-id
> resolves this nicely, but we settled for a simpler requirement to always
> respond with a=dtls-connection=new in response to empty INVITE.
>
> The question is does group feels strongly about changes to
> (dtls-association-id from dtls-connection at this late stage, since this
> will require a major rewrite.

I had discomfort with connection=new/existing back when it first came up 
with TCP, exactly because it isn't idempotent. I don't recall why I lost 
that battle.

But now that is water over the dam. So I think it takes a stronger 
argument for why to adopt a different pattern now for something so 
similar. If the SDP implementation already has to deal with this for 
a=connection, then why is it a problem to also do so for dtls-connection?

	Thanks,
	Paul