IETF Logo Mail Archive

Re: [rtcweb] WebRTC REF for OAUTH based TURN

Sean Turner <sean@sn3rd.com> Tue, 13 March 2018 17:53 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 8F7F31271FD for <rtcweb@ietfa.amsl.com>; Tue, 13 Mar 2018 10:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yG-4Vkr8X3k0 for <rtcweb@ietfa.amsl.com>; Tue, 13 Mar 2018 10:53:56 -0700 (PDT)
Received: from mail-pl0-x22c.google.com (mail-pl0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA296124C27 for <rtcweb@ietf.org>; Tue, 13 Mar 2018 10:53:55 -0700 (PDT)
Received: by mail-pl0-x22c.google.com with SMTP id ay1-v6so239314plb.7 for <rtcweb@ietf.org>; Tue, 13 Mar 2018 10:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PFy5f8dBu9xjKPYVh3DVNZhCldidt4MwQXKVCzzsmic=; b=fr2DYQsFsu1NxvvW1P/T03AmGuevkZQzJr7J+m6aujpwhj6Qxvhe/gt7XlWdM/xBk+ zqRxJbsJcyw9wUQvwNnmiHDe/KI1LXWKzORJSoiBnUqreg1QXTpNLj3CXwCZ7dMo/Xyv U1/fkUWp2VMRXjnLGIwBmY1mtCBCZazSVCvJc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PFy5f8dBu9xjKPYVh3DVNZhCldidt4MwQXKVCzzsmic=; b=q766XuHMGt/50aJGGmo8dUeWAQK7vzd42x/dBXfyzumOH3WMxLLVEy2m8MdvxtT0Je aa6mz9VOL5CGhX9Nj4qkWy1O3Ol9tI2E1RySDEDbG/NXkUnmTKhkJprjWkFf6CUNaGNP jtG96HPUhHYkko6kZ8QQdXUlxYQiC9PDB+3qz6bbZauwc3W2VLt5Y2W0sajBOS3aGtoJ NpU5wgh65zPX/NGAcllblEsJ7fMPk133sdeChNVhEQ128t2GAd24E9F8NBOXRCf9axD6 W59MMD77XyBLEW/RYUu/ifJOpalGCyoAAFZscbvohIO2PKpr5K4g02OuOr5pT+wWVj2U Xr7g==
X-Gm-Message-State: AElRT7HBQM3mC4xkpCDAeHYQ8QhEdm7RAwVk3NI4ieXHrkPSQS4oYFIP mtDqX5IAYn6JDB0iSEM3He3lcQ==
X-Google-Smtp-Source: AG47ELurrnDuQx5IMjViSkOKCt7pjOSaaZ7B+MIK/vBroqp+OH3ggMSZg9bz8mAg2dbCTtkBsCIS4g==
X-Received: by 2002:a17:902:7883:: with SMTP id q3-v6mr1262176pll.361.1520963635579; Tue, 13 Mar 2018 10:53:55 -0700 (PDT)
Received: from [5.5.33.141] (vpn.snozzages.com. [204.42.252.17]) by smtp.gmail.com with ESMTPSA id h26sm1176337pgv.22.2018.03.13.10.53.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Mar 2018 10:53:54 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <2C22A535-0F8D-496D-B8BF-C74ACB17958C@iii.ca>
Date: Tue, 13 Mar 2018 17:53:47 +0000
Cc: WebRTC WG <public-webrtc@w3.org>, RTCWeb IETF <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <500B1FA0-26D7-4DE5-9DC3-0180A1CA24C7@sn3rd.com>
References: <2C22A535-0F8D-496D-B8BF-C74ACB17958C@iii.ca>
To: Cullen Jennings <fluffy@iii.ca>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/y-sPNK16LcEZG9n6dWdWPL_PMDE>
Subject: Re: [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 17:53:57 -0000

I believe that
draft-ietf-oauth-pop-key-distribution
morphed into:
draft-ietf-ace-cwt-proof-of-possession/
I will double check with the ace chairs.

There is one downref to draft-ietf-ace-cbor-web-token, but it’s state is now "Approved-announcement to be sent::Revised I-D Needed for 5 days”

spt


> On Mar 13, 2018, at 14:14, Cullen Jennings <fluffy@iii.ca> wrote:
> 
> 
> 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 ?
> 
> 
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email