RFC 7675: Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness

To prevent WebRTC applications, such as browsers, from launching attacks by sending traffic to unwilling victims, periodic consent to send needs to be…

Read RFC 7675 on the RFC Editor

Outgoing relationships (10 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5389: Session Traversal Utilities for NAT (STUN)
Normative reference — RFC 5245: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
Informative reference — RFC 3830: MIKEY: Multimedia Internet KEYing
Informative reference — RFC 4568: Session Description Protocol (SDP) Security Descriptions for Media Streams
Informative reference — RFC 4953: Defending TCP Against Spoofing Attacks
Informative reference — RFC 5961: Improving TCP's Robustness to Blind In-Window Attacks
Informative reference — RFC 6062: Traversal Using Relays around NAT (TURN) Extensions for TCP Allocations
Informative reference — RFC 6263: Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol (RTCP) Flows
Informative reference — RFC 7350: Datagram Transport Layer Security (DTLS) as Transport for Session Traversal Utilities for NAT (STUN)

Incoming relationships (4 related RFCs)

Normatively referenced by — RFC 8827: WebRTC Security Architecture
Normatively referenced by — RFC 8862: Best Practices for Securing RTP Media Signaled with SIP
Informatively referenced by — RFC 8839: Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)
Informatively referenced by — RFC 8826: Security Considerations for WebRTC