IETF Logo Mail Archive

Re: [rtcweb] Default proto transport in JSEP

Iñaki Baz Castillo <ibc@aliax.net> Mon, 19 November 2018 19:36 UTC

Return-Path: <ibc@aliax.net>
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 1EE171292F1 for <rtcweb@ietfa.amsl.com>; Mon, 19 Nov 2018 11:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aliax-net.20150623.gappssmtp.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 LF1ZvfVRq0UZ for <rtcweb@ietfa.amsl.com>; Mon, 19 Nov 2018 11:36:31 -0800 (PST)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 4F1C712F1AB for <rtcweb@ietf.org>; Mon, 19 Nov 2018 11:36:31 -0800 (PST)
Received: by mail-vs1-xe35.google.com with SMTP id h18so18484514vsj.4 for <rtcweb@ietf.org>; Mon, 19 Nov 2018 11:36:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Uud4FYV7B57nMs0K+lQDk+D8q0YNHSFxzU5tyWD66Ww=; b=N0AWUGBd+iCsg4rc+Jx8tdTp2B0DegVfVLSweaOH7XaeLJ4mcM73QGJqKN/eZnIFsi Lp5V7roqYMLpSf52jDsWa3ot441pI8mCw36W7BgYiHDmgX+QxBblhh2wM6bfzhvh/kxd vaGUdU3Vf9/RKFZmOxOySbjav4F7gClgRHxFfPPNhhiCE81HuOYBQMG7NeBnvJTfrL0R zeymzAqUz3ArQsXgZV/I2DW7khyujfcvApe9zk2rATFKlM3eUadO3qzffSROLMwZEpFO SBsq5XN94p7U1ENg5Wi6qOhjLKx3t8SLQ4rUjm6miaA+RL/kGWoEl4EgpcF/j73vu2To PRQA==
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:content-transfer-encoding; bh=Uud4FYV7B57nMs0K+lQDk+D8q0YNHSFxzU5tyWD66Ww=; b=EibC7r1ebKdb0zENI4FzRuN+r2kncY2sqYrUEF7Ed66F83HUb7k66+JSQsMvY2c42A nuW5OUmjQY2x0ub9DIT+9Dc4EdVG3gN0O6wwLEHndpCYXahAnECUeTDvzY88aAENZCmk 6wj24eMAdnXlNRRMA4uBdcUO1DNEqJkSefxrFcyjbRNs7sFgvcSD9fiER7sBiwcsKqtY ZzBToTIxILV6YuJxEzjpySlNf1p7R3Kd/YHWnGyHmtA2T8diZCqPg+kcjvjmMc9AHJ7n drmebqMXZ21hmFNIE4RMGSgLmehmdgGLtVwULSOs4EWa5fcKyHzambVo1LSvVb+AUR3s i1kA==
X-Gm-Message-State: AGRZ1gKi8/H2h50cKKI22lLNAh048N2PKH67b89kY7bKgAEhZZFFLh+S nfqLI1ZdLTGojOvTeW+GmE9IQ+DBa5L/IQ0RXKuzw3aptXQ=
X-Google-Smtp-Source: AJdET5eZjXK9rG9rzsUrJD4EcqbRr8+h9+UFZHrw4I/05qQDzN13kzr97rVEqNmfLP16W1ZWXmXl7lRqL07Z5gpCZ8I=
X-Received: by 2002:a67:3659:: with SMTP id d86mr9907547vsa.17.1542656190209; Mon, 19 Nov 2018 11:36:30 -0800 (PST)
MIME-Version: 1.0
References: <CA+9kkMADnZJBaV0hfLuwGU0bGBEP5tCPZ=8Zd_85Dgzi37ghAQ@mail.gmail.com> <CAD5OKxsNFFmER__H0+5Mzts58yn9cWLMEADhSnLR4nreKD9WAQ@mail.gmail.com>
In-Reply-To: <CAD5OKxsNFFmER__H0+5Mzts58yn9cWLMEADhSnLR4nreKD9WAQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 19 Nov 2018 20:36:18 +0100
Message-ID: <CALiegfkHXv6f8P3C-C=2RKCyxWfzCAzkzOqxBXmmsNCPrZzFfg@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: rtcweb@ietf.org, mmusic@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/jzse1QY7EXQGZ3cneF4nVXDwmKA>
Subject: Re: [rtcweb] Default proto transport in JSEP
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, 19 Nov 2018 19:36:34 -0000

On Mon, 19 Nov 2018 at 19:28, Roman Shpount <roman@telurix.com> wrote:
> The problem is that JSEP proposes to use UDP protocol in the m= line and at the same time update address and port to the currently selected candidate. Based on ice-sip-sdp, if protocol of the current selected candidate does not match protocol in the m= line, this will mean either ICE mismatch or additional candidate with protocol, address, and port form m= and c= line.

We could just assume that no WebRTC capable endpoint will (absolutely
never) rely on the content of the c= line or the proto indicated in
the m= line (no matter it indicates "CHICKEN" as proto).

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email