IETF Logo Mail Archive

Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-consent-freshness-00.txt

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 20 September 2013 07:51 UTC

Return-Path: <christer.holmberg@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 3323A21F8A38 for <rtcweb@ietfa.amsl.com>; Fri, 20 Sep 2013 00:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.715
X-Spam-Level:
X-Spam-Status: No, score=-5.715 tagged_above=-999 required=5 tests=[AWL=0.534, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 rIxX5Wqd8dM8 for <rtcweb@ietfa.amsl.com>; Fri, 20 Sep 2013 00:51:46 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 986CC21F89FF for <rtcweb@ietf.org>; Fri, 20 Sep 2013 00:51:44 -0700 (PDT)
X-AuditID: c1b4fb25-b7eff8e000000eda-bc-523bfe8a0df1
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 71.2F.03802.A8EFB325; Fri, 20 Sep 2013 09:51:38 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.02.0328.009; Fri, 20 Sep 2013 09:51:38 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-consent-freshness-00.txt
Thread-Index: AQHOtdO3VyArQTGsZUKmwLiEhG8nLZnOPdbA
Date: Fri, 20 Sep 2013 07:51:37 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4A83EA@ESESSMB209.ericsson.se>
References: <20130920073331.2144.40500.idtracker@ietfa.amsl.com>
In-Reply-To: <20130920073331.2144.40500.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUyM+JvjW7XP+sggyfbzSzW/mtnd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxvnJ/9kL9gtWnG/8xdLAeJO3i5GTQ0LARGLu56VsELaYxIV7 64FsLg4hgcOMEkfm3GSHcJYwSsy7/wfI4eBgE7CQ6P6nDdIgIqAucfnhBXYQW1ggWKLj3lcm iHiIxJqjnWwQtpHE+zW9zCA2i4CqRPfD98wgY3gFfCXWH4oCCQsJOEh0zJ/LCGJzCjhKHF5+ kwXEZgS65/upNWAjmQXEJW49mc8EcaeAxJI955khbFGJl4//sYKMlBBQlFjeLwdRriOxYPcn NghbW2LZwtdg5bwCghInZz5hmcAoOgvJ1FlIWmYhaZmFpGUBI8sqRvbcxMyc9HKjTYzAkD+4 5bfqDsY750QOMUpzsCiJ827WOxMoJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgbHy3fz8K+e6 rDc9EPvi82hW7uuwiMq38x1uR786Nftr1U5f/0XXtv9+dPZ1dW0zg5vJle6eaS8rbwjMtHxz aNe88KKM7aX15VUK735kBO7a9y3i6dZd03001Svn5pRYKP4yjv8n+mM6t+mCLsPaU5071l7g eRvDP5/13LKAI69VjrG53lGd/sdYiaU4I9FQi7moOBEAVqVVD0cCAAA=
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-consent-freshness-00.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: Fri, 20 Sep 2013 07:51:53 -0000

Hi,

The draft doesn't mention the case when one entity (e.g. a gateway) is ICE lite. Eventhough ICE already specifies that an ICE lite entity does not send STUN requests, I think it would be good to cover it also for consent refreshness.

Regards,

Christer

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: 20. syyskuuta 2013 10:34
To: i-d-announce@ietf.org
Cc: rtcweb@ietf.org
Subject: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-consent-freshness-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Real-Time Communication in WEB-browsers Working Group of the IETF.

	Title           : STUN Usage for Consent Freshness
	Author(s)       : Muthu Arul Mozhi Perumal
                          Dan Wing
                          Ram Mohan Ravindranath
                          Tirumaleswar Reddy
	Filename        : draft-ietf-rtcweb-stun-consent-freshness-00.txt
	Pages           : 7
	Date            : 2013-09-19

Abstract:
   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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-stun-consent-freshness

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtcweb-stun-consent-freshness-00


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email