IETF Logo Mail Archive

Re: [rtcweb] [rtcweb-wg/jsep] JSEP says that subsequent offers need to specify the ICE protocol (#854)

Justin Uberti <juberti@google.com> Mon, 28 January 2019 19:50 UTC

Return-Path: <juberti@google.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 B20171311CF for <rtcweb@ietfa.amsl.com>; Mon, 28 Jan 2019 11:50:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.641
X-Spam-Level:
X-Spam-Status: No, score=-17.641 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 NrJHnl6Dr3F4 for <rtcweb@ietfa.amsl.com>; Mon, 28 Jan 2019 11:50:34 -0800 (PST)
Received: from mail-it1-x132.google.com (mail-it1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 1E77F1311CE for <rtcweb@ietf.org>; Mon, 28 Jan 2019 11:50:34 -0800 (PST)
Received: by mail-it1-x132.google.com with SMTP id g85so379764ita.3 for <rtcweb@ietf.org>; Mon, 28 Jan 2019 11:50:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r23wJVUB9z4g01NtjSzYmPNY/Ae7gaBAw7oJk3eWvok=; b=MF8yJ7g70Uo7tyHllHwbm/7j61k8TOuOqNI2eN30BErbtv17ZYfkvep5y+SqZ/K0kM NXDv4N8w6xONNnF/rHfsgkjQCqc+rJ/Lpb8hbPnxfKHU8SuQ4d5cLOOeCDwGxCdjq/IP aKyOrhv3VBO4JisHLXL5n16ItQrM6k3MwlZwfbilhKoLn5/C5hO5wzhzF49hQnjkee+x oJHf8SS+djj8mmHwLSFAO/gsfkj0Ta/VkbkNgU939BRu29AvJBuh64K3d3cs7TdKQz3z KjI8V0OxgBx16bsIMlPj0DTCpPscBfaHckD9CVHeRh0COTbKFFiwCBm07Q1ZAc+0DuBh xVdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r23wJVUB9z4g01NtjSzYmPNY/Ae7gaBAw7oJk3eWvok=; b=HOFrEfzdyv9mh9nY9j4cQ76nxfmOyA0mw6q9B8EByUTnnwPr0ZWXySoUiAtGx1aYOl y0PRR3iAAMuglyoLm00snoxWSZUHITJaqYkZxPbqkGkCQCYbJcXmyns8Tp/qPnrQHAdu TAYlrIybcoZAxlcwkC5A9dDrk53I61qD87taJ0XD7WuVgijXuV9DdMyQpDOetGQD8ltV 0N6t952icXiUSdjv/OTq0lhLvH8ZDRVlK2wilMJ7rZu8sA2sQV4EFdjCC1g46DaC7htf OB5wQAYPAtuybdTS8pZF7s9iDT/6IdLYB6awIPxgUCI3GuYi8X5BbxyxiVimtYy84p3n 2IxQ==
X-Gm-Message-State: AJcUukdu7gOKnZ5hXp77V5ehU1AWBHZb8+TW2uljNNYrJVW7PBbcQLU0 KH8TkxiCUyLpumla2/Qqnq5fjJMpo5u7rWSMPKiSww==
X-Google-Smtp-Source: ALg8bN7VXOk4NYf2lyzOvMql12wkraCTbOGg7F015C4p5y3R5knWKF9ndivCCeWJDinOhJq3jHbEXqp6Ig8daeFuC5U=
X-Received: by 2002:a24:738f:: with SMTP id y137mr10918027itb.136.1548705033084; Mon, 28 Jan 2019 11:50:33 -0800 (PST)
MIME-Version: 1.0
References: <rtcweb-wg/jsep/issues/854@github.com> <rtcweb-wg/jsep/issues/854/458269864@github.com> <bdcf555f-69fa-5f04-e42e-a976cde2bdb3@nostrum.com>
In-Reply-To: <bdcf555f-69fa-5f04-e42e-a976cde2bdb3@nostrum.com>
From: Justin Uberti <juberti@google.com>
Date: Mon, 28 Jan 2019 11:50:22 -0800
Message-ID: <CAOJ7v-3s=mA-_qW+KbJWgyBGXdHUvJX4KUKys7LYSUVJn9S64w@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, Roman Shpount <roman@telurix.com>
Content-Type: multipart/alternative; boundary="0000000000005c5462058089fdf5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/P-rRv5REFSXxj4tYoBRGdWkG9mM>
Subject: Re: [rtcweb] [rtcweb-wg/jsep] JSEP says that subsequent offers need to specify the ICE protocol (#854)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 28 Jan 2019 19:50:37 -0000

OK, will take a shot today or tomorrow.

On Mon, Jan 28, 2019 at 11:39 AM Adam Roach <adam@nostrum.com> wrote:

> Taking it back to the RTCWEB mailing list.
>
> This seems like a better formulation than the text that I put together,
> and it is a similarly minimal change that has no impact on any current
> WebRTC implementations (at least, that I know of).
>
> Justin -- if you're willing to craft text that captures this, you'll
> probably do a better job of doing it in a style that matches the rest of
> JSEP than I can.
>
> /a
>
> On 1/28/19 1:33 PM, Roman Shpount wrote:
>
> My proposal was to use TCP/DTLS/blah whenever the default candidate is a
> TCP candidate and *ICE nomination is complete*. If TCP candidate become
> default candidate after ICE nomination is complete, both end points should
> support TCP/DTLS based protocol. In all other cases, candidates are
> either still being collected or UDP candidate should be present and used as
> default.
>
> In the initial offer, when ICE nomination is in progress, when ICE restart
> is initiated, end points must still use UDP based proto, since we do not
> want them to send TCP based offer if remote does not support it or change
> the proto during the ICE negotiation.
>
> Regards,
> _____________
> Roman Shpount
>
>
> On Sat, Jan 26, 2019 at 8:29 PM Justin Uberti <notifications@github.com>
> <notifications@github.com>
> wrote:
>
> > Path in #862 <https://github.com/rtcweb-wg/jsep/pull/862>
> <https://github.com/rtcweb-wg/jsep/pull/862> seems to be to
> > use TCP/DTLS/blah whenever the default candidate is a TCP candidate. As
> > discussed in #394 <https://github.com/rtcweb-wg/jsep/issues/394>
> <https://github.com/rtcweb-wg/jsep/issues/394>, this
> > will break endpoints that don't understand the TCP/DTLS/RTP/SAVPF proto
> > name, but at this point such endpoints should be rare.
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/rtcweb-wg/jsep/issues/854#issuecomment-457880866>
> <https://github.com/rtcweb-wg/jsep/issues/854#issuecomment-457880866>, or
> mute
> > the thread
> >
> <https://github.com/notifications/unsubscribe-auth/AEh5ShA-_F70HMwECsHCaHt_kHcJPxBhks5vHQD6gaJpZM4X5Svw>
> <https://github.com/notifications/unsubscribe-auth/AEh5ShA-_F70HMwECsHCaHt_kHcJPxBhks5vHQD6gaJpZM4X5Svw>
> > .
> >
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/rtcweb-wg/jsep/issues/854#issuecomment-458269864>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AC1khFiKZS_Wmwvu7FfZ2NMgA-hzsf9lks5vH1CNgaJpZM4X5Svw>
> .
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email