Re: [MMUSIC] comments on draft-ietf-mmusic-sdp-bundle-negotiation-05 - Paul's comments 20131027 - Section 6.4.3

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 05 December 2013 11:55 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 487E01ADF7D for <mmusic@ietfa.amsl.com>; Thu, 5 Dec 2013 03:55:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
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 mIxkoYC9s1cb for <mmusic@ietfa.amsl.com>; Thu, 5 Dec 2013 03:55:08 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 320B91ADF79 for <mmusic@ietf.org>; Thu, 5 Dec 2013 03:55:07 -0800 (PST)
X-AuditID: c1b4fb32-b7f388e0000057e0-eb-52a06997f667
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.125]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id C7.C4.22496.79960A25; Thu, 5 Dec 2013 12:55:03 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.73]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0347.000; Thu, 5 Dec 2013 12:55:03 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: 'Paul Kyzivat' <pkyzivat@alum.mit.edu>
Thread-Topic: comments on draft-ietf-mmusic-sdp-bundle-negotiation-05 - Paul's comments 20131027 - Section 6.4.3
Thread-Index: Ac7xsM5j3Tyf3U3cQ+m6qr6hn1HjnA==
Date: Thu, 05 Dec 2013 11:55:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C56CEF0@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUyM+Jvre70zAVBBstmmlpMXf6YxWLFhgOs Dkwef99/YPJYsuQnUwBTFJdNSmpOZllqkb5dAlfGlct3GAt+qVasWF/ZwNgk28XIySEhYCIx cc1CJghbTOLCvfVsXYxcHEICJxglrvXeh3IWMUocX7CItYuRg4NNwEKi+582SIOIgJbEgSuX WUDCzAJqEo+uG4KEhQUKJX4tm8ICUVIkcfXOTXaQEhEBPYln7TUgYRYBFYnOW8fYQWxeAV+J Za2f2EBsRqATvp9aA3YOs4C4xK0n86FOE5BYsuc8M4QtKvHy8T9WCFtR4ur05VD1OhILdkPM YRbQlli28DUzxHxBiZMzn7BMYBSZhWTsLCQts5C0zELSsoCRZRWjZHFqcXFuupGBXm56bole alFmcnFxfp5eceomRmBEHNzy22gH48k99ocYpTlYlMR5r7PWBAkJpCeWpGanphakFsUXleak Fh9iZOLglGpgjJiwJMzu14s3ExjYfXWjhNSFL1qxMm6bcqnn+wL/ZzbS2gck5ROKmdb0d2zw 6Fj7tG4aQ2hA1KV7LwNZX8yKnCj2RPa15ZdXk7UEchL+hT779fvK/0UnJMXKHdT+28epP/OZ srKl2qdVgKdyrWvTkZ2PmZ+GnjgfXteX4/lWyHj1pkuHZexuKrEUZyQaajEXFScCAInbP11W AgAA
Cc: 'IETF MMUSIC WG' <mmusic@ietf.org>
Subject: Re: [MMUSIC] comments on draft-ietf-mmusic-sdp-bundle-negotiation-05 - Paul's comments 20131027 - Section 6.4.3
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Dec 2013 11:55:10 -0000

Hi Paul,

I am working on a new version of BUNDLE, so I took a closer look at your comments on -05. I will address them in separate e-mails.

I GUESS we should allow it, at least in the initial Offer, in case the Answerer doesn't support BUNDLE. But, in the BAS Offer I guess we should either say that it is not used, that the value MUST be identical to the RTP port, or that the value doesn't matter.

----------------------------

> Section 6.4.3 says:
>
>    When an Offerer receives an Answer, in which an offered BUNDLE group
>    is accepted, if the Offerer in the associated Offer assigned an
>    address (unique or shared), that does not represent the BUNDLE
>    address selected for the Offerer, to an "m=" line within the BUNDLE
>    group, the Offerer MUST send a subsequent Offer, in which it assigns
>    the BUNDLE address selected for the Offerer to each "m=" line within
>    the BUNDLE group.  This procedure is referred to as Bundle Address
>    Synchronization (BAS), and the Offer is referred to as a BAS Offer.
>
> I tried to parse it below. To do so, I had to move "that does not represent the BUNDLE address selected for the Offerer,".
>
>   When an Offerer receives an Answer,
>     in which an offered BUNDLE group is accepted,
>        if the Offerer in the associated Offer assigned an address
>        (unique or shared), to an "m=" line within the BUNDLE group,
>           that does not represent the BUNDLE address selected for the
>           Offerer,
>
>    the Offerer MUST send a subsequent Offer, in which it assigns
>    the BUNDLE address selected for the Offerer to each "m=" line within
>    the BUNDLE group.  This procedure is referred to as Bundle Address
>    Synchronization (BAS), and the Offer is referred to as a BAS Offer.
>
> Even so, it still doesn't quite make sense to me. The problem is with "selected for the Offerer". IIUC it would state that as "selected by the Answerer".
>
> And in any case I'm not sure if I then have the intended interpretation.
>
> I *think* the condition you are trying to describe is:
>
> - offer included bundle group
> - answer accepted bundle group
> - M is the first mid in the bundle group in the answer
> - A is the media address of the m-line in the offer that
>   has mid M
> - some m-line in offered bundle group that was accepted in the answer
>   doesn't have media address A
>
> If that is what you are trying to say, then we just have to figure out how to say it intelligibly. I think trying to string it out into a sentence is not going to work, and so you need to break it down something like I did above.

I replied to this earlier, but I'll modify my reply a bit.

The mid has nothing to do with whether a BAS Offer needs to be sent or not. The Answerer will indicate which mid value represents the determined BUNDLE address, and it doesn't matter if that is not the same address as the Offerer requested to become its BUNDLE address.

The only thing which matters is whether the Offer contained addresses that are different from the determined BUNDLE address (in the initial Offer that will always be the case, as each address with a non-zero port value must be unique).

Never the less, I still tried to make the text more clear:

------------

6.4.3.  Bundle Address Synchronization (BAS)

   When an Offerer receives an Answer, in which an offered BUNDLE group
   has been accepted by the Answerer, it checks the following criteria:

   o  In the Offer the Offerer assigned an address (unique or shared) to
      one or more "m=" lines within the BUNDLE group, that is different
      than the BUNDLE address determined by the Answerer Section 6.4.2.

   If the criteria is fulfilled, the Offerer MUST send a subsequent
   Offer, in which it assigns the BUNDLE address to each "m=" line
   within the BUNDLE group.  This procedure is referred to as Bundle
   Address Synchronization (BAS), and the Offer is referred to as a BAS
   Offer.

   The Offerer MAY modify any SDP parameter in a BAS Offer.

   NOTE: It is important that the BAS Offer gets accepted by the
   Answerer.  For that reason the Offerer needs to consider the
   necessity to modify SDP parameters that could get the Answerer to
   reject the BAS Offer.  Removing "m=" lines, or reducing the number of
   codecs, in the BAS Offer used for the is considered to have a low
   risk of being rejected.

   NOTE: The main purpose of the BAS Offer is to make sure that
   intermediaries, that might not support the BUNDLE mechanism, have
   correct information regarding which address is going to be used for
   the bundled media.

   Section 12.1 shows an example of an BAS Offer.

----------------------------

Regards,

Christer