IETF Logo Mail Archive

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

Cullen Jennings <fluffy@iii.ca> Mon, 03 December 2018 22:27 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 B3D78130DF5 for <rtcweb@ietfa.amsl.com>; Mon, 3 Dec 2018 14:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 93zS55i6EtlA for <rtcweb@ietfa.amsl.com>; Mon, 3 Dec 2018 14:27:30 -0800 (PST)
Received: from smtp73.iad3b.emailsrvr.com (smtp73.iad3b.emailsrvr.com [146.20.161.73]) (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 171C8130DF2 for <rtcweb@ietf.org>; Mon, 3 Dec 2018 14:27:30 -0800 (PST)
Received: from smtp10.relay.iad3b.emailsrvr.com (localhost [127.0.0.1]) by smtp10.relay.iad3b.emailsrvr.com (SMTP Server) with ESMTP id 495DCE0326; Mon, 3 Dec 2018 17:27:29 -0500 (EST)
X-Auth-ID: fluffy@iii.ca
Received: by smtp10.relay.iad3b.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 3F038E025A; Mon, 3 Dec 2018 17:27:27 -0500 (EST)
X-Sender-Id: fluffy@iii.ca
Received: from [10.66.246.3] ([UNAVAILABLE]. [64.104.248.215]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.12); Mon, 03 Dec 2018 17:27:29 -0500
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <0293CF6D-9B4F-4680-BBB9-833C33D03013@sn3rd.com>
Date: Mon, 03 Dec 2018 15:27:25 -0700
Cc: RTCWeb IETF <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <00FB4C71-EBD9-4EF6-A3B1-D0C06EA61A53@iii.ca>
References: <0293CF6D-9B4F-4680-BBB9-833C33D03013@sn3rd.com>
To: Sean Turner <sean@sn3rd.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/BAfR3b5v8thuNqKyOSNZYl0IwOQ>
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: Mon, 03 Dec 2018 22:27:32 -0000

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

v2.23.0 | Report a Bug | By Email