[MMUSIC] Can we use "a=bundle-only" in subsequent offers, instead of using a "shared address"?

Taylor Brandstetter <deadbeef@google.com> Wed, 08 February 2017 23:23 UTC

Return-Path: <deadbeef@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 8EAF412A0CC for <mmusic@ietfa.amsl.com>; Wed, 8 Feb 2017 15:23:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham 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 4NOu10XlxJAc for <mmusic@ietfa.amsl.com>; Wed, 8 Feb 2017 15:23:53 -0800 (PST)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (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 180CD129511 for <mmusic@ietf.org>; Wed, 8 Feb 2017 15:23:53 -0800 (PST)
Received: by mail-qt0-x235.google.com with SMTP id x49so180822813qtc.2 for <mmusic@ietf.org>; Wed, 08 Feb 2017 15:23:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=/tflwvr+071yrKQI2wwdeZXfdaaz29EY8s3BOVXqI+A=; b=totjWz0flVqO0jwJNghw21iP4bgi077iKvskzpXFRxcRnau4IlK/WuvJAD579EXfO8 kzRNfb5skz2IT9iHguUaSZl9x+VFpQl3DPzuGWFPn1V3xbxqexayQ1ZN6iRPaj6b4A9s eAtcIW/KGaror3My3wHyX5LT4l0pwP04HBzabloA4ksh8QNYqTYRB2gJD7Og+JDr9VoS wxEKK/0bVTPnCe/kP31m0u51mA41MbzcOUZKdFb/pr0fVNWLxvmMuM+JqVrX6zZFgyxz ewa+hwgR9rYPdUPkR4OLuuzhV3u9JDLrAnVa2qWMklcjmVEfXv/JEoVttSJtjAcKS/eH fRow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/tflwvr+071yrKQI2wwdeZXfdaaz29EY8s3BOVXqI+A=; b=E8F4QZz9q+ZEsNWVvVQ5pRTqPQr9GtGSQFJkqV5U1D2Qo3fyBX5C57GnOe6ys5bV9D /MSAOVGalZDRr1rmSLWXPqdhD/bUwoT95Ml3VI2JPG+Vdb3FBUggPH36foeeZ9GiWA9P +0733Kwh/hKPF5GIaC33JINHQ7tuenQRxbzLhc1OOGItaHl96j8D4ZDV2a9/kc2qIXrS Dn+ikkLpW3nYGRy/ZHl4yLqFQH7/ytG+lususzwLzVMIiH+O0Qrpl+vOELpcuPz1rG8f kbZWXGZhWmoArwPVLJhMPmdtrltRT3IFTOmBaafdxlhlezLYrYJUYkIJ3e9x1ZjHfO99 Dm9A==
X-Gm-Message-State: AMke39lmZ6YdqNW/yaFN3ipyy4W1h1Hm1g198+FHitVjEwdTki/9zk+jgUXKNv8NS24Jx0HwjwYNnwyQhl6NsORC
X-Received: by 10.200.48.172 with SMTP id v41mr112500qta.54.1486596231905; Wed, 08 Feb 2017 15:23:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.200.38.188 with HTTP; Wed, 8 Feb 2017 15:23:51 -0800 (PST)
From: Taylor Brandstetter <deadbeef@google.com>
Date: Wed, 08 Feb 2017 15:23:51 -0800
Message-ID: <CAK35n0bys1EUwoJtvok2Qjcg7bqK4hQx1HhwbnKSHZw2TuAPLA@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a113a14d05402b105480d281d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/-jENmu4iaapy7NdJ9_SLHpNjSDc>
Subject: [MMUSIC] Can we use "a=bundle-only" in subsequent offers, instead of using a "shared address"?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 08 Feb 2017 23:23:54 -0000

In an initial offer, if we want to communicate "this 'm=' section must be
either bundled or rejected", that's accomplished with "a=bundle-only":

a=group:BUNDLE A B
m=audio 10000 ...
a=mid:A
...
m=video 0 ...
a=mid:B
a=bundle-only

In subsequent offers, this is accomplished by duplicating the IP
address/port (see section 8.3.3):

a=group:BUNDLE A B
m=audio 10000 ...
a=mid:A
...
m=video 10000 ...
a=mid:B

Is this initial vs. subsequent offer difference necessary? Both blobs of
SDP are communicating the same information, so the "shared address" rules
seem to only add complexity.

Also, the approach of using a "shared address" to communicate something
isn't extensible to protocols that don't use an address for identification,
like ICE. We'd need to define additional rules for those cases, or allow
them specifically to use "a=bundle-only" in subsequent offers.