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

Justin Uberti <juberti@google.com> Thu, 28 January 2021 20:16 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 79F953A16EC for <mmusic@ietfa.amsl.com>; Thu, 28 Jan 2021 12:16:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.598
X-Spam-Level:
X-Spam-Status: No, score=-17.598 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, RCVD_IN_DNSWL_BLOCKED=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 c-t3ZkElBe9x for <mmusic@ietfa.amsl.com>; Thu, 28 Jan 2021 12:16:48 -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 59AE13A16F1 for <mmusic@ietf.org>; Thu, 28 Jan 2021 12:16:48 -0800 (PST)
Received: by mail-yb1-xb2f.google.com with SMTP id i141so6717592yba.0 for <mmusic@ietf.org>; Thu, 28 Jan 2021 12:16:48 -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=sEb8hf32KeeoJxjeOAugrmtzTIsNV7KHJlQSWV4FZlQ=; b=c+RZpjrYQzhoj6W03SZj5E/N/E5sLlVVpaHyVS2iDYNl4EATZslFanrR+ghw33HZgH ghqPq1HI/jck2FffSSTZukCw0g/FPyNL2CoTEIr5QoTnW65UzZZBsg3Bdw6Th5qq1mlV RL63nKMW1D9NF9VFpfpZ77vCC/br49OcBSz5F92G4ZHuGf9n3u4IeezW3HUFICrYHtSF NuXemvwp/Hrgje2yldbz2/8qbmEajOs1bJDiAnErka3bXELgl0WSeawB7UBuL2uU+Gsj 2f8AJMOB3gIKaeJdf5AfzT+1v5mOitU4IQGNnBK7bzrty1pGg2zwrk3Hga4JFVn0Kmi3 lFpQ==
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=sEb8hf32KeeoJxjeOAugrmtzTIsNV7KHJlQSWV4FZlQ=; b=S9WunDgKhZWvbCypUCuCYV3BsjzROVwRxqQST72j32Jn5OL4Hw7EQGGA5Zee6Zij7B xLSr7PPbgQPEdoSsP9BaE/T2Sew5HbWTV0FN3AO7h58woxa3EuJ0BfuA6a9RHLSXtJW3 VwMB1QiaarsTHPFjz06se6+yOUijN4q8i3oJTJJ33FUDmm8UG3AorcViO/+8u48Ysu/q p7Ljgz7xEA+eSBoV/STSQKFGJOXfAlN7PoDl7xhVmQUKwOTXBW4n9ox6OJg4ZGoGHnUr aznvtRHx843YY3a/KxBUYjULzBKexj8iAo2yCRiiZdQpiCkqbkPHVqznMm4kBVtOGIuK PS4g==
X-Gm-Message-State: AOAM533hxpBkkPOYOwiPeYnGZD8+an8Avv5yafHSNUp3xNkQm487DH3h fkfoNjA4ov5LPHLxI0MOguvjeM2eUOSApUbUfUSnIA==
X-Google-Smtp-Source: ABdhPJzJpbip+j0L0wi7Xp3vdAU+BKsIpV78kAV0bQIEI0l8Wq4Z/fhf5YlhkfG3YZMLVPgUk5X2A54szG7koA/Um/I=
X-Received: by 2002:a25:5007:: with SMTP id e7mr1424527ybb.46.1611865007086; Thu, 28 Jan 2021 12:16:47 -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> <CAL0qLwbS+6sN3FQVbJ3xsp2qxTGiBTbunTUvHXrT-nq+yiEaHA@mail.gmail.com> <CAD5OKxvDdLF8LbeUTxscKkYu7XVE8eg5eRMqg_TCeX73sVAKGg@mail.gmail.com> <CAOJ7v-1Cspakz79MHX2dEH9q+YGuWokUtzHTR4p1v=hvQmDHrw@mail.gmail.com> <AM0PR07MB3860F7E33547BE613D1ED9BE93BB0@AM0PR07MB3860.eurprd07.prod.outlook.com> <CAOJ7v-32i0xRuMVFmU4ioaVovh4JMyvXxy8a9MxUwMDz=ECwxQ@mail.gmail.com> <AM0PR07MB38603F2A77ABDE5BC4CEA4C493BB0@AM0PR07MB3860.eurprd07.prod.outlook.com> <CAOJ7v-3JPydV9SYkVxmari=hQ=TkFGn5_ox2w_oXb88RO_EXJQ@mail.gmail.com> <AM0PR07MB386077DF129D22FFD144914D93BA9@AM0PR07MB3860.eurprd07.prod.outlook.com> <CAOJ7v-05Fcew9f5Ti57dh_hOJqzhuPKnVgMsM4P3oTgJd1Q6Xg@mail.gmail.com> <AM0PR07MB38609D1FB2750749F95E3AF693BA9@AM0PR07MB3860.eurprd07.prod.outlook.com>
In-Reply-To: <AM0PR07MB38609D1FB2750749F95E3AF693BA9@AM0PR07MB3860.eurprd07.prod.outlook.com>
From: Justin Uberti <juberti@google.com>
Date: Thu, 28 Jan 2021 12:16:35 -0800
Message-ID: <CAOJ7v-0qLdjqdzGV7LKOy6o0Se0Rp2BgB9Zto+qkw-aovdBhZQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Roman Shpount <roman@telurix.com>, "Murray S. Kucherawy" <superuser@gmail.com>, Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002cb03305b9fb91eb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/4DxbhaDTu48atEehvOPic8CpiJw>
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: Thu, 28 Jan 2021 20:16:52 -0000

On Thu, Jan 28, 2021 at 12:09 PM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> ...
>
> >>> Look, I am as unhappy as anyone else that we have this issue to deal
> with. But this isn't an issue about what libwebrtc did or didn't do; this
> is an observation on the state of the WebRTC ecosystem in 2021. libwebrtc
> was unable to implement the standard
> >>> behavior 6 years ago because of application (not in libwebrtc!)
> incompatibilities when receiving port zero, and those incompatibilities
> have likely only multiplied over time. Ergo, we have to consider this
> situation as part of the problem space and resultant document update.
> >>
> >> So, what exactly were the issues with receiving port zero?
> >
> > The same as now - existing applications would suddenly treat this as a
> disabled m= section, when it previously worked fine.
>
> What do you mean by "previously"?
>
> Just to make sure I understand: if the application receives port zero +
> bundle-only, why does it treat is as a disabled m= section? Why doesn't it
> check the bundle-only attribute? I am just trying to understand what causes
> the problem...
>

Because applications exist that understand BUNDLE, but not port-zero with
a=bundle-only. So if one were to suddenly change the behavior of clients to
start using a=bundle-only, those applications would interpret these m=
sections as disabled. This is what I have been trying to say all along.