[rtcweb] FW: I-D Action: draft-muthu-behave-consent-freshness-03.txt

"Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com> Tue, 26 February 2013 15:06 UTC

Return-Path: <mperumal@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 48D8A21F8A67 for <rtcweb@ietfa.amsl.com>; Tue, 26 Feb 2013 07:06:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id mpgw2IcPTa0Z for <rtcweb@ietfa.amsl.com>; Tue, 26 Feb 2013 07:06:51 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id 654B021F887D for <rtcweb@ietf.org>; Tue, 26 Feb 2013 07:06:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2584; q=dns/txt; s=iport; t=1361891211; x=1363100811; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=0VfI5n0gO6OHbDNSKenCvmJVqoD3+8OXLw0FaOWQq+E=; b=BsyRb1yUZzNbn0myk4CdbYl2naDGTx8S1A5g2KSZckP0xJBItDo9SSWr 5m0VxXXsWb7er9qc6xepCSVBAYaFXvlct65kPqnZgoqZWRL40qmi44+dl PKqPq2Mk8XpzAO+WCKxvwlmu6+43i4YaLvC0rCrw3PmVqiWq4qSCEQOnq c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.84,740,1355097600"; d="scan'208";a="181112159"
Received: from rcdn-core2-6.cisco.com ([]) by rcdn-iport-1.cisco.com with ESMTP; 26 Feb 2013 15:06:51 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com []) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r1QF6ovl025390 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtcweb@ietf.org>; Tue, 26 Feb 2013 15:06:50 GMT
Received: from xmb-rcd-x02.cisco.com ([]) by xhc-rcd-x09.cisco.com ([]) with mapi id 14.02.0318.004; Tue, 26 Feb 2013 09:06:50 -0600
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: I-D Action: draft-muthu-behave-consent-freshness-03.txt
Thread-Index: AQHOE4XKyq5tIRCRdE+e+ktRkS0KtZiMOJFw
Date: Tue, 26 Feb 2013 15:06:49 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE224023E19@xmb-rcd-x02.cisco.com>
References: <20130225182705.666.1653.idtracker@ietfa.amsl.com>
In-Reply-To: <20130225182705.666.1653.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [rtcweb] FW: I-D Action: draft-muthu-behave-consent-freshness-03.txt
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: Tue, 26 Feb 2013 15:06:52 -0000


This draft was presented in RTCWEB during IETF 83.5 and 84 and was discussed earlier in the BEHAVE and RTCWEB mailing lists. Most of the comments received and consensus reached so far have been incorporated (as a result the draft has been trimmed). It now also has a section on the W3C API implications.

Is the draft heading in the right direction? Given that it just describes a STUN usage for performing consent freshness and liveness test and provides recommendations for the W3C APIs, would RTCWEB be a better home for this draft?

Comments welcome.

- Authors

-----Original Message-----
From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Monday, February 25, 2013 11:57 PM
To: i-d-announce@ietf.org
Subject: I-D Action: draft-muthu-behave-consent-freshness-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : STUN Usage for Consent Freshness
	Author(s)       : Muthu Arul Mozhi Perumal
                          Dan Wing
                          Ram Mohan Ravindranath
                          Hadriel Kaplan
	Filename        : draft-muthu-behave-consent-freshness-03.txt
	Pages           : 7
	Date            : 2013-02-25

   Verification of peer consent before sending traffic is necessary in
   WebRTC deployments to ensure that a malicious JavaScript cannot use
   the browser as a platform for launching attacks.  A related problem
   is session liveness.  WebRTC applications may want to detect
   connection failure and take appropriate actions.  This document
   describes a STUN usage that enables a WebRTC browser to perform the
   following on a candidate pair ICE is using for a media component
   after session establishment:

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Internet-Drafts are also available by anonymous FTP at:

I-D-Announce mailing list
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt