IETF Logo Mail Archive

Re: [rtcweb] Default proto transport in JSEP

Roman Shpount <roman@telurix.com> Tue, 20 November 2018 06:16 UTC

Return-Path: <roman@telurix.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 BA64D1277D2 for <rtcweb@ietfa.amsl.com>; Mon, 19 Nov 2018 22:16:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.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 4zrBEikLfTju for <rtcweb@ietfa.amsl.com>; Mon, 19 Nov 2018 22:16:02 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 77F2212870E for <rtcweb@ietf.org>; Mon, 19 Nov 2018 22:16:02 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id z9so487409pfi.2 for <rtcweb@ietf.org>; Mon, 19 Nov 2018 22:16:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ASXxn7Tj4LE3U4OmVLVqUg9rluquMSJ5YaE1dwr5z9o=; b=HdiFkF5pgugjKVzBH5iHLHggbhpzK8S0nU3rwAtWfQVuUKLolNfUanTkY3w2RqyqUV RAlDMZJmEIhxIt4cJMltOjCPRrNvw0bihKkoA1pkNSKu1aoWqsU/F3IwtT1zGXvDDwNu RNerp81TPHQ0dYnhSrek9Kzfs6EcWdVEBKS6WzVXayM/wg3islwrYrHnvllYEZcex1Ph G6pzQCK8Te2f5bc5y3VosTPpQ0npZgzR4Qs3xtdET72HIVJT/CNF1Sn71Vz+3950wUbQ O51oaz87j5qmJkjwQe3XJsen9u3rycccH2u81uSCxCue1i8n6Hn21MvosV/U6NQGFA2e WE7w==
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=ASXxn7Tj4LE3U4OmVLVqUg9rluquMSJ5YaE1dwr5z9o=; b=oJvtlCVer+6sNkhH8LJwM+84yqpQ9YIrzabx68R9OyoOQWF2+OqUihICt+TeXPZcnw r8X7zx0yxR7phLP+CX+CNJhgzotqcBQu7DTyI2ayd2074Qp+1Hqdr96RgtMLd2JLk06E XtKUI61i+IWgNJemct71jJ6qbiAzwycF7V3FsjdexGL1PUBl1AHPYwzgMAYO4RklXqSZ 965rTDKLDXqCYDz+1QXNgL9R0dPrq/Tioje0JueBj6KwJy1LGa7e3GLc0IHBV3RefW3d 8OUfA7SVwIHVilOcHQxUVoZW4+DABFAdtw3VweJe92/oCoxLBYOiSW7ip3B8uO0d1wg5 WjUA==
X-Gm-Message-State: AA+aEWboLUZHSdHipvZdu7aLT2HVlJhJSP8M0vw3JBmNttIh+3VkweHo FgdZROTbr5WfVVfPwYhJEVosg/WVrnQ=
X-Google-Smtp-Source: AFSGD/Ve4DdIBJz+vtTdOqfw8cGQDjEvZHBQGAQx+OAkK/4MEnr3mAh8O/tQUVEI0eXc3c+mWxf9xQ==
X-Received: by 2002:a63:504d:: with SMTP id q13mr743352pgl.319.1542694561855; Mon, 19 Nov 2018 22:16:01 -0800 (PST)
Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com. [209.85.210.181]) by smtp.gmail.com with ESMTPSA id g136sm27111503pfb.154.2018.11.19.22.16.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Nov 2018 22:16:01 -0800 (PST)
Received: by mail-pf1-f181.google.com with SMTP id i12so477234pfo.7; Mon, 19 Nov 2018 22:16:00 -0800 (PST)
X-Received: by 2002:a62:1b50:: with SMTP id b77mr920986pfb.36.1542694560687; Mon, 19 Nov 2018 22:16:00 -0800 (PST)
MIME-Version: 1.0
References: <CA+9kkMADnZJBaV0hfLuwGU0bGBEP5tCPZ=8Zd_85Dgzi37ghAQ@mail.gmail.com> <CAD5OKxsNFFmER__H0+5Mzts58yn9cWLMEADhSnLR4nreKD9WAQ@mail.gmail.com> <CALiegfkHXv6f8P3C-C=2RKCyxWfzCAzkzOqxBXmmsNCPrZzFfg@mail.gmail.com> <CAD5OKxswZdGm1CYvy=NoyEtN-eFFp7Sc8mmGT7jAJ-q3msJYXA@mail.gmail.com> <CALiegfmFV=988+WuViUQRGJRgR=mcqS9Y+eDnL4pH6VrbJRvCQ@mail.gmail.com> <CAD5OKxtwuQu0du+ptmJpX0ALQnUtjLG==NanP8OB51D4M9fYhg@mail.gmail.com> <CALiegfnMbwTruVKU-VnsZvddqRhnuCm1k8zLcLSuWSs9zT1JUA@mail.gmail.com> <CAD5OKxtxAiBbVY4HQjfjwqfsGoUxAZzmmrTWVfe7pG6MTsHGRA@mail.gmail.com> <CALiegfnVOFvUKYMRp7z0Q3aVyzbi=+JuyXmH+PL6_pNW9j9PVA@mail.gmail.com> <CAD5OKxtpepraJWVbJy2+x_4pFbeqF57=yh1GVF-WoYGBX1OV-Q@mail.gmail.com> <CALiegf=ffb1UL0FPrk770Q-ACQL-ySAqxBzB1M0yJXZUM6y9sg@mail.gmail.com> <CAD5OKxtj=nEWjOWztcAVMDsFOFRGO7hQaKUsn-Pqbk7Ma64Trg@mail.gmail.com> <CALiegfno4y5P-qLkrxSs0zLbEEUo1HWyp0rfEA8KecRjTQ43sQ@mail.gmail.com> <CAOJ7v-2o1Se9zaMgktQtwNW46zvB2i7Hk7+GK1yhWJV5xcT7ZA@mail.gmail.com> <CAD5OKxveNtx3uD7tD_mTgE-Rv2JTZPBmjk34iUJD9uw25-ZCzQ@mail.gmail.com> <CAOJ7v-1V_vtq+szN6299kw9dH_TOz9sxa+YYwQkBwHeJPoqvgA@mail.gmail.com> <CAD5OKxt6JyFXsdANSX13LytLsosRQUnP5oKoR1PUjZmJyP0kxw@mail.gmail.com> <CAOJ7v-1VuktqXrX6NVD85UWNPP6e_cbs=_YOr6ewn7g-KhR_ug@mail.gmail.com>
In-Reply-To: <CAOJ7v-1VuktqXrX6NVD85UWNPP6e_cbs=_YOr6ewn7g-KhR_ug@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 20 Nov 2018 01:15:49 -0500
X-Gmail-Original-Message-ID: <CAD5OKxuSGJp+JnnMxzx0jxs99Rgw-KBFAKE14MD4pXPV-c_9Eg@mail.gmail.com>
Message-ID: <CAD5OKxuSGJp+JnnMxzx0jxs99Rgw-KBFAKE14MD4pXPV-c_9Eg@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: Iñaki Baz Castillo <ibc@aliax.net>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000496a33057b12918b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/yYo5HTnl2QbeRUv7de7Nyn4Idw4>
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: Tue, 20 Nov 2018 06:16:05 -0000

On Tue, Nov 20, 2018 at 12:58 AM Justin Uberti <juberti@google.com> wrote:

> Anyway, we have the 3 choices listed below. We differ on which is the most
> pragmatic solution. If the WG has enough voices in support of #2 or #3 to
> overturn the consensus of #1 from IETF 103, I will write it up accordingly.
>

So the 3 choices are:

1) (current) Match IP and port, but stipulate an exact proto value -- This
choice is not compliant with either RFC 5245 or draft ice-sip-sdp. If this
is selected, ice-sip-sdp will need to be updated
2) Match IP, port and proto -- Compliant with both RFC 5245 and ice-sip-sdp
3) Set IP, port, and proto to fixed values -- Compliant with only
ice-sip-sdp but not with RFC 5245

Regards,
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email