Return-Path: 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 3604411E8125 for ; Sat, 21 Sep 2013 01:40:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.403 X-Spam-Level: X-Spam-Status: No, score=-5.403 tagged_above=-999 required=5 tests=[AWL=0.245, 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 TlnKWmYhRgu3 for ; Sat, 21 Sep 2013 01:40:30 -0700 (PDT) Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8C521F9A8C for ; Sat, 21 Sep 2013 01:40:28 -0700 (PDT) X-AuditID: c1b4fb25-b7eff8e000000eda-69-523d5b7b638f Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 02.F2.03802.B7B5D325; Sat, 21 Sep 2013 10:40:27 +0200 (CEST) Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.02.0328.009; Sat, 21 Sep 2013 10:34:57 +0200 From: Christer Holmberg To: Harald Alvestrand , "mmusic@ietf.org" Thread-Topic: [MMUSIC] BUNDLE (pre-5): New Answerer text Thread-Index: Ac6vqXfgfa2PFfL9SQ+/vvsowoLHhQG2yCSAAAgwRNA= Date: Sat, 21 Sep 2013 08:34:56 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4A8FC0@ESESSMB209.ericsson.se> References: <7594FB04B1934943A5C02806D1A2204B1C4A787B@ESESSMB209.ericsson.se> <523D3F31.8050204@alvestrand.no> In-Reply-To: <523D3F31.8050204@alvestrand.no> Accept-Language: en-US Content-Language: fi-FI X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.146] Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C4A8FC0ESESSMB209erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrJLMWRmVeSWpSXmKPExsUyM+JvjW51tG2Qwd6l8hbH+rrYLKYuf8zi wORxZcIVVo8lS34yBTBFcdmkpOZklqUW6dslcGVsfb2ZsWD9DsaKg2+uMjUwdi9h7GLk5JAQ MJHYuOE7O4QtJnHh3nq2LkYuDiGBw4wS1zv2MkI4SxglJsw7yNTFyMHBJmAh0f1PG6RBRCBY Yvmn7UwgtrCAuUTjqdusEHELibP/zkPZVhJ/P65mBrFZBFQl+o7uAFvGK+Ar8fj8LXaQkUIC BRJH1smAhDkFdCW2XjwL1soIdM/3U2vAxjMLiEt8OHidGeJOAYkle85D2aISLx//Y4WwlSR+ bLjEAlGfL/Hn1m5GiFWCEidnPmGZwCgyC8moWUjKZiEpg4jrSdyYOoUNwtaWWLbwNVS9rsSM f4dYkMUXMLKvYmTPTczMSS832sQIjJ6DW36r7mC8c07kEKM0B4uSOO9mvTOBQgLpiSWp2amp BalF8UWlOanFhxiZODilGhg3CkTvUme+kbC4ccafWVLRGot03p1v4ZY54C4dI/bi69uKr7wt v0KmNp3+3sSfq6ryoe10a4iq6uJVwXvXmmqK8LYo/gpwf7JmVX24em/zA6c19/ec+ftCc9rp 46IXVDQPmd00/ty2Lqrdo2jluhtiu5XOXzjTeWjGZ78l20MYolZlX05TYctWYinOSDTUYi4q TgQAZPwrgmwCAAA= Subject: Re: [MMUSIC] BUNDLE (pre-5): New Answerer text X-BeenThere: mmusic@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiparty Multimedia Session Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Sep 2013 08:40:35 -0000 --_000_7594FB04B1934943A5C02806D1A2204B1C4A8FC0ESESSMB209erics_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Harald, Thanks for your comments! Regards, Christer L=E4hett=E4j=E4: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] P= uolesta Harald Alvestrand L=E4hetetty: 21. syyskuuta 2013 9:40 Vastaanottaja: mmusic@ietf.org Aihe: Re: [MMUSIC] BUNDLE (pre-5): New Answerer text On 09/19/2013 12:23 PM, Christer Holmberg wrote: Hi, Based on the new BUNDLE Offerer text, I also modified (and, hopefully clari= fied) the Answerer text. In addition, the new text also covers 'bundle-only' m- lines. Comments are welcome. Some grammar nits. Regards, Christer --------------------- 6.5. SDP Answerer Procedures 6.5.1. Answerer Bundle Address Selection and Usage 6.5.1.1. Offerer Bundle Address Selection When an Answerer generates an Answer that contains a BUNDLE group, the Answer MUST select the Offerer's BUNDLE address. The first mid value in the SDP group:BUNDLE attribute mid list of the Offer represents the address which the Offerer wishes the Answer to select as the Offerer's BUNDLE address [ref-to-offer-prec]. The Answerer SHOULD select the address represented by the first mid value, unless the Answerer in the associated Answer will rejects the "m=3D" line associated with the mid value [ref], or remove the "m=3D" line from the BUNDLE group [ref] from the BUNDLE group. In such case the "from the BUNDLE group" is repeated twice. Answerer MUST select an address associated with the next mid value in the SDP group:BUNDLE attribute mid list of the Offer. This should be "an address associated with the first unrejected MID that re= mains in the BUNDLE group". Otherwise, rejecting MID #1 and #2 would leave you in an undefined state. In the SDP Answer, the Answerer MUST place the mid value associated with the selected Offerer's BUNDLE address first in the SDP group:BUNDLE attribute mid list associated with the BUNDLE group. Section 10.1 shows an example of an Offerer's BUNDLE address selection. 6.5.1.2. Anwerer Bundle Address Selection When an Answerer creates an Answer that contains a BUNDLE group, the Answerer MUST assign a local shared address, the Answerer's BUNDLE address, to each "m=3D" line within the BUNDLE group. The Answerer is allowed to change its BUNDLE address in any SDP Answer. The Answerer MUST NOT assign a shared address, that it has assigned to an "m=3D" line within a BUNDLE group, to an "m=3D" line outside the BUNDLE group. Section 10.1 shows an example of an Answerer's local BUNDLE address selection. 6.5.2. Moving A Media Description Out Of A BUNDLE Group When an Answerer generates an Answer, in which an "m=3D" line is moved out of a BUNDLE group, the Answerer assigns an address to the moved "m=3D" line based on the type of address that the Offerer assigned to the associated "m=3D" line in the associated Offer, as described below. If the Offerer assigned a shared address to the "m=3D" line, the answerer MUST reject the moved "m=3D" line, according to the procedures in Section 6.5.3. If the Offerer assigned a 'bundle-only' attribute to the "m=3D" line, the Answerer MUST reject the moved "m=3D" line, according to the procedures in Section 6.5.3. If the Offerer assigned a unique address to the "m=3D" line, the Answer MUST assign a unique address to the moved "m=3D" line. In addition, in either case above, the Answerer MUST NOT anymore include a mid value, representing the "m=3D" line, in the SDP group:BUNDLE attribute list associated with the BUNDLE group. 6.5.3. Rejecting A Media Description In A BUNDLE Group When an Answerer generates an Answer, in which an "m=3D" line associated with a BUNDLE group is rejected, the Answerer MUST assign an address with a zero port value to the rejected "m=3D" line, according to the procedures in [RFC3264]. In addition, the Answerer MUST NOT anymore include a mid value, representing the "m=3D" line, in the SDP group:BUNDLE attribute midlist associated with the BUNDLE group. _______________________________________________ mmusic mailing list mmusic@ietf.org https://www.ietf.org/mailman/listinfo/mmusic --_000_7594FB04B1934943A5C02806D1A2204B1C4A8FC0ESESSMB209erics_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi Harald,<= /span>

 

Thanks for your commen= ts!

 

Regards,

 

Christer

 

L=E4hett=E4j=E4: mmusic-bounces@ietf.org [mailto:mmusic= -bounces@ietf.org] Puolesta Harald Alvestrand
L=E4hetetty: 21. syyskuuta 2013 9:40
Vastaanottaja: mmusic@ietf.org
Aihe: Re: [MMUSIC] BUNDLE (pre-5): New Answerer text

 

On 09/19/2013 12:23 PM, Christer Holmberg wrote:

Hi,

 

Based on the new BUNDLE Offerer text, I also modifie= d (and, hopefully clarified) the Answerer text.

 

In addition, the new text also covers ‘bundle-= only’ m- lines.

 

Comments are welcome.

Some grammar nits.

 

Regards,

 

Christer

 

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

 

6.5.  SDP Answerer Procedures

 

6.5.1.  Answerer Bundle Address Selection and Usage

 

6.5.1.1.  Offerer Bundle Address Selection

 

When an Answerer generates an Answer that contains a BUNDL= E group,

the Answer MUST select the Offerer’s BUNDLE address.= The first mid

value in the SDP group:BUNDLE attribute mid list of the Of= fer

represents the address which the Offerer wishes the Answer= to

select as the Offerer's BUNDLE address [ref-to-offer-prec]= .

 

The Answerer SHOULD select the address represented by the = first mid

value, unless the Answerer in the associated Answer will r= ejects the

“m=3D” line associated with the mid value [ref= ], or remove the “m=3D” line

from the BUNDLE group [ref] from the BUNDLE group. In such= case the

"from the BUNDLE group" is= repeated twice.

Answerer MUST select an address associated with the next m= id value in

the SDP group:BUNDLE attribute mid list of the Offer.

This should be "an address asso= ciated with the first unrejected MID that remains in the BUNDLE group"= .
Otherwise, rejecting MID #1 and #2 would leave you in an undefined state.

 

In the SDP Answer, the Answerer MUST place the mid value a= ssociated with

the selected Offerer’s BUNDLE address first in the S= DP group:BUNDLE

attribute mid list associated with the BUNDLE group.

 

Section 10.1 shows an example of an Offerer's BUNDLE addre= ss

selection.

 

 

6.5.1.2.  Anwerer Bundle Address Selection

 

When an Answerer creates an Answer that contains a BUNDLE = group,

the Answerer MUST assign a local shared address, the Answe= rer’s BUNDLE

address, to each “m=3D” line within the BUNDLE= group.

 

The Answerer is allowed to change its BUNDLE address in an= y SDP

Answer.

 

The Answerer MUST NOT assign a shared address, that it has= assigned

to an "m=3D" line within a BUNDLE group, to an &= quot;m=3D" line outside

the BUNDLE group.

 

Section 10.1 shows an example of an Answerer's local BUNDL= E address

selection.

 

6.5.2.  Moving A Media Description Out Of A BUNDLE Gr= oup

 

When an Answerer generates an Answer, in which an "m= =3D" line is moved

out of a BUNDLE group, the Answerer assigns an address to = the moved

“m=3D” line based on the type of address that = the Offerer assigned

to the associated “m=3D” line in the associate= d Offer, as described below.

 

If the Offerer assigned a shared address to the “m= =3D” line, the

answerer MUST reject the moved “m=3D” line, ac= cording to the procedures

in Section 6.5.3.

 

If the Offerer assigned a ‘bundle-only’ attrib= ute to the “m=3D” line,

the Answerer MUST reject the moved “m=3D” line= , according to the procedures

in Section 6.5.3.

 

If the Offerer assigned a unique address to the “m= =3D” line, the Answer

MUST assign a unique address to the moved “m=3D̶= 1; line.

 

In addition, in either case above, the Answerer MUST NOT a= nymore

include a mid value, representing the “m=3D” l= ine, in the SDP

group:BUNDLE attribute list associated with the BUNDLE gro= up.

 

 

6.5.3.  Rejecting A Media Description In A BUNDLE Gro= up

 

When an Answerer generates an Answer, in which an "m= =3D" line associated

with a BUNDLE group is rejected, the Answerer MUST assign = an address

with a zero port value to the rejected "m=3D" li= ne, according to the

procedures in [RFC3264]. In addition, the Answerer MU= ST NOT anymore

include a mid value, representing the "m=3D" lin= e, in the SDP group:BUNDLE

attribute midlist associated with the BUNDLE group.=

 




_______________________________________________
mmusic mailing list
mmusic@ietf.org

https://www.i=
etf.org/mailman/listinfo/mmusic


 
--_000_7594FB04B1934943A5C02806D1A2204B1C4A8FC0ESESSMB209erics_--