IETF Logo Mail Archive

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

Adam Roach <adam@nostrum.com> Fri, 21 December 2018 23:13 UTC

Return-Path: <adam@nostrum.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 34567130EB8 for <rtcweb@ietfa.amsl.com>; Fri, 21 Dec 2018 15:13:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.68
X-Spam-Level:
X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 mvSiDM5dUICj for <rtcweb@ietfa.amsl.com>; Fri, 21 Dec 2018 15:13:05 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 1DB1A130EB3 for <rtcweb@ietf.org>; Fri, 21 Dec 2018 15:13:05 -0800 (PST)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wBLND1WQ057973 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 21 Dec 2018 17:13:03 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1545433984; bh=Sv1oYAX9ofW+kYQ0CUV5BBh6DcPcR8t0jUukZeuQzwE=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=eA9raU6xQUhpcVfCWH92uWzlcSk4c45vUMrEL6suf7iChmUgKbo3Erx2OOHmocEAS ARSq5kNbcT2lTwZ6wTB1aR3eB7yDgPps20GZ5CAj9msRA9oLAQlTky/dSp0SIirf18 CysjGKP8dtJkltoBrGfC8c1rVG1cEs38fFnfyJU0=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: Sean Turner <sean@sn3rd.com>, Cullen Jennings <fluffy@iii.ca>, Eric Rescorla <ekr@rtfm.com>
Cc: RTCWeb IETF <rtcweb@ietf.org>
References: <0293CF6D-9B4F-4680-BBB9-833C33D03013@sn3rd.com> <00FB4C71-EBD9-4EF6-A3B1-D0C06EA61A53@iii.ca> <9A355EC4-A687-44EE-B8F4-CED1D25F1EDA@sn3rd.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <b94f917a-5486-e53e-1602-09a1b372cb2b@nostrum.com>
Date: Fri, 21 Dec 2018 17:12:56 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <9A355EC4-A687-44EE-B8F4-CED1D25F1EDA@sn3rd.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/lM3q0N_pQkjMpWp57uWdqFqmUFM>
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: Fri, 21 Dec 2018 23:13:06 -0000

EKR / Fluffy -- can we come to closure on this?

/a

On 12/4/18 8:00 AM, Sean Turner wrote:
> 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
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email