Re: [rtcweb] DRAFT Agenda for RTCWEB

"Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com> Thu, 28 February 2013 23:10 UTC

Return-Path: <richard.ejzak@alcatel-lucent.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 9AE6421F8511 for <rtcweb@ietfa.amsl.com>; Thu, 28 Feb 2013 15:10:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.609
X-Spam-Level:
X-Spam-Status: No, score=-9.609 tagged_above=-999 required=5 tests=[AWL=0.640, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 ko2jT2248bbT for <rtcweb@ietfa.amsl.com>; Thu, 28 Feb 2013 15:10:21 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id AA83D21F8506 for <rtcweb@ietf.org>; Thu, 28 Feb 2013 15:10:20 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r1SNAB29021586 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 1 Mar 2013 00:10:11 +0100
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (135.5.2.35) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 1 Mar 2013 00:10:11 +0100
Received: from US70UWXCHMBA04.zam.alcatel-lucent.com ([169.254.12.105]) by US70TWXCHHUB03.zam.alcatel-lucent.com ([135.5.2.35]) with mapi id 14.02.0247.003; Thu, 28 Feb 2013 18:10:08 -0500
From: "Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Ted Hardie <ted.ietf@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] DRAFT Agenda for RTCWEB
Thread-Index: AQHOFRLcZ2QmQVBDiECl5/dQQDdArZiOfAyAgAFkj4A=
Date: Thu, 28 Feb 2013 23:10:07 +0000
Message-ID: <03FBA798AC24E3498B74F47FD082A92F36EA7EAB@US70UWXCHMBA04.zam.alcatel-lucent.com>
References: <CA+9kkMALouyyzN4dcGdF92TO2HGcBHbHR6fvHg7QC-x5ndCGjw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B10B717@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B10B717@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Cc: Richard Barnes <rbarnes@bbn.com>, "rtcweb-chairs@tools.ietf.org" <rtcweb-chairs@tools.ietf.org>
Subject: Re: [rtcweb] DRAFT Agenda for RTCWEB
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: Thu, 28 Feb 2013 23:10:21 -0000

Since multiplexing of the data channel with RTP media has been shown as a desirable feature of BUNDLE (and most of its variants), I would suggest that this be treated as a significant advantage for BUNDLE (and similarly capable variants) over any proposal without it.  Cullen's "Plan A" is preferred over Plan B precisely because it has an incremental muxing advantage.

BR, Richard

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Christer Holmberg
> Sent: Wednesday, February 27, 2013 2:30 PM
> To: Ted Hardie; rtcweb@ietf.org
> Cc: Richard Barnes; rtcweb-chairs@tools.ietf.org
> Subject: Re: [rtcweb] DRAFT Agenda for RTCWEB
> 
> 
> Hi,
> 
> Does the Data Channel part (or some other part) of the agenda include
> making a decision on whether it shall be possible to bundle the Data
> Channel with the RTP media?
> 
> Or, do we already have consensus that it shall be possible?
> 
> Just to clarify, because I think it is important input for the MMUSIC
> discussions on the actual mechanism.
> 
> Regards,
> 
> Christer
> 
> 
> ________________________________________
> From: rtcweb-bounces@ietf.org [rtcweb-bounces@ietf.org] on behalf of
> Ted Hardie [ted.ietf@gmail.com]
> Sent: Wednesday, 27 February 2013 7:49 PM
> To: rtcweb@ietf.org
> Cc: Richard Barnes; rtcweb-chairs@tools.ietf.org
> Subject: [rtcweb] DRAFT Agenda for RTCWEB
> 
> The agenda below has been uploaded as an initial, draft agenda for the
> group.  Comments on the timing and balance are encouraged.
> 
> thanks,
> 
> Ted Hardie
> 
> RTCWEB Draft Agenda
> March 12, 2013 9:00 to 11:30
> 
> Administrivia (5 min)
> 
> AD Message (5 min)
> 
> Data Channel
>  - draft-jesup-rtcweb-data-protocol (20 min)
>  - draft-thomson-rtcweb-data (15 min)
>  - draft-marcon-rtcweb-data-channel-management (15 min)
>  - Discussion (30 min)
>  - Consensus call(s) (5 min)
> 
> WGLC Issue resolution (30 min)
> - draft-ietf-rtcweb-security
> - draft-ietf-rtcweb-security-arch
> - draft-ietf-rtcweb-overview
> - draft-ietf-rtcweb-use-cases-and-requirements
> 
> RTCP-XR (15 min )
> - draft-ietf-rtcweb-rtp-usage-06
> 
> FEC in RTCWEB  (Call for interest)
> - draft-mandyam-rtcweb-fecframe-00 (5 min)
> 
> Mobile issues for RTCWEB (Call for review)
> - http://tools.ietf.org/html/draft-reddy-rtcweb-mobile-00 (5 min)
> 
> 
> March 14, 2013 9:00 to 11:30
> 
> JSEP
> - draft-rtcweb-jsep (40 min)
> - Discussion (30 min)
> - Consensus call(s) (5)
> 
> Video Codec                       10:15 to 11:30
> 1. draft-alvestrand-rtcweb-vp8-01 (15 mins) 2. draft-burman-rtcweb-
> h264-proposal-01+draft-dbenham-webrtcvideomti-01+draft-marjou-rtcweb-
> video-codec-00
> (25 mins)
>       Discussion (30 minutes)
>       Call the question (5 minutes)
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb