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

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
> 