Re: [MMUSIC] 10 BUNDLE questions: If the BUNDLE mids in the answer doesn't match the BUNDLE mids in the offer, what happens?

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 25 April 2013 11:16 UTC

Return-Path: <christer.holmberg@ericsson.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 555A621F9350 for <mmusic@ietfa.amsl.com>; Thu, 25 Apr 2013 04:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.117
X-Spam-Level:
X-Spam-Status: No, score=-6.117 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZetlsSgUHsyy for <mmusic@ietfa.amsl.com>; Thu, 25 Apr 2013 04:16:31 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5153421F84E2 for <mmusic@ietf.org>; Thu, 25 Apr 2013 04:16:31 -0700 (PDT)
X-AuditID: c1b4fb30-b7f266d000000cb5-f5-5179108e564b
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 36.A2.03253.E8019715; Thu, 25 Apr 2013 13:16:30 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.02.0328.009; Thu, 25 Apr 2013 13:16:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] 10 BUNDLE questions: If the BUNDLE mids in the answer doesn't match the BUNDLE mids in the offer, what happens?
Thread-Index: Ac5BpI+q5+GuQrBOQqWqGu5HQN4kLQ==
Date: Thu, 25 Apr 2013 11:16:29 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C35F204@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDLMWRmVeSWpSXmKPExsUyM+JvrW6fQGWgwbYzshZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxuIzHawFX7grHv3JbWA8w93FyMkhIWAiseT2ZTYIW0ziwr31 QDYXh5DAYUaJdQ9XsEM4SxglNj9+DORwcLAJWEh0/9MGaRARUJf4ureHGaRGWKCdUaLvwBsm iEQHo0TrZCcIW0/ix9RFLCA2i4CqRNOJN4wgNq+Ar8Sy64uYQWxGoM3fT60B62UWEJe49WQ+ E8RFAhJL9pxnhrBFJV4+/scKYStKXJ2+nAnkHmYBTYn1u/QhWhUlpnQ/ZIcYLyhxcuYTlgmM wrOQTJ2F0DELSccsJB0LGFlWMbLnJmbmpJebb2IEhvDBLb8NdjBuui92iFGag0VJnFeOrTJQ SCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dUA6NAxBcBDp7nSy+X6M9dyLZT7GJre9yctTaGBfPi 7Dz4LTa1Nay0flPLt293c+h9Y7XEfWz58j/fVDOeMJy7Nf3HT3vBbdfbHjNKam7XV1b7NLEr feqb1COL0uckPn0+g5FVKF3gbkJAjeaJTXr+Ckb1qvfuc+/Y9ngC78HAxht3Y1/dyTNUf6zE UpyRaKjFXFScCACTlz01LwIAAA==
Subject: Re: [MMUSIC] 10 BUNDLE questions: If the BUNDLE mids in the answer doesn't match the BUNDLE mids in the offer, what happens?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Apr 2013 11:16:32 -0000

Hi,

>7. If the BUNDLE mids in the answer doesn't match the BUNDLE mids in the offer, what happens?

Conclusion: As people have been indicated, it would violate the rules in section 9.1 of RFC 5888 (see below), so it is considered a failure.

   "The "mid" attribute is an identifier for a particular media stream.
   Therefore, the "mid" value in the offer MUST be the same as the "mid"
   value in the answer."

Paul asked whether we need to say something about what the offerer should do in this case. But, personally I think it is implementation issue. RFC 5888 does not say how to handle these kind of cases either, so...

Also keep in mind that BUNDLE is a generic mechanism, but if W3C wants to describe what a browser shall do in this case, that's a separate story.

Draft impact: I suggest to add a note saying that, as defined in RFC 5888, the mid values in the SDP answer are required to match the values in the associated SDP offer.

Please indicate if you OBJECT to the conclusion, and/or if you DO NOT think we need to say anything about this in the draft.

Regards,

Christer