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

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 29 May 2013 14:23 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 0E39221F9121 for <mmusic@ietfa.amsl.com>; Wed, 29 May 2013 07:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Level:
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[AWL=-0.063, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_56=0.6, RDNS_NONE=0.1]
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 TewMZ-o3vGEN for <mmusic@ietfa.amsl.com>; Wed, 29 May 2013 07:23:20 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id DDA9421F9060 for <mmusic@ietf.org>; Wed, 29 May 2013 07:23:14 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta12.westchester.pa.mail.comcast.net with comcast id hpF51l0040bG4ec5CqPEWE; Wed, 29 May 2013 14:23:14 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta03.westchester.pa.mail.comcast.net with comcast id hqPD1l0103ZTu2S3PqPDym; Wed, 29 May 2013 14:23:14 +0000
Message-ID: <51A60F50.9020902@alum.mit.edu>
Date: Wed, 29 May 2013 10:23:12 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C37B973@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C37B973@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369837394; bh=QauSHbfJp9oEHNEA77uWYWB/H1kCbZKb9/BCGVnmxOk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=TP+9wEx3Hd9jRjL5ElTGuMF+ctj+kKtDMPDdN5gS8IqmBnkjEAvUa7lgoVmtfZFK7 miimvzW4dhllNIHtyklg/t/aJTT8yzWY/U/P/6nFoBjg86zexkcm8zc2sSPxPKS9yE ITvYHwKJb67Zl3r+PKey6E5FqvUnwX7LhwdzZUAN08xgmewxmA07F0x9jgH4rp74CU 0kyPaX2ntjMsJDsYXWJ48CU4yq9v4uo8+gHuvP+Rbf/nn/aKfGdshhvbvML0ipgxM3 rSNkT56DnrPRqyO0xqN5eiuFEOgGcvtDm6ysAhTjQUE8yJL37p+GCzAQdBt0hJy9vd Y1ChmMZmHyeOw==
Subject: Re: [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 14:23:29 -0000

Christer,

This seems good to me, pending polishing the language.

I trust when you say "address information" you mean:
- the port in the m-line
- the address in the c-line
- associated ICE information

Obviously it would be cumbersome to mention all of that each time you 
need to refer to address information. So I'm expecting you will coin a 
term (e.g., "address information") and provide a definition of it.

	Thanks,
	Paul

On 5/29/13 7:39 AM, Christer Holmberg wrote:
> 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.
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>