Re: [MMUSIC] BUNDLE: meaning of "unspecified" when describing "bundle-only"

Cullen Jennings <fluffy@iii.ca> Thu, 13 July 2017 18:25 UTC

Return-Path: <fluffy@iii.ca>
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 559CB12EB4A for <mmusic@ietfa.amsl.com>; Thu, 13 Jul 2017 11:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level:
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 m5-DBGDUPU7q for <mmusic@ietfa.amsl.com>; Thu, 13 Jul 2017 11:25:05 -0700 (PDT)
Received: from smtp122.iad3a.emailsrvr.com (smtp122.iad3a.emailsrvr.com [173.203.187.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5500A129B77 for <mmusic@ietf.org>; Thu, 13 Jul 2017 11:25:05 -0700 (PDT)
Received: from smtp32.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp32.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 0167A5AB5; Thu, 13 Jul 2017 14:24:56 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp32.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 88A0C5A04; Thu, 13 Jul 2017 14:24:56 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.55] (d172-219-247-164.abhsia.telus.net [172.219.247.164]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Thu, 13 Jul 2017 14:24:56 -0400
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <D58AB032.1F24F%christer.holmberg@ericsson.com>
Date: Thu, 13 Jul 2017 12:24:55 -0600
Cc: Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <129EFD55-0FB2-43A3-88C0-F759B5BED602@iii.ca>
References: <9e5fc493-bfba-1a27-149e-1f566a25b411@nostrum.com> <D49AAB4A.155D4%christer.holmberg@ericsson.com> <D58AB032.1F24F%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ZgNBLTVJJod2qtVVZv7-JHCVGfc>
Subject: Re: [MMUSIC] BUNDLE: meaning of "unspecified" when describing "bundle-only"
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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, 13 Jul 2017 18:25:07 -0000

That works for me. 

> On Jul 11, 2017, at 7:46 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
> Hi,
> 
> It took a while, but here is my suggestion (based on alternative #2):
> 
> OLD TEXT:
> 
> "The usage of the 'bundle-only' attribute is only defined for a
>   bundled "m=" line with a zero port value, within an offer.  Other
>   usage is unspecified."
> 
> 
> NEW TEXT:
> 
> "The usage of the 'bundle-only' attribute is only defined for a
>   bundled "m=" line with a zero port value, within an offer.  Other
>   usage is unspecified. If an implementation receives, within
> an offer or answer, a bundled "m=“ line with a non-zero port value
> 
> and an ‘bundle-only’ attribute associated with the “m=“ line, the
> implementation MUST ignore the attribute."
> 
> Regards,
> 
> Christer
> 
> 
> On 10/01/17 15:18, "mmusic on behalf of Christer Holmberg"
> <mmusic-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
> wrote:
> 
>> Hi Adam,
>> 
>> My suggestion would be alternative #2. Because, if an endpoint supports
>> the attribute it doesn¹t really matter what the port value is, so there is
>> no need to reject the m- line.
>> 
>> Regards,
>> 
>> Christer
>> 
>> 
>> On 29/12/16 23:15, "mmusic on behalf of Adam Roach"
>> <mmusic-bounces@ietf.org on behalf of adam@nostrum.com> wrote:
>> 
>>> We've recently come across an issue with the way the "bundle-only"
>>> attribute is described in the current document. The current language
>>> regarding port handling reads:
>>> 
>>>   The usage of the 'bundle-only' attribute is only defined for a
>>>   bundled "m=" line with a zero port value, within an offer. Other
>>>   usage is unspecified.
>>> 
>>> Usually, when we have this kind of language, we still ensure that
>>> behavior is well defined, to help avoid unnecessary interop failures. I
>>> see a couple of different options here:
>>> 
>>> 1. Remove the final sentence and add language saying that creators of
>>>   SDP MUST NOT include a "bundle-only" attribute in an m-section that
>>>   has a non-zero port, and that recipients of such SDP {SHOULD,MUST}
>>>   reject it; or
>>> 
>>> 2. Retain language saying that including a "bundle-only" attribute in a
>>>   non-zero m-section is unspecified, but add normative language along
>>>   the lines of: "implementations that receive an m-section with a
>>>   non-zero port that also contains a 'bundle-only' attribute MUST
>>>   ignore the {attribute,port}."
>>> 
>>> I don't have a preference between these choices, but I think we do need
>>> clarity. To be absolutely clear, this feedback is based on actual
>>> implementation interop failures in the field. This problem is not
>>> theoretical.
>>> 
>>> /a
>>> 
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>> 
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic