Re: [rtcweb] Referring to 5245bis or 5245?

Sean Turner <sean@sn3rd.com> Thu, 08 June 2017 14:32 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7386127136 for <rtcweb@ietfa.amsl.com>; Thu, 8 Jun 2017 07:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 Y4DJ6V5-aQaO for <rtcweb@ietfa.amsl.com>; Thu, 8 Jun 2017 07:32:16 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB097127058 for <rtcweb@ietf.org>; Thu, 8 Jun 2017 07:32:16 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id m47so125442842iti.1 for <rtcweb@ietf.org>; Thu, 08 Jun 2017 07:32:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LkjZdBbfNN9vmZzN+a1TfpuTgCtGCKh3EbSFkGcVxB8=; b=Ick+K4JsxO7d5ALD6tRitWseil8sBRB8qkD/CcPKWEgX056cfnUrE735Kdl1sR0nQ0 2oVk7phxy4HVxU0J6FagRs4yyXRdN5VT8+GCoB7pFSKjyGcQSnj66wxWm2k9pq5+GZyN fI1jUlzDnMOii8Sub0TcP4VwSOa1UiRGSWjZM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LkjZdBbfNN9vmZzN+a1TfpuTgCtGCKh3EbSFkGcVxB8=; b=PDhJ/4RUQfTPGUqPF7WfeYhtWbvWp2smkS7DNHru3obcRBeVSm0Gh7r/B3Tm/4y3cO 6Is4C9jfWnsTdQKMzJDgsEZgysjFH5tWK8pPEb6t/MZPskqPvBn/NFKhxyb1cCz6YYfD w+cFCVepXHLTA+Hp7URYVOVWQSZ8D8abKT2ClINt4GFBF+vfNGum/M1nQWY9BRqC/G6A apJOFx8HI3IvivB7X0I06vVykCC2eE7qeSv6FbdCAqBS/Hkho0mXbqDcug96tKJvQ1um 2OzbfpWSWQefjyPm+8x+uqOx/MJX0zjDhCna8RkxBUMt7SQ5v8j8QRcxdvpAamCRcSrx R5KA==
X-Gm-Message-State: AODbwcDdedgz60rmjCjtH/thpR2/yzI5JpwkZWeiJcaskCFjexeM6yKg n8tRvGvenNkVhDkf
X-Received: by 10.36.192.197 with SMTP id u188mr5866002itf.39.1496932336057; Thu, 08 Jun 2017 07:32:16 -0700 (PDT)
Received: from ?IPv6:2001:450:1e:232:e0e2:f5a3:78ef:af82? ([2001:450:1e:232:e0e2:f5a3:78ef:af82]) by smtp.gmail.com with ESMTPSA id r77sm2338964ioe.16.2017.06.08.07.32.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jun 2017 07:32:14 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <3f0ae431-c9cc-9912-881a-9fea23d402ca@cisco.com>
Date: Thu, 08 Jun 2017 16:32:09 +0200
Cc: Eric Rescorla <ekr@rtfm.com>, "mmusic-chairs@tools.ietf.org" <mmusic-chairs@tools.ietf.org>, RTCWeb IETF <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DD58D50-6742-4203-A7A5-BC3F037274C3@sn3rd.com>
References: <4C1F0FE7-F7E6-47F7-922D-057E4E7FA466@sn3rd.com> <CABkgnnVhS07gUdw+MJT8dLH89=Y1HBhrrwh6wTGs5gyy8O5DWw@mail.gmail.com> <3CC0A416-5A81-46FA-886C-5F43BA5193A6@sn3rd.com> <6BD64B92-4DE2-4BAD-A23D-65E8F52E13B0@sn3rd.com> <CAOW+2duBrC3f=-XaKFvMmyQ_JU72eTsES-UZDYPjQg6yZhab8Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4CBA8FEF@ESESSMB109.ericsson.se> <E9FF59C3-91E6-435D-A57B-7DE96CD7B969@iii.ca> <58f45548-6c04-348b-a9e7-b87a17dbe93c@cisco.com> <CABcZeBNW4UR29rOoxyS8mT_cehz0wFXf+iuV-0ciNYUyYUXYJA@mail.gmail.com> <3d52929e-a0f1-36d9-3361-93b875d355cc@cisco.com> <CABcZeBMSiy06DeRNox9b=A-xtGyAr3OB8rxBbtBO9OdL+1p9sQ@mail.gmail.com> <3f0ae431-c9cc-9912-881a-9fea23d402ca@cisco.com>
To: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/wwQAPoDkr31juIYWsuupdWU4xBs>
Subject: Re: [rtcweb] Referring to 5245bis or 5245?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Jun 2017 14:32:18 -0000

> On Jun 8, 2017, at 15:14, Flemming Andreasen <fandreas@cisco.com> wrote:
> 
> 
> 
> On 6/7/17 10:38 PM, Eric Rescorla wrote:
>> 
>> 
>> On Wed, Jun 7, 2017 at 10:45 PM, Flemming Andreasen <fandreas@cisco.com> wrote:
>> Based on https://datatracker.ietf.org/doc/draft-ietf-ice-rfc5245bis/referencedby/ (or you can take a look at https://datatracker.ietf.org/doc/draft-jennings-rtcweb-deps/):
>> 
>> draft-ietf-mmusic-dtls-sdp
>> 
>> draft-ietf-mmusic-ice-sip-sdp
>> 
>> draft-ietf-mmusic-sdp-bundle-negotiation
>> 
>> I don't see why any of these would require ICE-bis except through trickle.
>> 
>> I appreciate that the document reference graph shows a lot of dependencies on ICE-bis, but what's not clear to me is what the *technical* dependencies are.
> The MMUSIC list would be the best place to discuss that further and if you want to make changes, then I'd suggest a thread per draft to understand the technical dependencies. 
> 
> FYI, the MMUSIC chairs, ICE chairs and our AD (Ben Campbell) did have a discussion around this issue about a year ago in the context of bundle. At the time, we did identify references to new 5245bis behavior in the bundle draft that some people had asked for explicitly. 
> 
> Thanks 
> 
> -- Flemming 

Flemming,

I have to ask if those conversation happened on list?  If not, it seems to me like the shorter path might be to share those 5245bis behaviors you identified.

spt