Re: [rtcweb] path forward on bundle

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 05 October 2012 12:41 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 35A5D21F8645; Fri, 5 Oct 2012 05:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.912
X-Spam-Level:
X-Spam-Status: No, score=-4.912 tagged_above=-999 required=5 tests=[AWL=-1.063, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_16=0.6, J_CHICKENPOX_56=0.6, RCVD_IN_DNSWL_MED=-4]
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 x2fTsBDAm+-U; Fri, 5 Oct 2012 05:41:44 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8CDF621F8630; Fri, 5 Oct 2012 05:41:43 -0700 (PDT)
X-AuditID: c1b4fb30-b7f7d6d0000042ea-c4-506ed5866dc6
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 32.83.17130.685DE605; Fri, 5 Oct 2012 14:41:42 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.99]) by esessmw0256.eemea.ericsson.se ([153.88.115.96]) with mapi; Fri, 5 Oct 2012 14:41:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, mmusic WG <mmusic@ietf.org>, Harald Tveit Alvestrand <harald@alvestrand.no>, Justin Uberti <juberti@google.com>, Eric Rescorla <ekr@rtfm.com>, Bernard Aboba <bernard_aboba@hotmail.com>, Jonathan Lennox <jonathan@vidyo.com>, Randell Jesup <rjesup@mozilla.com>
Date: Fri, 5 Oct 2012 14:41:40 +0200
Thread-Topic: path forward on bundle
Thread-Index: AQHNovTwIf3O/3MMMESi6UaijuNjf5eqpRiw
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585340A7BD37B@ESESSCMS0356.eemea.ericsson.se>
References: <C5E08FE080ACFD4DAE31E4BDBF944EB111869DCB@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB111869DCB@xmb-aln-x02.cisco.com>
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: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyM+JvrW7b1bwAg32XpC32L7nMbLHi9Tl2 i47JbBbH+rrYLPYvPs9ssXWqkMXU5Y9ZLDZ9OchssfZfO7sDp8eVCVdYPab83sjqsWBTqcfj njNsHkuW/GTy6DvQxeox+XEbs0fbszvsARxRXDYpqTmZZalF+nYJXBl9W5uZCharVpzbM4Ol gbFLuouRk0NCwERiXsNbNghbTOLCvfVANheHkMApRokZF89COfMZJRZcWcbSxcjBwSZgIdH9 TxskLiKwl0li0vHbjCDdzALqEncWn2MHsVkEVCQuzLrEDGILA9k3+jrBakQEVCUeLL3OAmEb SbyZf5YVxOYVCJe48/YoWI2QgI/Erj/nwWo4BXwl9j3qBYszAl33/dQaJohd4hK3nsxngrha QGLJnvPMELaoxMvH/1gh6kUl7rSvh7pNR2LB7k9sELa2xLKFr5kh9gpKnJz5hGUCo9gsJGNn IWmZhaRlFpKWBYwsqxiFcxMzc9LLzfVSizKTi4vz8/SKUzcxAiP34JbfBjsYN90XO8QozcGi JM6rp7rfX0ggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAMj8+KStYJquaeluwNyix133DjO7+J+ vbtWeWPefB/mhasEHCq5e31UChNdtTLFe46dUPCfx10z7Y/rzaN5m0oEZ0yftn06T6KVz5q2 vz+dA75qLD1mJNVhubXsxv/+Dywfahbe2tnYv4x1ooDI1DdNmYp8PlPkF8fVK/KYZU/YxLC4 +MHqA2VKLMUZiYZazEXFiQAEuMcCqgIAAA==
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] path forward on bundle
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: Fri, 05 Oct 2012 12:41:45 -0000

Hi,

>I'm trying to figure out how to move forward on bundle stuff. Let me start by summarizing what I think the three proposals are then we can try and sort out pros/cons of each. I think we agree that the goals here is to have something that gets the SDP so 
>that we can negotiate using less ports. 
>
>I see it as we have three proposed solutions that I will call "a=bundle same port", "a=bundle different port", and  "m=bundle". I'll try and describe these below to make sure we are on same page of what the three are then we can try and figurer out 
>pros/cons of each and what to do. I'll give examples of the SDP offer for each but I tried and make everything simple, I'm going to ignore the RTCP mux and such but I think you can see how that would get added to all the examples. 
>
>
>First lets set the baseline of an offer that does not want to multiplex the audio and video on same port 
 >        v=0
 >        o=alice 2890844526 2890844526 IN IP4 host.atlanta.example.com
 >        s=
 >        c=IN IP4 host.atlanta.example.com
 >        t=0 0
 >        m=audio 49170 RTP/AVP 0 
 >        a=mid:foo
 >        a=rtpmap:0 PCMU/8000
 >        m=video 49172 RTP/AVP 31 
 >        a=mid:bar
 >       a=rtpmap:31 H261/90000

Correct.


>Proposal "a=bundle same port"
>        v=0
>         o=alice 2890844526 2890844526 IN IP4 host.atlanta.example.com
>         s=
>         c=IN IP4 host.atlanta.example.com
>         t=0 0
>         a=group:BUNDLE foo bar
>         m=audio 49170 RTP/AVP 0 
>         a=mid:foo
>         a=rtpmap:0 PCMU/8000
>         m=video 49170 RTP/AVP 31 
>        a=mid:bar
>         a=rtpmap:31 H261/90000
>
> In the above example, note that all the m lines for a mid identified in the group:BUNLDE have the same port (49170)

Correct. This is what is currently described in draft-bundle.



>Proposal "a=bundle different port"
>         v=0
>         o=alice 2890844526 2890844526 IN IP4 host.atlanta.example.com
>         s=
>         c=IN IP4 host.atlanta.example.com
>         t=0 0
>         a=group:BUNDLE foo bar
>         m=audio 49170 RTP/AVP 0 
>         a=mid:foo
>         a=rtpmap:0 PCMU/8000
>         m=video 49172 RTP/AVP 31 
>         a=mid:bar
>         a=rtpmap:31 H261/90000

> In the above example, note that the port numbers are the same as baseline - if you device receiving this offer does not support group:BUNLDE, then this is identical to the baseline. So one m line has a port of 49170 and the other has a different port. 
> Other than that, it is the same as the "a=bundle same port". The semantics of group:BUNLDE would be defined to be that if the SDP receiver supports BUNDLE and wants to use it, then it places a group:BUNDLE line in the answer and it send all the media 
> to the mids in the in BUNDLE group to the port number identified for the m-line corresponding to the first mid in the BUNDLE group. In this example, the first mid on the a=group:BUNDLE lines is foo, which has a m line with a port of 49170, so both the 
> H261 and PCMU (mids foo and bar) would go to port 49170 if the device creating the answer wanted to use BUNDLE. We don't have a draft yet that says exactly this thought it is very close to the one-rtp draft ( and for that matter  close to bundle draft )

This is more or less Harald's original proposal.



>Proposal "m=bundle"
>         v=0
>         o=alice 2890844526 2890844526 IN IP4 host.atlanta.example.com
>         s=
>         c=IN IP4 host.atlanta.example.com
>         t=0 0
>         a=group:BUNDLE foo bar baz 
>         m=audio 49170 RTP/AVP 0 
>         a=mid:foo
>         a=rtpmap:0 PCMU/8000
>         m=video 49172 RTP/AVP 31 
>         a=mid:bar
>         a=rtpmap:31 H261/90000
>         m=bundle 10000 RTP/AVP 0 8 97 31 32
>         a=mid:baz
>         a=full-rtpmap:0 audio/PCMU/8000
>         a=full-rtpmap:31 video/H261/90000
>
>
> Note in the above example the SDP above the m=bundle line is pretty much the same as the baseline + the group:BUNDLE line. The m=bundle is new media type that indicates many things are bundled together on port 10000. A device that understood 
> bundle would know to ignore the m lines corresponding to foo and bar mids and would just use the stuff from the bas mid. 

Correct. Later today, we are planning to submit an individual draft (ie *not* a new version of draft-bundle) on this alternative, so that people have some text to look at.

Regards,

Christer