IETF Logo Mail Archive

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

"Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com> Wed, 04 July 2012 07:36 UTC

Return-Path: <mperumal@cisco.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 07D1121F8799 for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2012 00:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 Xu5zvX7IMcNx for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2012 00:36:25 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 0512621F8795 for <rtcweb@ietf.org>; Wed, 4 Jul 2012 00:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mperumal@cisco.com; l=2397; q=dns/txt; s=iport; t=1341387395; x=1342596995; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=/MzGym75XYhaTPrF5V1ZaeRnJz8Vnq2BbCKKlc8LmS8=; b=XmqAJSfB7omkJCKHk+gSiisMHkSYO74XehYnL2+97c6+nburhb40ZKlg SxUp9FpS19U046+mUz6LOpUS0mu0dJ0WL0W7xMbqeATtybW3l3/bbT1sM F/o8MjSz2Se2thVjT4u3D1gdJ8op8c5O/uZq7CVc7128NMenDepSpxTOc Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EADHx80+tJV2c/2dsb2JhbABEtyCBB4IYAQEBBAEBAQkGAVsXAgICAQgRBAEBCx0HGwwLFAkIAgQBEggah2kLmhSgRgQEizWFV2ADiBebPYFmgl8
X-IronPort-AV: E=Sophos;i="4.77,520,1336348800"; d="scan'208";a="98669340"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP; 04 Jul 2012 07:36:34 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id q647aYJi022243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Jul 2012 07:36:34 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.192]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0298.004; Wed, 4 Jul 2012 02:36:34 -0500
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Where to specify ICE usage and the common transport
Thread-Index: AQHNWbLSqHcZgCkhb0KVzPBA2p9XJ5cYuDMA
Date: Wed, 04 Jul 2012 07:36:33 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE20129FC7B@xmb-rcd-x02.cisco.com>
References: <4FF3EA29.7090504@ericsson.com>
In-Reply-To: <4FF3EA29.7090504@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.39.69.122]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19016.003
x-tm-as-result: No--39.263100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [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:36:26 -0000

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

Yes, IMO. I think it would ensue we get enough focus on this key component.

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

Please count me in. I think it makes sense to merge the consent freshness specification (draft-muthu-behave-consent-freshness) with the ICE usage for WebRTC.

Muthu

|-----Original Message-----
|From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Magnus Westerlund
|Sent: Wednesday, July 04, 2012 12:31 PM
|To: rtcweb@ietf.org
|Subject: [rtcweb] Where to specify ICE usage and the common transport
|
|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
|----------------------------------------------------------------------
|
|
|_______________________________________________
|rtcweb mailing list
|rtcweb@ietf.org
|https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email