Last Call: <draft-ietf-rtcweb-stun-consent-freshness-15.txt> (STUN Usage for Consent Freshness) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The IESG has received a request from the Real-Time Communication in
WEB-browsers WG (rtcweb) to consider the following document:
- 'STUN Usage for Consent Freshness'
  <draft-ietf-rtcweb-stun-consent-freshness-15.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-07-16. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

This document was previously last called on May 1 and has been updated as a result of comments submitted during that last call.

Abstract


   To prevent WebRTC applications, such as browsers, from launching
   attacks by sending media to unwilling victims, periodic consent to
   send needs to be obtained from remote endpoints.

   This document describes a consent mechanism using a new Session
   Traversal Utilities for NAT (STUN) usage.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-stun-consent-freshness/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-stun-consent-freshness/ballot/


No IPR declarations have been submitted directly on this I-D.





[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux