[rtcweb] RFC 8829 on JavaScript Session Establishment Protocol (JSEP)

rfc-editor@rfc-editor.org Thu, 21 January 2021 00:30 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 606D13A1640; Wed, 20 Jan 2021 16:30:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNmAYh7FUNDk; Wed, 20 Jan 2021 16:30:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5FA43A163E; Wed, 20 Jan 2021 16:30:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7ABF3F4071D; Wed, 20 Jan 2021 16:30:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20210121003006.7ABF3F4071D@rfc-editor.org>
Date: Wed, 20 Jan 2021 16:30:06 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/PMX70NOvlJM0dYz5sIL38u7Ju_Q>
Subject: [rtcweb] =?utf-8?q?RFC_8829_on_JavaScript_Session_Establishment_?= =?utf-8?q?Protocol_=28JSEP=29?=
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 00:30:26 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8829

        Title:      JavaScript Session Establishment Protocol (JSEP) 
        Author:     J. Uberti,
                    C. Jennings,
                    E. Rescorla, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    justin@uberti.name,
                    fluffy@iii.ca,
                    ekr@rtfm.com
        Pages:      95
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-jsep-26.txt

        URL:        https://www.rfc-editor.org/info/rfc8829

        DOI:        10.17487/RFC8829

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 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