RFC 9429 on JavaScript Session Establishment Protocol (JSEP)
rfc-editor@rfc-editor.org Thu, 11 April 2024 19:32 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A456C14F61B; Thu, 11 Apr 2024 12:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level:
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSIPo5I6c4zb; Thu, 11 Apr 2024 12:32:46 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16104C14F610; Thu, 11 Apr 2024 12:32:46 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id F0CCBCE3BD; Thu, 11 Apr 2024 12:32:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9429 on JavaScript Session Establishment Protocol (JSEP)
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240411193245.F0CCBCE3BD@rfcpa.amsl.com>
Date: Thu, 11 Apr 2024 12:32:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/SFKU3LbjX11bbfPviZZroyrAmL4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2024 19:32:50 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9429
Title: JavaScript Session Establishment Protocol (JSEP)
Author: J. Uberti,
C. Jennings,
E. Rescorla, Ed.
Status: Standards Track
Stream: IETF
Date: April 2024
Mailbox: justin@uberti.name,
fluffy@iii.ca,
ekr@rtfm.com
Pages: 86
Obsoletes: RFC 8829
I-D Tag: draft-uberti-rtcweb-rfc8829bis-05.txt
URL: https://www.rfc-editor.org/info/rfc9429
DOI: 10.17487/RFC9429
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.
This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC