IETF Logo Mail Archive

Re: [rtcweb] Last Change for draft-uberti-rtcweb-rfc8829bis

Roman Shpount <roman@telurix.com> Fri, 05 May 2023 14:04 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 1F53AC159495 for <rtcweb@ietfa.amsl.com>; Fri, 5 May 2023 07:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telurix.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hvIKdlcrL1kv for <rtcweb@ietfa.amsl.com>; Fri, 5 May 2023 07:04:23 -0700 (PDT)
Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C446C14F738 for <rtcweb@ietf.org>; Fri, 5 May 2023 07:04:23 -0700 (PDT)
Received: by mail-oi1-x232.google.com with SMTP id 5614622812f47-3921cd76d5bso1183106b6e.2 for <rtcweb@ietf.org>; Fri, 05 May 2023 07:04:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix.com; s=google; t=1683295461; x=1685887461; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Jl+32ZBEZs16xmAlr3jY23oNImrKhsXuLXTOseSQSM0=; b=Q/yYNkkIxiNWdd1vSpJojP3RU+lcHm/wyp6hndODll54zH3NTuSEtCi+w1cRPJF5dQ 3QmM5RnR+9rd1L9v9sWWjPXdZB6KxPO0AzSkAGXcbvfOLKDBFDR+DkA1ypxhtHby7TUr y4NJwB6qMMfht/IjuozvwNT6P/wcMZWJaKNho=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683295461; x=1685887461; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Jl+32ZBEZs16xmAlr3jY23oNImrKhsXuLXTOseSQSM0=; b=Hjf7iISGErYnjh3g0L4kdchbzmGPcN4ceKEsPf01tmtj2+549lR0GYyK1CLKC06oi2 eMDIcV8g4PknCgHLIvrpP8wYiYRH/G6nnFlNzMkRoqUQbIqKQo1Ogj92rGjTUZQ5uIRr M99kB3Q6D3M/iT7jh0fNZs0adaGjWnSmOv2phOKJHNbKLSon8bj3v3cD2qPiBaUnoajd F5luUA2VubnI4N6ZBLK/2nwm2zsyGofePt7vYzypgTSn5TLv4F3bB5UnFjMxcbhSTRda R6oM7vFDAVnnBOOzKeofJO8aoWxYZ4Unis8u0pAkOuG0DQrnqDAhYPnCbPVDc9KWjW2F 1huA==
X-Gm-Message-State: AC+VfDzWzG4dPlEYaJjDhZ0nC809FVUkJxRdukGujU3RRh8IbqvxgvYo HiB17qPjv2Lwp80aAf3tPt0lkj41TDpGygkFzwA=
X-Google-Smtp-Source: ACHHUZ4RCN/ucHUviMuoB378amUcPR7nqf8+bliRdAJPUOf54A/MTf5vqK2tedFIrHRRTXGNTXL4Zg==
X-Received: by 2002:a05:6808:6286:b0:38c:3cfd:e3a6 with SMTP id du6-20020a056808628600b0038c3cfde3a6mr545673oib.31.1683295460856; Fri, 05 May 2023 07:04:20 -0700 (PDT)
Received: from mail-oo1-f50.google.com (mail-oo1-f50.google.com. [209.85.161.50]) by smtp.gmail.com with ESMTPSA id p17-20020a4ae151000000b005462a25c4f9sm983250oot.9.2023.05.05.07.04.20 for <rtcweb@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 05 May 2023 07:04:20 -0700 (PDT)
Received: by mail-oo1-f50.google.com with SMTP id 006d021491bc7-54eb5cdd418so1184762eaf.0 for <rtcweb@ietf.org>; Fri, 05 May 2023 07:04:20 -0700 (PDT)
X-Received: by 2002:a4a:6b1e:0:b0:547:7816:303a with SMTP id g30-20020a4a6b1e000000b005477816303amr610589ooc.4.1683295460037; Fri, 05 May 2023 07:04:20 -0700 (PDT)
MIME-Version: 1.0
References: <8ABC994A-FDB3-4E89-8CD7-F5954E2D761D@sn3rd.com> <4A04053D-C6F6-42E1-B0DD-5382C9E10FA2@westhawk.co.uk>
In-Reply-To: <4A04053D-C6F6-42E1-B0DD-5382C9E10FA2@westhawk.co.uk>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 05 May 2023 10:04:07 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvLr1rm6gweZczsQhAWP-MDn5_58bh+SKTRBg=TW7-d+Q@mail.gmail.com>
Message-ID: <CAD5OKxvLr1rm6gweZczsQhAWP-MDn5_58bh+SKTRBg=TW7-d+Q@mail.gmail.com>
To: Tim Panton <thp@westhawk.co.uk>
Cc: Sean Turner <sean@sn3rd.com>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f29eb305faf2c3de"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/9oA5KNAyhIH4rRK-8eDE-rcUrEY>
Subject: Re: [rtcweb] Last Change for draft-uberti-rtcweb-rfc8829bis
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 05 May 2023 14:04:27 -0000

I am also in favor of approving this since it gives more control to the
application regarding what extensions are supported.
_____________
Roman Shpount


On Fri, May 5, 2023 at 10:03 AM Tim Panton <thp@westhawk.co.uk> wrote:

>
> I’m in favour of us accepting this.
>
> As I understand it, this moves control over the extensions that _may_ be
> used in a session up to the api level and removes the need for the
> application to manipulate the sdp when trying to disable extensions that
> are unsuitable for the current use-case.
>
> T.
> > On 5 May 2023, at 14:43, Sean Turner <sean@sn3rd.com> wrote:
> >
> > Hi!
> >
> > We would like to get comments on a late breaking change to accommodate
> the W3C by 2359 UTC on 12 May 2023. Justin has created the following PR:
> > https://github.com/rtcweb-wg/jsep/pull/1033/files
> >
> > The backstory here is that the WebRTC W3C WG is working on an extensions
> spec that introduces behavior which conflicts slightly with the current
> version of JSEP. There were two options: 1) define an extension to JSEP in
> the W3C specification, or 2) apply a tiny patch to JSEP before JSEP-bis
> that is currently in RFC Editor state.
> >
> > Ted and I had a look at the changes. To our eyes the changes are
> editorial, but neither of us want to approve these changes at this late
> date without WG input.
> >
> > Cheers,
> > spt
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email