Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.

Hadriel Kaplan <HKaplan@acmepacket.com> Wed, 16 November 2011 06:42 UTC

Return-Path: <HKaplan@acmepacket.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB471F0C4A for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 22:42:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level:
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599]
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 eHjMJThuKF8E for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 22:42:13 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 67D101F0C5D for <avt@ietf.org>; Tue, 15 Nov 2011 22:42:13 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 16 Nov 2011 01:42:12 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 16 Nov 2011 01:42:12 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Roni Even <ron.even.tlv@gmail.com>
Thread-Topic: [AVTCORE] Call for consensus on multiplexing multipe media streams.
Thread-Index: AQHMpCrenylke9Cqx0KuKib+4n5omA==
Date: Wed, 16 Nov 2011 06:42:11 +0000
Message-ID: <4FECDC5A-6393-4D73-9965-C9AE60391A56@acmepacket.com>
References: <04CAD96D4C5A3D48B1919248A8FE0D54104F2031@xmb-sjc-215.amer.cisco.com> <4EC3256A.1030802@matthew.at> <5ABEAD38-E871-4CA6-8A3F-632FFD15369A@acmepacket.com> <4ec3557a.1c05650a.2f07.7d11@mx.google.com>
In-Reply-To: <4ec3557a.1c05650a.2f07.7d11@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <367A61A557AD4B40979C14B3ACB691BE@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<avt@ietf.org>" <avt@ietf.org>
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2011 06:42:17 -0000

OK, so that's how I had also interpreted the original consensus-call email options.
Thank you for the clarification.

-hadriel


On Nov 16, 2011, at 1:14 AM, Roni Even wrote:

> Hi Hadriel,
> There is background information about the different multiplexing in
> http://tools.ietf.org/html/draft-westerlund-avtcore-multiplex-architecture-0
> 0 
> I would like to say that this is an individual draft does not reflect
> consensus of the WG. Sections 3 till 6 provide the overview that may be
> helpful for you.
> 
> As a WG chair I cannot comment on  sections 7-9 but they are relevant but
> caused discussion.
> 
> The different proposals are in
> 
> http://tools.ietf.org/html/draft-westerlund-avtcore-transport-multiplexing-0
> 1 for option 2
> 
> and 
> 
> http://tools.ietf.org/id/draft-lennox-rtcweb-rtp-media-type-mux-00.txt for
> option 3
> 
> 
> All the documents were discussed in the AVTcore session.
> 
> 
> Roni Even
> AVT co-chair
> 
> 
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Hadriel Kaplan
>> Sent: Wednesday, November 16, 2011 7:44 AM
>> To: avt@ietf.org
>> Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media
>> streams.
>> 
>> 
>> If what Matthew says is true, that 2 and 3 are on-the-wire equivalent,
>> then I'm totally confused by the choices now.
>> 
>> Can the chairs please clarifies what the consensus call options mean?
>> 
>> In particular, can you do so by indicating actual drafts, rather than
>> using high-level terminology?
>> 
>> -hadriel
>> 
>> 
>> On Nov 15, 2011, at 9:52 PM, Matthew Kaufman wrote:
>> 
>>> On 11/16/11 10:47 AM, Ali C. Begen (abegen) wrote:
>>>>> So the WG chairs are asking which direction to take
>>>>> 
>>>>> 
>>>>> 
>>>>> The options we have are:
>>>>> 
>>>>> 
>>>>> 
>>>>> 1. Go forward with both solutions.
>>>>> 
>>>>> 2. Only define multiplexing of multiple RTP sessions in a single
>> transport flow.
>>>>> 
>>>>> 3. Only define multiplexing of multiple media types in a single RTP
>> session.
>>>>> 
>>>>> 4. Not enough information in order to decide, more discussion is
>> needed.
>>>> My preference is (2) but I am also fine with (1) if that is the
>> consensus.
>>>> 
>>>> 
>>> 
>>> (Sorry about tagging on to this point in the thread, but I joined the
>>> list late)
>>> 
>>> I'm fine with either 2 or 3, but only because I think that 2 and 3
>> can look exactly the same on the wire and only differ in the
>> semantics... and I don't really care which semantics we choose.
>>> 
>>> I'm not ok with a kind of 2 that isn't wire-equivalent to 3.
>>> 
>>> Matthew Kaufman
>>> _______________________________________________
>>> Audio/Video Transport Core Maintenance avt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/avt
>> 
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>