IETF Logo Mail Archive

Re: [rtcweb] Alexey Melnikov's No Objection on draft-ietf-rtcweb-overview-18: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Fri, 21 April 2017 06:33 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 B8CB1127599; Thu, 20 Apr 2017 23:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level:
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=eNaBNJUQ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Hd94icPL
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 lD9FqDyTa81s; Thu, 20 Apr 2017 23:33:45 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DD1F129457; Thu, 20 Apr 2017 23:33:45 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E08152082E; Fri, 21 Apr 2017 02:33:44 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Fri, 21 Apr 2017 02:33:44 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=UYXtUvEiUV0hOeD5OQ op29ESF1PNQUCd01SlnPoMBqg=; b=eNaBNJUQxUTOU7n9tuZqf/ASVlIo5g6VLl 4PAYBwVTbkL7OdAH1gVgRD7s6jyzSfaBSPGaBlQTCKRBhKLHiZvN6/I0wIEhqwbf 7PL+wcumbLpywEhsLkZNnK2j31q3ZiUFJaOKHYFI4KNh0NF4runeMJCrZYJH4Ndo qyIfkf5obyQX7Zp5jGFwoKXT6oIapzjV7KWYTSJJOcHrGWVtdezQE9oUFmTHMfr2 Rvru5RPAeLH4ZcPhAUuK634Rgc7G4mRLFDJT9d29RgR4jqd673HBVNo3xz8DYcdo ZAm/ZcNgR3J118G2bicutBmPkes8CK+N+qpQqd9rWBp73CBOJrmg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=UYXtUvEiUV0hOeD5OQop29ESF1PNQUCd01SlnPoMBqg=; b=Hd94icPL DpEsNUDSeYNhRHE4fF2KVC6IefRetf0BcAGKA6oXFy1DxyjDLCLq30EWyFJ4FSFr 32g9tNuSl6EwcgHgPa2cZgMxyljLvk3Sb7nsWIoSdsumG1x6p/7Kd6ojWfdK7vKG Ois7ect9F7BAL/H2VH9LmEW6Ifz5DiFl6d7wKd3fEhHAgx3sZc8G3fllLjXBSzt3 eUQyWwTC4Qhr/z+XIm1w7yEJ35hyfLnh+0dWPaeYyS1SL4H/X3rXe9Jn1KSur1Kt Bev9MGM79qiXPA7OQAZ7hImISsnjnTo8ZjSEUn81Wu4XbpjnikOgSN4V5Dir+WCv DweqKEEOt7eLBw==
X-ME-Sender: <xms:yKf5WOn0hYBbRI-1arcHWnDcZn3z7uLRnx8HjwnNVpjQl95d8ROkzg>
X-Sasl-enc: 8yg77KFcp1KNIerSBiN5wNhk2IEpsPhzYv3Fj1lxMzDE 1492756424
Received: from [10.1.0.228] (unknown [85.255.237.155]) by mail.messagingengine.com (Postfix) with ESMTPA id 693577E352; Fri, 21 Apr 2017 02:33:44 -0400 (EDT)
Content-Type: text/plain; charset="windows-1251"
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <90597C26-2C7A-4108-BE54-535453C546A6@sn3rd.com>
Date: Fri, 21 Apr 2017 07:49:03 +0100
Cc: The IESG <iesg@ietf.org>, draft-ietf-rtcweb-overview@ietf.org, rtcweb-chairs@ietf.org, "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <594FA817-3944-420C-A439-44D99250F11E@fastmail.fm>
References: <149272773758.22277.5303623973493888340.idtracker@ietfa.amsl.com> <CA+9kkMDDfxEHThzKGz6gjxG5VYW7GY_p+Xv7EN0x3htZ0F3CPQ@mail.gmail.com> <90597C26-2C7A-4108-BE54-535453C546A6@sn3rd.com>
To: Sean Turner <sean@sn3rd.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/0_tm7vNbqRTH8xN-1SdSpXvvT-o>
Subject: Re: [rtcweb] Alexey Melnikov's No Objection on draft-ietf-rtcweb-overview-18: (with COMMENT)
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: Fri, 21 Apr 2017 06:33:48 -0000

> On 21 Apr 2017, at 01:55, Sean Turner <sean@sn3rd.com> wrote:
> 
>> On Apr 20, 2017, at 18:40, Ted Hardie <ted.ietf@gmail.com> wrote:
>> 
>> On Thu, Apr 20, 2017 at 3:35 PM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
>> 
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>> 
>> Last time I checked the document is referencing normatively 2 expired
>> drafts (security considerations and security architecture). What is the
>> plan for completing them?
>> 
>> 
>> They both went through WG last call and then got put aside until the work on JSEP finished.   We should have changed the status so that they did not expire, but failed to do that.  My apologies for the oversight.
>> 
>> Refreshing them is on the top of the WG list after JSEP moves to the IESG (currently being updated after Adam's AD review).
> 
> Alexey thanks for making this a comment.
> 
> I am hoping that the IESG will help us get RTCWEB done in stages.

Sure.
> We could back up the draft truck and dump a couple of hundred pages on y’all but that wouldn’t be nice.  Our bottle neck is obviously editor cycles and I’m really hoping that you share the prioritization of TLS1.3 and JSEP followed by the two RTCWEB security drafts.  Appointing another editor at this point isn’t really realistic.  And do note that though expired they are available for your viewing pleasure on github:

That is fine. I just couldn't figure out from datatracker what is the status of 2 documents.

>  https://github.com/rtcweb-wg/security
>  http://rtcweb-wg.github.io/security-arch/
> and tools:
>  https://tools.ietf.org/html/draft-ietf-rtcweb-security-arch-12
>  https://tools.ietf.org/html/draft-ietf-rtcweb-security-08
> 
> spt

v2.23.0 | Report a Bug | By Email