Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29th May)
Christer Holmberg <christer.holmberg@ericsson.com> Thu, 30 May 2013 08:27 UTC
Return-Path: <prvs=6862f8098b=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 3C00121F96CF for <mmusic@ietfa.amsl.com>; Thu, 30 May 2013 01:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.665
X-Spam-Level:
X-Spam-Status: No, score=-5.665 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 Lv0UyV1qSwc5 for <mmusic@ietfa.amsl.com>; Thu, 30 May 2013 01:27:52 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id D792B21F96FE for <mmusic@ietf.org>; Thu, 30 May 2013 01:27:05 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-b9-51a70d521693
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 77.A2.18006.25D07A15; Thu, 30 May 2013 10:26:59 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0328.009; Thu, 30 May 2013 10:26:58 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Kevin Dempsey <kevindempsey70@gmail.com>
Thread-Topic: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29th May)
Thread-Index: Ac5cYL6Xjkqad1ozQWuoyGt6QctbSAABoqcAACXMJdD///4KgP//3LxQ
Date: Thu, 30 May 2013 08:26:58 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C37D20A@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C37B973@ESESSMB209.ericsson.se> <51A60F50.9020902@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C37CFE4@ESESSMB209.ericsson.se> <CAMvTgccVOPVjxN7BoV7tYfcwrsUcUXx8LdcVrss2ZfmV-m7Xgg@mail.gmail.com>
In-Reply-To: <CAMvTgccVOPVjxN7BoV7tYfcwrsUcUXx8LdcVrss2ZfmV-m7Xgg@mail.gmail.com>
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: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrNLMWRmVeSWpSXmKPExsUyM+JvrW4w7/JAgwMdLBY3579lsZi6/DGL xYoNB1gdmD3+vv/A5LFz1l12jyVLfjIFMEdx2yQllpQFZ6bn6dslcGd0LdrJUvDWvGLrs062 Bsbd2l2MnBwSAiYSl7bcZYKwxSQu3FvP1sXIxSEkcJhRYmHPJyhnCaPEqgtzWLsYOTjYBCwk uv+BNYsI6EgcvD+ZHcRmFvCVeLngCzOILSzgKLH76hkmiBoniae/1rCDtIoIuEls+s8JEmYR UJXo+NXIAmLzArWuaJzEDLHqF6PEp3WbwBKcAoESq/qa2UBsRqDjvp9awwSxS1zi1pP5UEcL SCzZc54ZwhaVePn4H9iZEgKKEsv75SDK9SRuTJ3CBmFrSyxb+JoZYq+gxMmZT1gmMIrNQjJ1 FpKWWUhaZiFpWcDIsoqRPTcxMye93GgTIzBuDm75rbqD8c45kUOM0hwsSuK8eryLA4UE0hNL UrNTUwtSi+KLSnNSiw8xMnFwggguqQbGym9m3/WvHxcRDt5/uj9Hgevst28ZdzaYdbT1NTyd FjL35J3JGwq0b/zVy+H8yDEn+mTGGVe31ReURZVn1fNblDYJvNOdeHRFSmn+Sct/+ieLr3Hv eXllk/WW9V9FpG6/8/JeoK5t6RkpoPLqWoxgVOdtlZUJTUkcXOn6M/TnHHi2NthsJdtlJZbi jERDLeai4kQAHfondm4CAAA=
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
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: Thu, 30 May 2013 08:28:01 -0000
Hi Kevin, > Can we add that the answerer must also ensure that it can de-mulitplex the media it will receive? That is, it must either agree > to a de-mulitplex scheme that was offered (either in the SDP, such as SSRC signalling, or external signalling) or ensure that > there is no PT overlap in the bundle by not including certain PTs or by unbundling one or more m-lines. For sure we will have to add text also about that. The reason I didn't add anything yet is because we don't have a clear outcome of that discussion yet :) Thanks! Regards, Christer On 30 May 2013 07:27, Christer Holmberg <christer.holmberg@ericsson.com> wrote: Hi, > 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. Yes. There is going to be a separate section which describes that more in detail. Thanks! Regards, Christer 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 > _______________________________________________ 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] BUNDLE TEXT: Answerer Procedures (29th M… Christer Holmberg
- Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29… Paul Kyzivat
- Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29… Christer Holmberg
- Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29… Kevin Dempsey
- Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29… Christer Holmberg
- Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29… Cullen Jennings (fluffy)
- Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29… Eric Rescorla
- Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29… Christer Holmberg
- Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29… Cullen Jennings
- Re: [MMUSIC] BUNDLE TEXT: Answerer Procedures (29… Christer Holmberg