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

Harald Alvestrand <harald@alvestrand.no> Mon, 15 December 2014 13:44 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28E431A6FC7 for <rtcweb@ietfa.amsl.com>; Mon, 15 Dec 2014 05:44:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u18BOMcrPRuO for <rtcweb@ietfa.amsl.com>; Mon, 15 Dec 2014 05:44:01 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id 18D3E1A6FB5 for <rtcweb@ietf.org>; Mon, 15 Dec 2014 05:43:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id EB3AE7C36D1 for <rtcweb@ietf.org>; Mon, 15 Dec 2014 14:43:55 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7gS-XfOAz5hC for <rtcweb@ietf.org>; Mon, 15 Dec 2014 14:43:51 +0100 (CET)
Received: from [IPv6:2001:470:de0a:27:1c71:93e8:8434:4216] (unknown [IPv6:2001:470:de0a:27:1c71:93e8:8434:4216]) by mork.alvestrand.no (Postfix) with ESMTPSA id A89737C35B4 for <rtcweb@ietf.org>; Mon, 15 Dec 2014 14:43:51 +0100 (CET)
Message-ID: <548EE596.5090503@alvestrand.no>
Date: Mon, 15 Dec 2014 14:43:50 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <20141215034305.14105.51004.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B1D5C7B1D@ESESSMB208.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5C7B1D@ESESSMB208.ericsson.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/DqzR3ttH9uReqX0QXCHVj26xIHE
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-consent-freshness-10.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 15 Dec 2014 13:44:04 -0000

Den 15. des. 2014 14:24, skrev Christer Holmberg:
> Hi,
> 
> Thank you very much for addressing my comments! :)
> 
> However, I still have an issue with the text saying:
> 
>   	"A WebRTC implementation [I-D.ietf-rtcweb-overview], which implements
>    	full ICE, MUST perform consent freshness test using STUN request/
>    	response as described below:"
> 
> 
> First, I question whether this document should make normative requirements on WebRTC? Shouldn't some WebRTC document instead mandate the usage?
> 

I think this sentence, suitably massaged, belongs in -overview. I'll
make sure it gets there.

> Second, what if a non-WebRTC implementation wants to use the mechanism? The procedures are described below the text above, so the way I read it they only apply to WebRTC implementations.
> 
> Third, *IF* the scope of the mechanism is only WebRTC (perhaps it is, and I have misunderstood), I think we need to have some explicit text indicating that.
> 
> Fourth, if you want to use terminology from [I-D.ietf-rtcweb-overview] you need to make sure it's aligned with that draft. I don't think "WebRTC implementation" exists in draft-rtcweb-overview-13, so you would have to define that as a browser, non-browser or compatible endpoint (or, use those terminologies).
> 

The correct nomenclature at the moment is "WebRTC endpoint", which
contains both browsers and non-browsers.


> Thanks!
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> 
> 
> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: 15. joulukuuta 2014 5:43
> To: i-d-announce@ietf.org
> Cc: rtcweb@ietf.org
> Subject: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-consent-freshness-10.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
>         Authors         : Muthu Arul Mozhi Perumal
>                           Dan Wing
>                           Ram Mohan Ravindranath
>                           Tirumaleswar Reddy
>                           Martin Thomson
> 	Filename        : draft-ietf-rtcweb-stun-consent-freshness-10.txt
> 	Pages           : 9
> 	Date            : 2014-12-14
> 
> Abstract:
>    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 Session
>    Traversal Utilities for NAT (STUN) usage.
> 
> 
> 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-10
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-stun-consent-freshness-10
> 
> 
> 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
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>