IETF Logo Mail Archive

[rtcweb] WebRTC REF for OAUTH based TURN

Cullen Jennings <fluffy@iii.ca> Tue, 13 March 2018 14:14 UTC

Return-Path: <fluffy@iii.ca>
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 2FD03127444 for <rtcweb@ietfa.amsl.com>; Tue, 13 Mar 2018 07:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 Rc73QbxhKxOZ for <rtcweb@ietfa.amsl.com>; Tue, 13 Mar 2018 07:14:25 -0700 (PDT)
Received: from smtp89.ord1d.emailsrvr.com (smtp89.ord1d.emailsrvr.com [184.106.54.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6030124B0A for <rtcweb@ietf.org>; Tue, 13 Mar 2018 07:14:25 -0700 (PDT)
Received: from smtp20.relay.ord1d.emailsrvr.com (localhost [127.0.0.1]) by smtp20.relay.ord1d.emailsrvr.com (SMTP Server) with ESMTP id 05E38C0065; Tue, 13 Mar 2018 10:14:25 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp20.relay.ord1d.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id BF030C0098; Tue, 13 Mar 2018 10:14:24 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.91] (S0106004268479ae3.cg.shawcable.net [70.77.44.153]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:25 (trex/5.7.12); Tue, 13 Mar 2018 10:14:25 -0400
From: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Tue, 13 Mar 2018 08:14:23 -0600
Message-Id: <2C22A535-0F8D-496D-B8BF-C74ACB17958C@iii.ca>
To: WebRTC WG <public-webrtc@w3.org>, RTCWeb IETF <rtcweb@ietf.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/NExmatwJyoduZyXaIT5gpkY2wI8>
Subject: [rtcweb] WebRTC REF for OAUTH based TURN
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 13 Mar 2018 14:14:27 -0000

From a dependency point of view, I would like to note that right now the WebRTC PC spec references

* draft-ietf-oauth-pop-key-distribution

Which rumor has it has been replaced by 

* datatracker.ietf.org/doc/draft-ietf-ace-oauth-authz

Which normatively references the following:

* draft-ietf-ace-cbor-web-token
* ietf-ace-cwt-proof-of-possession
* draft-ietf-ace-cbor-web-token
* draft-ietf-ace-cwt-proof-of-possession

More discussion of this at https://github.com/w3c/webrtc-pc/issues/1642

What needs to happen with all this so we can finish up the stuff WebRTC needs to reference from IETF ?

v2.23.0 | Report a Bug | By Email