Re: [rtcweb] status: draft-ietf-rtcweb-security-arch

Sean Turner <sean@sn3rd.com> Tue, 04 December 2018 14:00 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 1905D130DD5 for <rtcweb@ietfa.amsl.com>; Tue, 4 Dec 2018 06:00:58 -0800 (PST)
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 LPu7ba3HgU8S for <rtcweb@ietfa.amsl.com>; Tue, 4 Dec 2018 06:00:53 -0800 (PST)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 CC0DA126DBF for <rtcweb@ietf.org>; Tue, 4 Dec 2018 06:00:52 -0800 (PST)
Received: by mail-qk1-x734.google.com with SMTP id q70so9631897qkh.6 for <rtcweb@ietf.org>; Tue, 04 Dec 2018 06:00:52 -0800 (PST)
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=/8FMgKWDovOj1jcAXnO4uUmuISBuIdiqTRGzSjbaZmE=; b=S3T6hTCiUMp6uaDLcbIMn5iqy96ihpQjZazQF9BbwjTQuIftPlINASf0wt/1AqoC8V M6KhaC9XKYyrb28G/XbEeWD/OuXq4dK9O2MU8/M5P8jsqWuo+MgJ8k2PqZVYGq7Ec6rz D5udJInice9L/qJu4Ewm9BXHp8NO2eyZ9CdzE=
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=/8FMgKWDovOj1jcAXnO4uUmuISBuIdiqTRGzSjbaZmE=; b=sDXwC88Kj1FpzBGWS8WNWvTR00osqSoqiEPssmGCQu93xynASIQ/2gv3jE5kR0VvRX X2+h0VqMX75DARtzBfJsNIQ7tHd61Z1/rDtwCBjjuLoLEy0DztOP0fMlSkSMt2oBhes8 hGZbkDGe+fiF0+cdtingdsxpFjmjYm9A6HOekTcQ+uJGt6t9rYt2DnJe4oteWx0DS0yO Q/XMILAJhkh6Owk/sjjaaC2MnNQzEX73wDZZeKr3kuwVFUBWjL57eP3NPfGywBkHHlP1 GbKcnId94GEVn1BBfaYvq9jXPSMfu/XrxGeG+BfoptpXZurInRS8585/dZhWxo9Zs2Lo AY7g==
X-Gm-Message-State: AA+aEWYvJpvG8pxQNh6hN3v5ew+9eLxTR0/64gNblQaSKYT9iXC2LLsc 2kmduYbPpu9jZB+afA7ruIT6rQ==
X-Google-Smtp-Source: AFSGD/WCRUF7g2ksJepSWmOtyR4WyRMKOub+njW1KgXqvPfjRWEd/FH0lY4TLfvbDnbDHE2OF6NWRg==
X-Received: by 2002:a37:611:: with SMTP id 17mr18785585qkg.123.1543932051931; Tue, 04 Dec 2018 06:00:51 -0800 (PST)
Received: from [172.16.0.18] ([96.231.221.42]) by smtp.gmail.com with ESMTPSA id 195sm9407607qki.76.2018.12.04.06.00.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Dec 2018 06:00:51 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <00FB4C71-EBD9-4EF6-A3B1-D0C06EA61A53@iii.ca>
Date: Tue, 4 Dec 2018 09:00:50 -0500
Cc: RTCWeb IETF <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A355EC4-A687-44EE-B8F4-CED1D25F1EDA@sn3rd.com>
References: <0293CF6D-9B4F-4680-BBB9-833C33D03013@sn3rd.com> <00FB4C71-EBD9-4EF6-A3B1-D0C06EA61A53@iii.ca>
To: Cullen Jennings <fluffy@iii.ca>, Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/2z0uo7GLhxv8AwqYPwlboB80tiU>
Subject: Re: [rtcweb] status: draft-ietf-rtcweb-security-arch
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: Tue, 04 Dec 2018 14:00:58 -0000

I will have to defer to ekr as I was just throwing in a PR to address this issue:
https://github.com/rtcweb-wg/security-arch/issues/82

spt

> On Dec 3, 2018, at 17:27, Cullen Jennings <fluffy@iii.ca> wrote:
> 
> 
> Why would we want to prohibit false start? I has assumed we could use it for early media. Is there an issue we should be aware of ?
> 
> 
> 
>> On Nov 21, 2018, at 10:54 AM, Sean Turner <sean@sn3rd.com> wrote:
>> 
>> Hi!
>> 
>> We are getting to the point where we be able to move draft-ietf-rtcweb-security-arch
>> (https://datatracker.ietf.org/doc/draft-ietf-rtcweb-security-arch/) to our AD for IETF LC.
>> ekr has noted in PR that follows that false start should be prohibited:
>> 
>> https://github.com/rtcweb-wg/security-arch/issues/82
>> 
>> If there is any concerns with merging addressing this issue please speak up.
>> 
>> Cheers,
>> 
>> stp
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>