Re: [MMUSIC] [rtcweb] Updating JSEP and BUNDLE

Justin Uberti <juberti@google.com> Tue, 26 January 2021 19:43 UTC

Return-Path: <juberti@google.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE833A0DF4 for <mmusic@ietfa.amsl.com>; Tue, 26 Jan 2021 11:43:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.699
X-Spam-Level:
X-Spam-Status: No, score=-15.699 tagged_above=-999 required=5 tests=[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 8JYV23PEo5u3 for <mmusic@ietfa.amsl.com>; Tue, 26 Jan 2021 11:43:50 -0800 (PST)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 362FB3A0DF0 for <mmusic@ietf.org>; Tue, 26 Jan 2021 11:43:50 -0800 (PST)
Received: by mail-io1-xd2f.google.com with SMTP id y19so36086525iov.2 for <mmusic@ietf.org>; Tue, 26 Jan 2021 11:43:50 -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=45NGKJuodKugNAhSXRMYY6fg03jVcSa238yUyKLnEjo=; b=Q56GwmmlJ+b+4z5EGMMdTmICDxp+2fmdBaW8BPccqzBA4ZIc8i0hAAn3j69az2ZHq6 sesFqPkxhLk4AgEpkH3346vp6DP5696UufMvkIyqh5XKKgZVhw1D+8HoYOdxDjOF8NzT 61ywHaNEJXp1QhNdvmMPsLtlOlhQfk+pibS/HLLTM1jrY0gD81Ij9iE+W4+Bz2hGX3Ll IevnF8ZlVYwaLUiEb5Y6BR4NaJ0uAXhEwXivXpS+fv0Zxr1j+pDIpXHSMuqh9t4DfBn3 BgAn7vYRNB5DhwedRjlKKCIOvWyVQuVmRB3rictB8cGQ2UbHzyjfnSH/Msom48wVD4Zq A1Qg==
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=45NGKJuodKugNAhSXRMYY6fg03jVcSa238yUyKLnEjo=; b=jWt8EKty+JhA6jcGT15TTNKNRklxrdVQQn3V1wO6FURe+WukMwBMFIboqovoSdokQB qnAOtfIEecVNPQwAoByOvv9kYphCCc0p/BosMd96yPuEPXUPgWjHT40Dd3hw8IKlBI5K JwpDohtg1nLd68lgcVPbrABGttZ3/rJZHdj3lhYByQh9km//FHxE6VwJVfHQgf4rV0ba sFbgbPHhyPC6t0MCO8JETCraokp8uYbc8Ibs7pA0g9+QqSqThRW0sGMBBmpbNZWbrVKY ExGRnNzP9/Wf4zEmmPqzYRmeWKSwILqc4u1OXSaF15I859g5srqt6JjrY0u1Z2no4Loh qZXw==
X-Gm-Message-State: AOAM530xFUdiCdbzZSaM+W4mY5SCaX0sMutPtaxTQd8wDOf/yT9Z+r/k OMhi6yC/zhLSb6j/VpRTCuHtpHnfkwPa1f7d2POcQSnHC2244g==
X-Google-Smtp-Source: ABdhPJxcab3c4fNEs7gGVz7A7l0UvJZ7ZCn1qFbnluJEHD5wq4gcoljeoNtWh6BYUjDBGYm8u5aWyKeRW4NOuoiAgD0=
X-Received: by 2002:a02:6554:: with SMTP id u81mr6168946jab.116.1611690229133; Tue, 26 Jan 2021 11:43:49 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwYeg6_HdjVuLCdhPxtaNH4_vnE_r4Lr1p=s8uiTAu+hdQ@mail.gmail.com> <3259d26b0df271445895d17c73fdf60d94209c52.camel@ericsson.com> <61b30cc5-d56a-f83b-0faf-0df8b07aea0f@alvestrand.no> <f12469ff29408168c98124c46348804b5cbd86d2.camel@ericsson.com> <CAL0qLwakSYdoVm9fhMWuC9bM8tjUkLku4mM5Q4XgdGm2T9uevw@mail.gmail.com> <AM0PR07MB386064B544F18A38FD900EF593BC0@AM0PR07MB3860.eurprd07.prod.outlook.com> <CAOJ7v-0DvOjEocqxgiKr3n3iS7WZH-qkvgjUi7EOtZH=by5_BQ@mail.gmail.com> <AM0PR07MB3860CC1CD265F56932815A9A93BC0@AM0PR07MB3860.eurprd07.prod.outlook.com>
In-Reply-To: <AM0PR07MB3860CC1CD265F56932815A9A93BC0@AM0PR07MB3860.eurprd07.prod.outlook.com>
From: Justin Uberti <juberti@google.com>
Date: Tue, 26 Jan 2021 11:43:37 -0800
Message-ID: <CAOJ7v-1vgtyz5ivAs+RehAMfVSaFQAygFrvDg9FxaWa8Q_n-qw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000098f55e05b9d2dfc7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1ZOTqQWTWHANdtQ9Eml4Sj0xjZ0>
Subject: Re: [MMUSIC] [rtcweb] Updating JSEP and BUNDLE
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 19:43:55 -0000

On Tue, Jan 26, 2021 at 11:28 AM Christer Holmberg <christer.holmberg=
40ericsson.com@dmarc.ietf.org> wrote:

> Hi,
>
> ...
>
> >>> Secondly, I can definitely live with the work being done in a revivied
> >>> specifically charted RTCWeb WG. However, SDP Offer/Answer is used in
> several
> >>> places for different usages. Something which was considred very much
> when
> >>> developing BUNDLE. Thus, I think it is relevant that RTCWeb will keep
> MMUSIC
> >>> informed about their work. So that RTCWeb doesn't end up missing an
> important
> >>> aspect of this, a run into issue when forming the IETF consensus
> needed to
> >>> publish this document.
> >>
> >> I think the revised charter takes this into account.  Please let me
> know if it needs any other corrections.
> >
> > It needs to be clear that the charter is about fixing the misalignment
> between the BUNDLE and JSEP specifications - nothing more, nothing less.
> >
> > As noted in the spec blurb, we also need to consider the existing
> deployments and how any changes at this point may affect them. Specs that
> implementors can't implement are not useful.
>
> Absolutely. When we discuss how to solve the misalignment between the JSEP
> and BUNDLE specifications we need to take existing deployments into
> consideration.
>
> But, any issue that is not related to the misalignment between the JSEP
> and BUNDLE specifications shall be outside the scope.
>
> Agreed that we want to keep this narrowly focused. I believe the existing
blurbs added to JSEP and BUNDLE outline the scope well, in that we are
trying to solve a specific problem, but the solution space for said problem
may need to consider options beyond what JSEP and BUNDLE currently specify.

On that topic: to understand the importance of the BUNDLE v41 change
regarding answers and subsequent offers, does anyone recall the technical
reasons behind this change?