[rtcweb] Where to specify ICE usage and the common transport

Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 04 July 2012 07:00 UTC

Return-Path: <magnus.westerlund@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 816F011E812C for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2012 00:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.223
X-Spam-Level:
X-Spam-Status: No, score=-106.223 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 4BVrgqSRAkFH for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2012 00:00:52 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 67ABA11E8129 for <rtcweb@ietf.org>; Wed, 4 Jul 2012 00:00:51 -0700 (PDT)
X-AuditID: c1b4fb30-b7fb46d0000064f2-0b-4ff3ea2c06c4
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 95.AD.25842.C2AE3FF4; Wed, 4 Jul 2012 09:01:00 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.264.0; Wed, 4 Jul 2012 09:00:59 +0200
Message-ID: <4FF3EA29.7090504@ericsson.com>
Date: Wed, 04 Jul 2012 09:00:57 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPJMWRmVeSWpSXmKPExsUyM+Jvra7Oq8/+BpOeyVus/dfO7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujBW/fzEWdPFULNl/k7WB8SlnFyMnh4SAicTBp/PYIGwxiQv3 1gPZXBxCAqcYJVYe/cEI4SxjlLj56QY7SBWvgLbEgxczmEBsFgEViavProPZbAIWEjd/NIJN EhUIlpg2/R5UvaDEyZlPWEBsEQF1icsPL4DFhQVsJHqXHmeG2Cwpca99NVgvs4CexJSrLYwQ trxE89bZYDVCQHsbmjpYJzDyz0IydhaSlllIWhYwMq9iFM5NzMxJLzfXSy3KTC4uzs/TK07d xAgMtINbfhvsYNx0X+wQozQHi5I4r57qfn8hgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjEH1 vF6p5T77RZ2CrJhnnZoSrxO39NO5hjzTywbcB/kVVzRP1z6+/IC2bFJu7Q5WdsXgRXb+33Lk Ba5ceqz9LOHVehM9oVgRSfNr735dPzgn/37zC5vKqh/OulHO5S8XRlW/uCOyJmHhVOX/+js2 irVEZy3NDvgooJy+8YXMmvijpxYySZ++r8RSnJFoqMVcVJwIAPj7/8MCAgAA
Subject: [rtcweb] Where to specify ICE usage and the common transport
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, 04 Jul 2012 07:00:52 -0000

WG,

We chairs have identified that we currently we are missing specification
text for one of the key components of RTCWEB. This component is how
WebRTC uses ICE and defines the datagram transport that both the
DTLS/SCTP data channel uses and the RTP session.

Such a specification would most likely contain the following:

- How ICE is used in the WebRTC context
- Inclusion of STUN, TURN, TURN-TCP
- Inclusion of any defined "HTTP fallback"
- Description of the data transport in general and specifically how one
  can separate the traffic from the data channel and RTP session.
- Requirements on the signalling and API and what configuration data is
  needed.

My personal view is that this is best served by having its own
specification. Alternatives that exist is to include it either in the
data channel or RTP usage specifications.

Thus we chairs would appreciate feedback on at least two things:

- Is specifying this in its own specification the most suitable approach

- Do we have any volunteers for writing such a specification?

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------