Skip to main content

Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness
draft-ietf-rtcweb-stun-consent-freshness-16

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    rtcweb mailing list <rtcweb@ietf.org>,
    rtcweb chair <rtcweb-chairs@ietf.org>
Subject: Protocol Action: 'STUN Usage for Consent Freshness' to Proposed Standard (draft-ietf-rtcweb-stun-consent-freshness-16.txt)

The IESG has approved the following document:
- 'STUN Usage for Consent Freshness'
  (draft-ietf-rtcweb-stun-consent-freshness-16.txt) as Proposed Standard

This document is the product of the Real-Time Communication in
WEB-browsers Working Group.

The IESG contact persons are Ben Campbell, Barry Leiba and Alissa Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-stun-consent-freshness/


Ballot Text

Technical Summary

   In WebRTC contexts, peers send media traffic to each other.
   To prevent attacks on peers, endpoints have to ensure the remote 
   peer is willing to receive traffic.  This is performed both when the
   session is first established to the remote peer and periodically 
    for the duration of the session.  This document defines a method
    for confirming consent using a new STUN usage.

Working Group Summary

One of the consistent issues within the WebRTC ecosystem is
the extent to which requirements from deployed systems impact
the working of the protocol.  In this context, discussion of how
ICE-lite entities should behave consumed a good bit of time, but
I believe that the document represents the WG's general understanding.

After a set of external reviews by directorates the documented was
updated and a new working group last call issued.  No new issues
were identified during the final working group last call.


Document Quality

The document was reviewed by a number of implementors
and implementations are planned or under way.    This document did
not require expert review of the type mentioned above, but Christer
Holmberg's review is called out in the document for its thoroughness.

Personnel

Ted Hardie is the Document Shepherd; Alissa Cooper is the
Responsible Area Director.

RFC Editor Note