[rtcweb] Draft name change: draft-holmberg-mmusic-sdp-bundle-negotiation-00 [was: API options for supporting fork with ROAP (Re: SDP Offer/Answer draft-jennings-rtcweb-signaling]

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 19 October 2011 09:35 UTC

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 51F1521F8B3E for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 02:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.528
X-Spam-Level:
X-Spam-Status: No, score=-6.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 j5lN-geENdyd for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 02:35:34 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 8A69921F8B7A for <rtcweb@ietf.org>; Wed, 19 Oct 2011 02:35:34 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-0c-4e9e99e5696c
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 11.B4.20773.5E99E9E4; Wed, 19 Oct 2011 11:35:33 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.250]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Wed, 19 Oct 2011 11:35:33 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Wed, 19 Oct 2011 11:35:32 +0200
Thread-Topic: Draft name change: draft-holmberg-mmusic-sdp-bundle-negotiation-00 [was: API options for supporting fork with ROAP (Re: SDP Offer/Answer draft-jennings-rtcweb-signaling]
Thread-Index: AcyOOAvFEQM5Q6/cSBGsE2j1JPlOUgACcZXQ
Message-ID: <7F2072F1E0DE894DA4B517B93C6A058522341F4895@ESESSCMS0356.eemea.ericsson.se>
References: <15B0E3AD-3086-499A-8E79-7AE58B3376C4@cisco.com> <CAD5OKxvE77Fia1hVRhdmqnfsOExpdJq=J2VMwtsfB_7ztEYtLA@mail.gmail.com> <4E9D43D2.9010804@alvestrand.no> <CALiegfnaE4OX6QHkkr1k5+Ux2WUOixB+4=e52_+gpphM4HKi6w@mail.gmail.com> <4E9D5E9A.7090308@alvestrand.no> <CALiegfkPk=o0YvmUCocmUOeL_hp37UogeYkv9vE=KQqQESRcKg@mail.gmail.com> <4E9D7019.2020303@ericsson.com> <CALiegf=3dHhC1gt=YEH-=7mdi33cjKx74OMa65CxVDvsgRwUdQ@mail.gmail.com> <4E9D85CB.6030503@ericsson.com> <CAD5OKxtRygfzAYviKPyDxeZGt2ajXFQHr9WGdqiR24MbC3j2Cw@mail.gmail.com> <4E9E81B3.10404@ericsson.com> <4E9E885A.1030108@alvestrand.no>
In-Reply-To: <4E9E885A.1030108@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [rtcweb] Draft name change: draft-holmberg-mmusic-sdp-bundle-negotiation-00 [was: API options for supporting fork with ROAP (Re: SDP Offer/Answer draft-jennings-rtcweb-signaling]
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, 19 Oct 2011 09:35:35 -0000

Hi,
 
>> Now we're getting into the stuff that is not my home turf :). 
>> But as I understand it, the current assumption is that the browser would in 
>> fact only open one port which all RTP streams use. In most 
>> cases all streams would be multiplexed over the same 5-tuple, but the 
>> other end (if it is not a browser) could open separate ports for each RTP 
>> stream, if it (read legacy) would like to avoid multiplexing.
>> Actually my current understanding is that in all cases, all 
>> video components of all MediaStreams would use the same RTP 
>> session, and all audio components of all MediaStreams would 
>> use the same RTP session.
> 
> If the TOGETHER extension (draft-alvestrand-one-rtp) or 
> BONDING extension (next version of draft-holmberg-mmusic-sdp-multiplex-negotiation; 
> the name changed) is supported, both media types would be sent across 
> one RTP session.

Actually, BUNDLE is the name of the new extension :)

Due to the name change of the extension, the name of the draft has also changed.

The name is now: draft-holmberg-mmusic-sdp-bundle-negotiation-00.

http://www.ietf.org/id/draft-holmberg-mmusic-sdp-bundle-negotiation-00.txt

Note that Harald is now co-author of the draft.

Regards,

Christer