Re: [rtcweb] WG Last Call for draft-ietf-rtcweb-stun-consent-freshness

On 08/20/2014 06:09 AM, Muthu Arul Mozhi Perumal wrote:
> I believe draft-ietf-rtcweb-stun-consent-freshness deals with the
> WebRTC browser. A WebRTC device (eg. a mobile phone) on the other
> hand, could run a WebRTC browser and a JS and perform consent.
> Similarly, a WebRTC endpoint (whatever that gets defined as) might
> also perform consent, while a WebRTC gateway might not, and how
> consent applies to those should get specified in the document(s) that
> define those requirements (note: the gateway referred to in
> draft-ietf-rtcweb-stun-consent-freshness is any SIP gateway).

Note: In terms of conformance requirements, "might" and "might not" are
completely equivalent (2119 style: MAY - there is no MAY NOT).

>
> So, draft-ietf-rtcweb-stun-consent-freshness should just replace
> WebRTC endpoint and WebRTC implementation with WebRTC browser, IMHO.
>
> Muthu
>
> On Tue, Aug 19, 2014 at 7:36 PM, Christer Holmberg
> <christer.holmberg@ericsson.com
> <mailto:christer.holmberg@ericsson.com>> wrote:
>
>     Hi,
>
>      
>
>     The draft says:
>
>      
>
>     “WebRTC endpoints are required to support full ICE as specified in
>
>                     section 3.4 of [I-D.
>
>      
>     ietf-rtcweb-transports].  However, when WebRTC
>
>                     endpoints interwork with other endpoints that
>     support only ICE-lite
>
>                     (e.g., gateways) those endpoints will not generate
>     consent checks,
>
>                     but just respond to consent checks they receive.”
>
>      
>
>     The draft also talks about “WebRTC implementations” and “WebRTC
>     browsers”.
>
>      
>
>     We need to make sure that the terminology is aligned with
>     draft-ietf-rtcweb-overview (for example,
>
>      
>     draft-ietf-rtcweb-overview does not talk about “WebRTC
>     endpoints”), which also may be impacted based on the outcome of
>     the current terminology/gateway discussion.
>
>      
>
>     Regards,
>
>      
>
>     Christer
>
>      
>
>      
>
>     *From:*rtcweb [mailto:rtcweb-bounces@ietf.org
>     <mailto:rtcweb-bounces@ietf.org>] *On Behalf Of *Ted Hardie
>     *Sent:* 14. elokuuta 2014 18:10
>     *To:* rtcweb@ietf.org <mailto:rtcweb@ietf.org>; Sean Turner;
>     Cullen Jennings
>     *Subject:* [rtcweb] WG Last Call for
>     draft-ietf-rtcweb-stun-consent-freshness
>
>      
>
>     This starts a WG Last Call for
>     draft-ietf-rtcweb-stun-consent-freshness (available at
>     http://datatracker.ietf.org/doc/draft-ietf-rtcweb-stun-consent-freshness/). 
>     Please review the document and send comments to the list by
>     September 10, 2014.
>
>     thanks,
>
>     Ted Hardie
>
>
>     _______________________________________________
>     rtcweb mailing list
>     rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

-- 
Surveillance is pervasive. Go Dark.