Re: [rtcweb] New Version Notification for draft-ietf-rtcweb-stun-consent-freshness-01.txt

"Muthu Arul Mozhi Perumal (mperumal)" <> Mon, 24 March 2014 02:17 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id AF4921A00B0 for <>; Sun, 23 Mar 2014 19:17:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9XLu3Ym4q_OC for <>; Sun, 23 Mar 2014 19:17:14 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B23DA1A00AA for <>; Sun, 23 Mar 2014 19:17:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2698; q=dns/txt; s=iport; t=1395627434; x=1396837034; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=8IJGsSU4dl1NQlSfrDufrUyGfO+QkVusRfKG2Ejcpfg=; b=GwxdE5drfDnFrXV6aokFiYnvagmc4pKlBVz/6csTLkIVaaTJ9iDxpSTF UMA5DDkpTo4ifeCLSAlwCjHZRZJCeoWkaBAFq2XhLScPm5KJFXcL6BgAO 0QmJmNERQFeIAU5jup6EwNjYHoe5vnIF46pg7gxk4QmQlWVkUJDr/wUKE w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.97,717,1389744000"; d="scan'208";a="312133678"
Received: from ([]) by with ESMTP; 24 Mar 2014 02:17:14 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id s2O2HDlw027674 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <>; Mon, 24 Mar 2014 02:17:13 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Sun, 23 Mar 2014 21:17:13 -0500
From: "Muthu Arul Mozhi Perumal (mperumal)" <>
To: "" <>
Thread-Topic: New Version Notification for draft-ietf-rtcweb-stun-consent-freshness-01.txt
Thread-Index: AQHPRwa2vIYR3llUgEyGbYR9f83oiZrvf+JA
Date: Mon, 24 Mar 2014 02:17:12 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [rtcweb] New Version Notification for draft-ietf-rtcweb-stun-consent-freshness-01.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 24 Mar 2014 02:17:17 -0000

This is just a keepalive version while we are working on updating the draft based on WG discussions..


|-----Original Message-----
|From: []
|Sent: Monday, March 24, 2014 7:44 AM
|To: Ram Mohan R (rmohanr); Tirumaleswar Reddy (tireddy); Dan Wing (dwing); Tirumaleswar Reddy
|(tireddy); Muthu Arul Mozhi Perumal (mperumal); Ram Mohan R (rmohanr); Dan Wing (dwing); Muthu Arul
|Mozhi Perumal (mperumal)
|Subject: New Version Notification for draft-ietf-rtcweb-stun-consent-freshness-01.txt
|A new version of I-D, draft-ietf-rtcweb-stun-consent-freshness-01.txt
|has been successfully submitted by Muthu Arul Mozhi Perumal and posted to the
|IETF repository.
|Name:		draft-ietf-rtcweb-stun-consent-freshness
|Revision:	01
|Title:		STUN Usage for Consent Freshness
|Document date:	2014-03-24
|Group:		rtcweb
|Pages:		7
|   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 application may want to detect
|   connection failure and take appropriate action.
|   This document describes how a WebRTC browser can verify peer consent
|   to continue sending traffic and detect connection failure.
|Please note that it may take a couple of minutes from the time of submission
|until the htmlized version and diff are available at
|The IETF Secretariat