[MMUSIC] BUNDLE TEXT: Answerer Procedures (29th May)

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 29 May 2013 11:40 UTC

Return-Path: <prvs=58610ee6a3=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 7FA7921F9408 for <mmusic@ietfa.amsl.com>; Wed, 29 May 2013 04:40:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.644
X-Spam-Level:
X-Spam-Status: No, score=-5.644 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6, 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 lY3z-EoYE6ZM for <mmusic@ietfa.amsl.com>; Wed, 29 May 2013 04:39:58 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5D39921F93EF for <mmusic@ietf.org>; Wed, 29 May 2013 04:39:57 -0700 (PDT)
X-AuditID: c1b4fb30-b7f9e6d000002643-be-51a5e90bbae5
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 3F.6C.09795.B09E5A15; Wed, 29 May 2013 13:39:56 +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; Wed, 29 May 2013 13:39:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE TEXT: Answerer Procedures (29th May)
Thread-Index: Ac5cYL6Xjkqad1ozQWuoyGt6QctbSA==
Date: Wed, 29 May 2013 11:39:54 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C37B973@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.17]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C37B973ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDLMWRmVeSWpSXmKPExsUyM+JvrS7Py6WBBnumc1lMXf6YxYHRY8mS n0wBjFHcNkmJJWXBmel5+nYJ3Bl7/ixnLZhxgLFi0XGVBsbjKxm7GDk5JARMJC4v2MsOYYtJ XLi3nq2LkYtDSOAwo8SVI3tZIJwljBJv/7UDZTg42AQsJLr/aYM0iAioS3zd28MMYgsDDeqa 8p0NIm4pcfnmMxYIW0/iwKqrYDaLgKrElAc/WUFsXgFfiTMrToLFGYEWfz+1hgnEZhYQl7j1 ZD4TxEECEkv2nGeGsEUlXj7+xwpygoSAosTyfjmI8nyJ7j0XoUYKSpyc+YRlAqPQLCSTZiEp m4WkDCKuI7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9iZM9NzMxJLzffxAgM/INbfhvsYNx0 X+wQozQHi5I4rz7v4kAhgfTEktTs1NSC1KL4otKc1OJDjEwcnCCCS6qBUcj4/dztkkLdTxov rbsXVWu7OvaVuKqldUpszbdqzW9az54KL/6p8NPp0rb1TLs87t2Y8FDyk/Qv5c3TNv6wfaGf Y8/NybGMd8GEC2c2uS+YxuGiLvs3vndRQofRlQTGs1a7XOdz1retK3lb9WzlHJat+ku+bgrY MmdtqLxSz5N7hyxu5wnZpiuxFGckGmoxFxUnAgBybWSfTwIAAA==
Subject: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29th May)
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: Wed, 29 May 2013 11:40:04 -0000

Hi,

Based on the e-mail and interim discussions, I've tried together some "Answerer Procedures" text for BUNDLE.

For now, I would request that people mainly focus on the technical stuff, and if some text is unclear. I WILL align the usage of "m=" line and "media description" :)

Also note that examples will be added later.

Regards,

Christer

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


6.4.  Answerer Procedures

6.4.1.  General

   This section describes how an Answerer, when it receives an SDP Offer
   including a BUNDLE group, generates the associated SDP Answer.

   When an Answerer receives an SDP Offer which includes a BUNDLE group,
   and the Answerer accepts the offered BUNDLE group, the Answerer MUST
   generate an SDP Answer according to the procedures in Section 6.1 and
   this section.

6.4.2.  RFC 5888 restrictions

   Based on the rules and procedures in RFC 5888, the following
   restrictions also apply to BUNDLE groups in SDP Answers:

   o  1) A BUNDLE group must not be added to an SDP Answer, unless the
      same BUNDLE group was included in the associated SDP Offer; and

   o  2) An SDP "m=" line must not be added to a BUNDLE group in the SDP
      Answer, unless it in the associated SDP Offer was included in the
      same BUNDLE group.

6.4.3.  Offerer Bundle Address Selection

   In the SDP Answer, the Answerer selects the bundle address for the
   Offerer, based on the address information received in the associated
   SDP Offer, using the mid value.  The mid value associated with the
   "m=" line in the SDP Offer that represents the bundle address MUST in
   the SDP Answer be located first in the mid value list added to SDP
   group:BUNDLE attribute associated with the BUNDLE group.

   From the associated SDP Offer, the Answerer SHOULD choose the bundle
   address associated with the mid value located first in the mid value
   list included in the SDP group:BUNDLE attribute associated with the
   BUNDLE group, unless:

   o  1) The mid value represents an "m=" line with a port zero value in
      the SDP Offer; or

   o  2) The mid value represents an "m=" line with a port zero value in
      the SDP Answer.

   OPEN: The decision for allowing a media description with port zero
   values inside a BUNDLE group is pending on update for RFC 5888.

6.4.4.  Answerer Bundle Address Selection

   In the SDP Answer, the Answerer selects its local bundle address.
   Each "m=" line included in a BUNDLE group MUST contain identical
   address information.  The only exception is the usage of a zero port
   value for an "m=" line, which is allowed eventhough another port
   value number is used for other "m=" lines in the BUNDLE group.

   OPEN: The decision for allowing a media description with port zero
   values inside a BUNDLE group is pending on update for RFC 5888.

   In a subsequent SDP Answer, the Answerer MAY change its local bundle
   address, as long as each "m=" line included the BUNDLE group contain
   identical address information.

   For a given BUNDLE group, the Answerer MUST NOT assign the bundle
   address to "m=" lines that are not included the BUNDLE group, or to
   "m=" lines that are included in another BUNDLE group.

6.4.5.  Rejecting A BUNDLE Media Description

   When generating the SDP Answer, if the Answerer wants to reject media
   associated with an "m=" line in the BUNDLE group, it will add a zero
   port number value to the "m=" line, according to the procedures
   defined in RFC 3264.

   OPEN ISSUE: It is FFS whether it is allowed to include a port zero
   media descriptions in a BUNDLE group.

6.4.6.  Removing a media description from a BUNDLE group

   When generating the SDP Answer, if the Answerer wants to remove an
   "m=" line from a BUNDLE group (without rejecting the "m=" line),it
   MUST NOT include the "m=" line in a BUNDLE group.  In addition, the
   SDP Answer MUST not add its local bundle address to the "m=" line.

   An Answerer MUST NOT, in the SDP Answer, remove an "m=" line from a
   BUNDLE group, unless the "m=" line had unique address information in
   the associated SDP Offer.

   NOTE: The reason for the restriction above is that, if the "m=" line
   would be removed from the BUNDLE group, the address information would
   be identical to the "m=" lines remaining in the BUNDLE group.

   OPEN: The decision for allowing a media description with port zero
   values inside a BUNDLE group is pending on update for RFC 5888.