[rtcweb] RTP architecture
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Wed, 20 July 2011 07:52 UTC
Return-Path: <gonzalo.camarillo@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 A0A5621F84BF for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 00:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.607
X-Spam-Level:
X-Spam-Status: No, score=-106.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 tHKlC4Fx1av2 for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 00:52:23 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 282F421F847C for <rtcweb@ietf.org>; Wed, 20 Jul 2011 00:51:13 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-2f-4e2688f01eb2
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 00.A0.20773.0F8862E4; Wed, 20 Jul 2011 09:51:12 +0200 (CEST)
Received: from [131.160.126.141] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Wed, 20 Jul 2011 09:51:12 +0200
Message-ID: <4E2688F0.8090403@ericsson.com>
Date: Wed, 20 Jul 2011 10:51:12 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: rtcweb@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: [rtcweb] RTP architecture
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, 20 Jul 2011 07:52:27 -0000
Folks, as you know if you are following this WG, there have been discussions on multiplexing RTP sessions and how that would affect legacy RTP systems. Those discussions have not concluded yet. Nevertheless, note that changes to the RTP architecture and other fundamental changes to RTP (should you require any) would need to be made in AVTCORE, which is where the RTP expertise is. The RTCWeb charter says the following: > If there is identification of missing protocols or > functionalities, such work can be requested to be done in another > working group with a suitable charter or by requests for chartering it > in this WG or another WG Cheers, Gonzalo
- [rtcweb] RTP architecture Gonzalo Camarillo