Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
 with ESMTP id AEA5E11E814F for <rtcweb@ietfa.amsl.com>;
 Fri, 27 Sep 2013 06:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.874
X-Spam-Level: 
X-Spam-Status: No, score=-3.874 tagged_above=-999 required=5 tests=[AWL=-1.276,
 BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 tGPMOKfFBf5H for
 <rtcweb@ietfa.amsl.com>; Fri, 27 Sep 2013 06:59:17 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56])
 by ietfa.amsl.com (Postfix) with ESMTP id 4C32321F9CA1 for <rtcweb@ietf.org>;
 Fri, 27 Sep 2013 06:59:14 -0700 (PDT)
X-AuditID: c1b4fb38-b7fcf8e0000062b8-d4-52458f312f91
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.125]) by
 sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id
 16.83.25272.13F85425; Fri, 27 Sep 2013 15:59:13 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by
 ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.02.0328.009;
 Fri, 27 Sep 2013 15:59:13 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Unified Plan: 'bundle-only' documentation
Thread-Index: Ac67icB0IqAhwR+TTWqeeD7ies23YA==
Content-Class: urn:content-classes:message
Date: Fri, 27 Sep 2013 13:59:12 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4ADF2D@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.18]
Content-Type: multipart/alternative;
 boundary="_000_7594FB04B1934943A5C02806D1A2204B1C4ADF2DESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFLMWRmVeSWpSXmKPExsUyM+Jvra5hv2uQwdwOeYu1/9rZHRg9liz5
 yRTAGMVlk5Kak1mWWqRvl8CVMffPJ6aCNSIVqzbOZWlgfCfQxcjJISFgInF8z15mCFtM4sK9
 9WwgtpDAUUaJo//Kuxi5gOwljBLvLy5m6mLk4GATsJDo/qcNUiMioC5x+eEFdhBbWMBIYtrW
 LawQcXOJhtdrWCBsPYld3yeA1TALaEnsmLCPEcRmEVCVWL92DxOIzSvgK/H98wqwOCPQDd9P
 rWGCqBeXuPVkPhPEbQISS/ach7pTVOLl43+sELaixMdXEDOZBfIlFm2ZygIxU1Di5MwnLBMY
 hWchWT0LydhZSFpmIWmBiOtJ3Jg6hQ3C1pZYtvA1M4StKzHj3yGoGmuJ32+PMSKrWcDIuYqR
 ozi1OCk33chgEyMwfg5u+W2xg/HyX5tDjNIcLErivB/fOgcJCaQnlqRmp6YWpBbFF5XmpBYf
 YmTi4JRqYBTh6Tpd+4TjnM8M/Y+znJf92fh7jYFRfDfbsq6XTRrHcq+c/aXrsKvsuluE87el
 9z4/6t0X+WeeRbcur3RR5D3Fu/7y/3kMbUt/fwkyOs/zVffGhs/8++Xv6e7PTPslGBU35/Wn
 6Z3283Y9nGFR/Xj+U5WjTZw8r/k3qNsmigS2aDhNVmhf916JpTgj0VCLuag4EQBY+ScObQIA AA==
Subject: [rtcweb] Unified Plan: 'bundle-only' documentation
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list
 <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>,
 <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>,
 <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2013 13:59:23 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1C4ADF2DESESSMB209erics_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,



On the MMUSIC list I have suggested updated SDP Offer/Answer text for BUNDL=
E.



Part of that text is the definition, and usage, of the SDP 'bundle-only' at=
tribute.



However, eventhough I personally think it fits well there (and I believe Ad=
am had the same opinion, when I talked with him off-line in Berlin), afaik =
there has never been any formal WG agreement that the 'bundle-only' attribu=
te will be defined in the BUNDLE draft.



So, without going into the details (there are some issues, and if you are i=
nterested there are mail threads on the MMUSIC list dealing with those) do =
people have any issues with defining the SDP 'bundle-only' attribute, and t=
he usage of it, in BUNDLE?



If not, can we make a WG decision on the matter?



Regards,



Christer

--_000_7594FB04B1934943A5C02806D1A2204B1C4ADF2DESESSMB209erics_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <5B36C4DDF38F0247BA3DDAA9B219DECA@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style id=3D"owaParaStyle">P {=0A=
	MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px=0A=
}=0A=
</style>
</head>
<body ocsi=3D"0" fpstyle=3D"1">
<div style=3D"color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; di=
rection: ltr;">
<p>Hi,</p>
<p>&nbsp;</p>
<p>On the MMUSIC list I have suggested updated SDP Offer/Answer text for BU=
NDLE.</p>
<p>&nbsp;</p>
<p>Part of that text is the definition, and usage, of the SDP 'bundle-only'=
 attribute.</p>
<p>&nbsp;</p>
<p>However, eventhough I personally think it fits well there (and I believe=
 Adam had the same opinion, when I talked with him off-line in Berlin), afa=
ik there has never been any formal WG agreement that the 'bundle-only' attr=
ibute will be defined in the BUNDLE
 draft.</p>
<p>&nbsp;</p>
<p>So, without going into the details (there are some&nbsp;issues, and&nbsp=
;if you are interested there are mail threads on the MMUSIC list dealing wi=
th those)&nbsp;do people have any issues with defining the SDP 'bundle-only=
' attribute, and the usage of it, in BUNDLE?</p>
<p>&nbsp;</p>
<p>If not, can we make a WG decision on the matter?</p>
<p>&nbsp;</p>
<p>Regards,</p>
<p>&nbsp;</p>
<p>Christer</p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1C4ADF2DESESSMB209erics_--
