IETF Logo Mail Archive

Re: [rtcweb] RFC 9429 on JavaScript Session Establishment Protocol (JSEP)

Sean Turner <sean@sn3rd.com> Fri, 12 April 2024 14:01 UTC

Return-Path: <sean@sn3rd.com>
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 0090DC14F68F for <rtcweb@ietfa.amsl.com>; Fri, 12 Apr 2024 07:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 QnckPhZfSUjg for <rtcweb@ietfa.amsl.com>; Fri, 12 Apr 2024 07:01:22 -0700 (PDT)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 ADCB1C14F5E8 for <rtcweb@ietf.org>; Fri, 12 Apr 2024 07:01:22 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id af79cd13be357-78d62c1e82bso55376185a.3 for <rtcweb@ietf.org>; Fri, 12 Apr 2024 07:01:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; t=1712930481; x=1713535281; darn=ietf.org; h=to:in-reply-to:references:message-id:date:subject:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=gZ7uEoRyPwzQPHQChTPQX7igRaOQJTE59GkVkR+AFwU=; b=c5UFwYfYtAtzD7Yq2i02rGDPdih9nEM4U2/aK3XtfMAFd25Ppa8+rfdwgwrIzpVojg fUGI83nFfhlE8CvPBM7C2PSmxp5AEodnnRt3pdA/84FgzLzF7yUtHPef/SiXk2oxenJO 85i5asfjH1MCdGK3eMW7Dc2AENCqSaHmdqVjg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712930481; x=1713535281; h=to:in-reply-to:references:message-id:date:subject:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=gZ7uEoRyPwzQPHQChTPQX7igRaOQJTE59GkVkR+AFwU=; b=Jhz4pKVSLAbkPPJ/jVOLwaG0LWfSRCSOQEJLu6ZwUC7xlP9a9XS2mMbsjkELJ/nKfi 3Cbl+2THL28219+GQzF/rZrIbt7ZWSm3j8pBej8isCat8nc/HVHCwnTbZhDEqSAEQRXq 8IKpbT3kGU33fGDfwE6K6sIYZhIL4k6W4lFQ96TUiRH08WmCyQl/BbenZwyW7EGFMWfw oEdKpDMA3zDZP6LAgI0VuF/SWQA/KbO/5iEhrEvf8E9t29ug8M8nBunPsGns3rotcrpK Ysyy8dqmUWfmXbCV5XU8BL2c3Z5LJCG6cUDQe0i8dL5B2jYsrHNVUTPFFjOoUm0F9NX8 YWrQ==
X-Gm-Message-State: AOJu0Yy/wB/dKf1qilHkBlxfvafIGk3VPEAMHgCYCPWwniv+L7mWm5mT hFmIkKi7UTkVHLJ4gpj3/+2zUZQuEz9+NmS7gCA9diU2LZV8PHunTrmb82P14lBVch67cYgWvtw O
X-Google-Smtp-Source: AGHT+IEbzuAfPZpuqzkF+zKohah6YcB8L8xUwjkki1I5vSY0p7xlZ2BPqkublpAH0YlNr6dz+4Cj8Q==
X-Received: by 2002:a05:6214:400a:b0:69b:30f6:d567 with SMTP id kd10-20020a056214400a00b0069b30f6d567mr2793981qvb.58.1712930481106; Fri, 12 Apr 2024 07:01:21 -0700 (PDT)
Received: from smtpclient.apple ([2600:381:5a0f:fc2a:7816:407e:fbe9:9ad0]) by smtp.gmail.com with ESMTPSA id x10-20020ae9e90a000000b0078d6d22a0c3sm2420564qkf.90.2024.04.12.07.01.20 for <rtcweb@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 12 Apr 2024 07:01:20 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Sean Turner <sean@sn3rd.com>
Mime-Version: 1.0 (1.0)
Date: Fri, 12 Apr 2024 10:01:08 -0400
Message-Id: <F34A843C-051D-42C8-A052-26544EF366AC@sn3rd.com>
References: <20240411193245.F0CCBCE3BD@rfcpa.amsl.com>
In-Reply-To: <20240411193245.F0CCBCE3BD@rfcpa.amsl.com>
To: rtcweb@ietf.org
X-Mailer: iPhone Mail (21E236)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/oduI66LryIVBgEtSBpqtKqmMogI>
Subject: Re: [rtcweb] RFC 9429 on JavaScript Session Establishment Protocol (JSEP)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 12 Apr 2024 14:01:28 -0000

Thanks to everybody who helped get this done!

spt

Sent from my iPhone

> On Apr 11, 2024, at 15:33, rfc-editor@rfc-editor.org wrote:
> 
> 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
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email