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

"Karl Stahl" <> Fri, 11 April 2014 10:49 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E31E81A01CE for <>; Fri, 11 Apr 2014 03:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MSGID_MULTIPLE_AT=1] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SnbZVdTR3Vof for <>; Fri, 11 Apr 2014 03:49:43 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 403E71A00FB for <>; Fri, 11 Apr 2014 03:49:42 -0700 (PDT)
Received: from ([]) by (Telecom3 SMTP service) with ASMTP id 201404111249387034; Fri, 11 Apr 2014 12:49:38 +0200
From: Karl Stahl <>
To: 'Harald Alvestrand' <>,
References: <> <> <>
In-Reply-To: <>
Date: Fri, 11 Apr 2014 12:49:44 +0200
Message-ID: <014201cf5573$c02ae3b0$4080ab10$@stahl>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: sv
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-consent-freshness-02.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: Fri, 11 Apr 2014 10:49:46 -0000


Just remembered regarding ICE Lite in your transport document; I think your
statement regarding ICE, not ICE Lite therein, should be clarified so it is
understood that browsers must (also) operate against ICE Lite devices
(typical for a gateway).

(That is the way it already works in Chrome - buggy in Firefox though)

-----Ursprungligt meddelande-----
Från: rtcweb [] För Christer Holmberg
Skickat: den 11 april 2014 08:52
Till: Ram Mohan R (rmohanr);
Ämne: Re: [rtcweb] I-D Action:


I think it would be good to have some text about usage of consent freshness
when one entity is ICE lite.

And, I think it would be good to make it more clear that the usage of
consent is always negotiated per direction.




-----Original Message-----
From: rtcweb [] On Behalf Of Ram Mohan R
Sent: 11. huhtikuuta 2014 8:01
Subject: Re: [rtcweb] I-D Action:

Summary of changes in this revision

Addressed the comments received from the WG.
Removed the timers definition from solution overview and made the text more
Incorporated text from draft-thomson-rtcweb-consent.
Most of the text of solution overview is re-written however the idea is
still kept intact

Comments are welcome.

There is still some dangling reference (text) to SRTP/DTLS mechanism for
consent which we will modify in the next revision


-----Original Message-----
From: "" <>
Date: Friday, 11 April 2014 9:07 am
To: "" <>
Cc: "" <>
Subject: [rtcweb] I-D Action:

>A New Internet-Draft is available from the on-line Internet-Drafts 
> 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
>        Authors         : Muthu Arul Mozhi Perumal
>                          Dan Wing
>                          Ram Mohan Ravindranath
>                          Tirumaleswar Reddy
>                          Martin Thomson
>	Filename        : draft-ietf-rtcweb-stun-consent-freshness-02.txt
>	Pages           : 8
>	Date            : 2014-04-10
>   To prevent sending excessive traffic to an endpoint, periodic consent
>   needs to be obtained from that remote endpoint.
>   This document describes a consent mechanism using a new STUN usage.
>   This same mechanism can also determine connection loss ("liveness")
>   with a remote peer.
>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:
>Please note that it may take a couple of minutes from the time of 
>submission until the htmlized version and diff are available at 
>Internet-Drafts are also available by anonymous FTP at:
>rtcweb mailing list

rtcweb mailing list

rtcweb mailing list