RFC 7675: Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness
In plain English — editorial summary, not part of the RFC
To prevent WebRTC applications, such as browsers, from launching attacks by sending traffic 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.
Document record
- Document ID
- RFC7675
- Published
- October 2015
- Authors
- M. Perumal; D. Wing; R. Ravindranath; T. Reddy; M. Thomson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7478Web Real-Time Communication Use Cases and RequirementsCurrent
March 2015
- RFC 7875Additional WebRTC Audio Codecs for InteroperabilityCurrent
May 2016
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
- RFC 9725WebRTC-HTTP Ingestion Protocol (WHIP)Current
March 2025
- RFC 7635Session Traversal Utilities for NAT (STUN) Extension for Third-Party AuthorizationCurrent
August 2015
- RFC 8836Congestion Control Requirements for Interactive Real-Time MediaCurrent
January 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?