Re: [rtcweb] WG Action: Rechartered Real-Time Communication in WEB-browsers (rtcweb)

Justin Uberti <juberti@google.com> Wed, 24 February 2021 21:44 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 08E663A1D4E for <rtcweb@ietfa.amsl.com>; Wed, 24 Feb 2021 13:44:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable 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 Df58oclCkz2J for <rtcweb@ietfa.amsl.com>; Wed, 24 Feb 2021 13:44:50 -0800 (PST)
Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 089983A1CB8 for <rtcweb@ietf.org>; Wed, 24 Feb 2021 13:44:36 -0800 (PST)
Received: by mail-yb1-xb2f.google.com with SMTP id c131so3342869ybf.7 for <rtcweb@ietf.org>; Wed, 24 Feb 2021 13:44:35 -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=PaAmQFLOMq4nPFGLPEGWI0dIygQfmrZ4UdnXGi8YX3U=; b=bfgygbGjTsE8VA9vnxQM6qlA5P9sp6SPIZ9Ujcvy1d+1OgEt3uzshzqp8cDk7NWlWS 4zwZ6IJit1yd5sJ1nmqDIginDjIuQYFuRWXaaK4AE7z+YEFejoohdqQKfyeaPpMR2YBx /6CXT9aZc/m59TmabA5WS5RfacAr1MjmNiTB0ufvRc1mYTwES5ad30ABmCAt8jnSRwbE ni1PnWvebza+VRhQCPcKgvgdbULrL6eigF2qcyUKOupE83WJK5zHlqmhJ/qE2e4dzfPb M6f5wCX4ilkNt+B20c+qW8mo6EknSwFYvc729laohLbEbkbDTdwOn2VsXb8jf9oPD0Zv 4afA==
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=PaAmQFLOMq4nPFGLPEGWI0dIygQfmrZ4UdnXGi8YX3U=; b=a5SdvDeQBbBofrRe69YJgAgYPHxhZFmfJL+3MppfUO5lwVAnYkOwvNavqjykGHtFSX ASitlhywAOhLPteNOvz7hM1tGFT9kfbOkGlMbFFWgZ6H9nRKNGKpVsa/1mn5fY2tLxZp kRMrhCOWUBaxHY7PrlU1WqrpK9fuUKgHuPkWWeV04qeCYfnAGvpKtJ9Zv1rxcqeAjLkQ umba0IpSSoo/vmlIGQE/trxUxmPb6Iw5Joakaq8I1KLigY9vmfwTto+7d98OoxWr8iTI M2p85ZT7Nm6+MhxkGacxJJqQKHzxWUNTyUXbKuFxNLFq53xuKQrti/ICpiS4r/2k82+1 MDcA==
X-Gm-Message-State: AOAM533B+mmS73eEukk7oggri0Lv9wQpgXSs3emBNuU5OwcFZulZ8oYP H+iTYhiDrRAXCF5xIVNO1MbJmCgjScFjO/7ty/BWaw==
X-Google-Smtp-Source: ABdhPJy/1V2c7YQlF69NuZDn1GjWjCXiBoE/fd3jCt8h10qShzFJNihAevQY7GqqQhwOvI3GvG9cVYKYx9ZMxTTAteY=
X-Received: by 2002:a25:e4c5:: with SMTP id b188mr49758035ybh.235.1614203074759; Wed, 24 Feb 2021 13:44:34 -0800 (PST)
MIME-Version: 1.0
References: <161375655330.29021.8215379109983130364@ietfa.amsl.com> <CA+9kkMCEmVsVj2cfabV-L03Rt_RWrboRGime4ebv=9KTS=EnUA@mail.gmail.com> <AM0PR07MB38604A4C86EF63AC017596FE93839@AM0PR07MB3860.eurprd07.prod.outlook.com> <CAD5OKxvksjRghr6gT_7-zRsY8E4WBS-PM1JdgOP0D3p8bYN+AQ@mail.gmail.com> <VI1PR07MB38715CF957088531DBCD7F4193839@VI1PR07MB3871.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR07MB38715CF957088531DBCD7F4193839@VI1PR07MB3871.eurprd07.prod.outlook.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 24 Feb 2021 13:44:23 -0800
Message-ID: <CAOJ7v-0eOBt0zr_7tsaL+En1w7SGuuH67_aA39bbBOQNsgm3Vw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>
Cc: Roman Shpount <roman@telurix.com>, RTCWeb IETF <rtcweb@ietf.org>, "rtcweb-chairs@ietf.org" <rtcweb-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000de445505bc1bf08b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/FycGiE6a3UJvYWaO63WspjLDCUk>
Subject: Re: [rtcweb] WG Action: Rechartered Real-Time Communication in WEB-browsers (rtcweb)
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: Wed, 24 Feb 2021 21:44:59 -0000

Here's an initial set of slides that I put together the other day, still a
few ??? to address:
https://docs.google.com/presentation/d/1aprC-TwmLI_zGdWgnTdKVYvaqXNkcf9eMgMhAIzv8Ek/edit?usp=sharing&resourcekey=0-8HY7ugai8XnQyH4sA8cQdAcQdA.
Please have a look and feel free to leave comments in the preso.

On Sat, Feb 20, 2021 at 1:53 PM Christer Holmberg <christer.holmberg=
40ericsson.com@dmarc.ietf.org> wrote:

> Hi Roman,
>
>
>
> >You are probably the most qualified to do so. Let me know if you need
> any help regarding the current implementation status or backward interop
> testing.
>
>
>
> I don’t have much information, so feel free to send me whatever you have :)
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
>
> On Sat, Feb 20, 2021 at 1:25 PM Christer Holmberg <christer.holmberg=
> 40ericsson.com@dmarc.ietf.org> wrote:
>
> Hi,
>
>
>
> I could present the JSEP/BUNDLE specification misalignment, unless someone
> else wants to.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
> *From:* rtcweb <rtcweb-bounces@ietf.org> *On Behalf Of *Ted Hardie
> *Sent:* perjantai 19. helmikuuta 2021 20.11
> *To:* RTCWeb IETF <rtcweb@ietf.org>
> *Cc:* rtcweb-chairs@ietf.org
> *Subject:* Re: [rtcweb] WG Action: Rechartered Real-Time Communication in
> WEB-browsers (rtcweb)
>
>
>
> And we're back.
>
>
>
> This is hopefully for a limited engagement, as the charter is quite
> pointed on what we have to do.
>
>
>
> We do have a meeting slot at IETF 110, Friday March 12, 12:00 UTC (the
> first slot on the final day, in other words). The bulk of the time will be
> spent on the handling of "m=" sections that are designated as bundle-only.
> If you want to present on this, please send a note to the WG as soon as
> possible.  If you have some other agenda item, please let Sean and me know,
> and we'll discuss it with you.
>
>
>
> thanks,
>
>
>
> Ted and Sean
>
>
>
>
>
> On Fri, Feb 19, 2021 at 9:42 AM The IESG <iesg-secretary@ietf.org> wrote:
>
> The Real-Time Communication in WEB-browsers (rtcweb) WG in the Applications
> and Real-Time Area of the IETF has been rechartered. For additional
> information, please contact the Area Directors or the WG Chairs.
>
> Real-Time Communication in WEB-browsers (rtcweb)
> -----------------------------------------------------------------------
> Current status: Proposed WG
>
> Chairs:
>   Sean Turner <sean+ietf@sn3rd.com>
>   Ted Hardie <ted.ietf@gmail.com>
>
> Assigned Area Director:
>   Murray Kucherawy <superuser@gmail.com>
>
> Applications and Real-Time Area Directors:
>   Barry Leiba <barryleiba@computer.org>
>   Murray Kucherawy <superuser@gmail.com>
>
> Mailing list:
>   Address: rtcweb@ietf.org
>   To subscribe: https://www.ietf.org/mailman/listinfo/rtcweb
>   Archive: https://mailarchive.ietf.org/arch/browse/rtcweb/
>
> Group page: https://datatracker.ietf.org/group/rtcweb/
>
> Charter: https://datatracker.ietf.org/doc/charter-ietf-rtcweb/
>
> The RTCWEB working group was originally chartered to standardize mechanisms
> that provide direct interactive rich communication using audio, video,
> collaboration, games, etc. between two peers' web-browsers, without
> requiring
> non-standard extensions or proprietary plug-ins.  The result was a set of
> RFCs from RTCWEB, in addition to many other RFCs from other working groups,
> all of which are interrelated and had to be published together in what the
> RFC Editor refers to as a “cluster”.  In the end, that cluster comprised
> more
> than 40 RFCs and was finally published in January 2021.
>
> During the run-up to publication of the cluster, a contradiction was
> identified between what became RFCs 8829 and 8843.  A description of this
> contradiction was added to both documents to highlight the problem, and
> state
> our intention to proceed with publication but quickly initiate an effort to
> publish updates to the affected documents.
>
> The key part of the added text was as follows:
>
> “The specific issue involves the handling of "m=" sections that are
> designated as bundle-only, as discussed in Section 4.1.1 of [RFC 8829].
> Currently, there is divergence between JSEP and BUNDLE, as well as between
> these specifications and existing browser implementations …”
>
> The working group is being reconstituted to take up this contradiction,
> come
> to consensus on a resolution, and issue Standards Track updates for those
> two
> documents.  Specifically, the goal of this work is to address only the
> contradictions regarding "bundle-only" between BUNDLE and JSEP.  The
> resulting aligned solution should avoid impacting the interoperability with
> SDP Offer/Answer.  Finally, the impact on existing implementations that are
> affected by any change is to be considered.
>
> draft-ietf-rtcweb-sdp, which has not yet been published, will be returned
> to
> the working group to be updated according to the resolution of the issue
> described above.  The working group will therefore produce updates to the
> JSEP and BUNDLE documents, and re-submit draft-ietf-rtcweb-sdp for
> publication after it has been revised.  Updating any other document, or
> taking up any other issue, is out of scope and will require IESG approval
> via
> rechartering.
>
> Coordination with the MMUSIC working group to develop this solution will be
> required.
>
> Milestones:
>
>   Aug 2021 - Update to draft-ietf-rtcweb-sdp to the IESG as Informational.
>
>   Aug 2021 - Updates to the JSEP and BUNDLE documents to the IESG as
> Proposed
>   Standard.
>
> _______________________________________________
> 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
>