RFC 9429: JavaScript Session Establishment Protocol (JSEP)

In plain English — editorial summary, not part of the RFC

This document describes the mechanisms for allowing a JavaScript application to control the signaling plane of a multimedia session via the interface specified in the W3C RTCPeerConnection API and discusses how this relates to existing signaling protocols. This specification obsoletes RFC 8829.

Document record

Document ID

RFC9429

Published

April 2024

Authors

J. Uberti; C. Jennings; E. Rescorla

Status

PROPOSED STANDARD

Stream

IETF

Area

wit

Pages

86

Also known as

—

Obsoletes:

RFC 8829

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC9429

Topics

• webrtc
• sdp
• negotiation
• signaling
• peerconnection
• api
• ice
• rtp
• offer
• answer

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 8858Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)Current

  January 2021

• RFC 8035Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP MultiplexingCurrent

  November 2016

• RFC 8122Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)Updated

  March 2017

• RFC 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current

  December 2016

• RFC 6337Session Initiation Protocol (SIP) Usage of the Offer/Answer ModelCurrent

  August 2011

• RFC 9143Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Current

  February 2022

• RFC 8865T.140 Real-Time Text Conversation over WebRTC Data ChannelsCurrent

  January 2021

• RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent

  January 2021

Also filed under

• PROPOSED STANDARD
• 2024
• IETF stream
• wit area