RFC 7584: Session Traversal Utilities for NAT (STUN) Message Handling for SIP Back-to-Back User Agents (B2BUAs)
In plain English — editorial summary, not part of the RFC
Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs) are often designed to be on the media path rather than just intercepting signaling. This means that B2BUAs often act on the media path leading to separate media legs that the B2BUA correlates and bridges together. When acting on the media path, B2BUAs are likely to receive Session Traversal Utilities for NAT (STUN) packets as part of Interactive Connectivity Establishment (ICE) processing. This document defines behavior for a B2BUA performing ICE processing. The goal of this document is to ensure that B2BUAs properly handle SIP messages that carry ICE semantics in Session Description Protocol (SDP) and STUN messages received as part of the ICE procedures for NAT and Firewall traversal of multimedia sessions.
Document record
- Document ID
- RFC7584
- Published
- July 2015
- Authors
- R. Ravindranath; T. Reddy; G. Salgueiro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7587RTP Payload Format for the Opus Speech and Audio CodecCurrent
June 2015
- RFC 7578Returning Values from Forms: multipart/form-dataCurrent
July 2015
- RFC 7573Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat SessionsCurrent
June 2015
- RFC 7595Guidelines and Registration Procedures for URI SchemesUpdated
June 2015
- RFC 7572Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant MessagingCurrent
June 2015
- RFC 7601Message Header Field for Indicating Message Authentication StatusObsoleted
August 2015
- RFC 7565The 'acct' URI SchemeCurrent
May 2015
- RFC 7564PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application ProtocolsObsoleted
May 2015
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?