Re: [rtcweb] [MMUSIC] BUNDLE: RTP only?

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Wed, 13 February 2013 20:37 UTC

Return-Path: <fluffy@cisco.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 3910921E8064; Wed, 13 Feb 2013 12:37:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.298
X-Spam-Level:
X-Spam-Status: No, score=-110.298 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id weXfTUFS6MpA; Wed, 13 Feb 2013 12:37:43 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4DC21E8055; Wed, 13 Feb 2013 12:37:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1065; q=dns/txt; s=iport; t=1360787863; x=1361997463; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yDQyfEh9wl2MUgutnT7/ceetg9OC+8Mku4WZez/JGd0=; b=MNsEIJTavk1FfbIR7STJ3uaDerRaEyq0cGjE5mwAK6FeLwy3UVshwpwU ypCXbiUEpFgSZDLQQ0T/4BkoDbcvzBW2xfCFkVWP3wyLhbL6ScVg8I2CL 6S3mxn9NgiDgp1YrSngi7Ygdbh+Myb/Dw629SVhCxlURW+a4r/qjr/WX8 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAG/4G1GtJXG8/2dsb2JhbABFwG4Wc4IgAQEEAQEBNzQLEAIBCCIUECcLJQIEDgUIE4d3DL9EBJEjYQOmd4MGgic
X-IronPort-AV: E=Sophos;i="4.84,658,1355097600"; d="scan'208";a="176830057"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-4.cisco.com with ESMTP; 13 Feb 2013 20:37:42 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r1DKbg6V010889 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Feb 2013 20:37:42 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.155]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Wed, 13 Feb 2013 14:37:42 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] BUNDLE: RTP only?
Thread-Index: AQHOCin4yriVbi3BTkiuqlV2yqiiBw==
Date: Wed, 13 Feb 2013 20:37:42 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1133DE7B0@xmb-aln-x02.cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B0D8131@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B0D8131@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D4D5C2A1516F234C84A43B630042AF25@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [rtcweb] [MMUSIC] BUNDLE: RTP only?
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: Wed, 13 Feb 2013 20:37:44 -0000

I think EKR expressed that he felt it was important for data channel to be included in the multiplexing. 


On Feb 13, 2013, at 12:48 PM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> 
> (Sorry for sending this to both RTCWEB and MMUSIC, but it is related to both the need of RTCWEB, and the solution produced by MMUSIC)
> 
> Hi,
> 
> At the interim, during my BUNDLE presentation, I indicated that we need to make a decision whether the solution (whatever it will be...) shall support bundling of non-RTP media. Not saying it can't be changed, but as currently documented all alternatives only support bundling of RTP media.
> 
> There might have been some comments from the mic, but as far as I know there was no decision (if there was, please point me to it).
> 
> So, my question is: do we keep the scope to RTP media?
> 
> Regards,
> 
> Christer
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic