Re: [rtcweb] Transport -03, bundling question (Re: Comments on draft-ietf-rtcweb-transports-02)

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 31 March 2014 15:04 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4AD1A066B for <rtcweb@ietfa.amsl.com>; Mon, 31 Mar 2014 08:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h9ECcAkaYfWC for <rtcweb@ietfa.amsl.com>; Mon, 31 Mar 2014 08:04:11 -0700 (PDT)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 18E591A0A24 for <rtcweb@ietf.org>; Mon, 31 Mar 2014 08:04:10 -0700 (PDT)
X-AuditID: c1b4fb32-b7fe98e0000034f3-09-533983e7589d
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id BA.66.13555.7E389335; Mon, 31 Mar 2014 17:04:07 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.41) with Microsoft SMTP Server id 14.3.174.1; Mon, 31 Mar 2014 17:04:06 +0200
Message-ID: <533983E6.20108@ericsson.com>
Date: Mon, 31 Mar 2014 17:04:06 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>, Harald Alvestrand <hta@google.com>
References: <5304829E.20809@ericsson.com> <5304FC27.807@alvestrand.no> <530C74A1.3000203@ericsson.com> <5338829B.3020505@alvestrand.no> <5339385D.6070006@ericsson.com> <53397036.5050104@alvestrand.no>
In-Reply-To: <53397036.5050104@alvestrand.no>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHLMWRmVeSWpSXmKPExsUyM+Jvje7zZstgg74vPBbH+rrYLE7cOM1s sfZfO7sDs8eVCVdYPRZsKvVYsuQnUwBzFJdNSmpOZllqkb5dAlfG6rvvmQq28le8vHOVqYHx IE8XIyeHhICJxK7Wh4wQtpjEhXvr2boYuTiEBE4ySjxY2MAM4SxnlJj9sYcFpIpXQFOifftR 9i5GDg4WAVWJtVdUQcJsAhYSN380soHYogLBEkvnLIYqF5Q4OfMJC0i5iEC5xJ9/8iBhYYEM iRf7NjBCjD/BKPHzzQqwek4BXYltL0D2cgAdJC7R0xgEEmYW0JOYcrWFEcKWl2jeOpsZxBYS 0JZoaOpgncAoOAvJtllIWmYhaVnAyLyKUbI4tbg4N93IQC83PbdEL7UoM7m4OD9Przh1EyMw jA9u+W20g/HkHvtDjNIcLErivNdZa4KEBNITS1KzU1MLUovii0pzUosPMTJxcEo1MO7hf6l6 n0VSb6Jz+HkJ5z9MfHOdJFapC6rvKnTcuep02smnnBcW5ssKXi3sFd3+mX0dV6fz2scnGuSE 1fNWeWz6t3Ot+MtZ74UvLFjBVVSvspmN6eyan5kXXh/6ebP4apLLjQkLdPRObbU9ocJw0dIr 6dBVtWniXPUZKgwvdvn+r7k3WzBXIkOJpTgj0VCLuag4EQAXWcj+MQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/QSS6FgLsQwfUWlnB4JFpQ87rkRA
Subject: Re: [rtcweb] Transport -03, bundling question (Re: Comments on draft-ietf-rtcweb-transports-02)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 31 Mar 2014 15:04:13 -0000

On 2014-03-31 15:40, Harald Alvestrand wrote:
> Version -03 is now published. I hope you like it!
> 
> New outstanding item:
> 
> I added requirements for implementations to be able to generate both
> fully bundled (one 5-tuple for everything) and fully unbundled (one
> 5-tuple for each flow) configurations, and for implementations to be
> able to tolerate being hit with any combination of bundling schemes.
> 
> Is there a need to specify at MUST, SHOULD or MAY levels other combinations?

RTP Usage has in Section 4.4 requirements concerning implementations
support for bundling of RTP that is:

- Required to support one RTP session per media type
- Required to support one RTP session for all media types

We don't have a requirement regarding one MST per RTP session in the RTP
usage document currently.

To this open issue I would like to highlight that we might need text
describing which combinations of RTP and data channel we expect to be
supported.

>From my individual perspective, I think being able to have data channel
on an individual transport-layer flow (5-tuple) is important to be able
to put QoS treatments on RTP packets within an RTP session separate from
the data channel. Having everything bundled, i.e one RTP session for all
media types combined with the data channel I think have strong support.
This leaves what possibilities one have to combine the data channel with
one out of several RTP sessions?

Cheers

Magnus Westerlund
(As individual)

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------