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

Sean Turner <sean@sn3rd.com> Fri, 21 April 2017 00:55 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 43B2712EABC for <rtcweb@ietfa.amsl.com>; Thu, 20 Apr 2017 17:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, 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 QmmvlpjrybF1 for <rtcweb@ietfa.amsl.com>; Thu, 20 Apr 2017 17:55:36 -0700 (PDT)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 2246612EAB8 for <rtcweb@ietf.org>; Thu, 20 Apr 2017 17:55:36 -0700 (PDT)
Received: by mail-qk0-x231.google.com with SMTP id f133so61108985qke.2 for <rtcweb@ietf.org>; Thu, 20 Apr 2017 17:55:36 -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=B/dPtjGF0QJYXFuYDjj6TKZWxKwQSZ1g87RG0SG3IL8=; b=HkYEzJNAHDnYkxmajU5Trux5Us7q06zsVwsrFUwgwll45NR+LSdZx/uS/1BYq6AIaq G2a46RFKYW9UedCeI2uAhJqJik5Su2v3vZJQszCC/6YNQz2ScOm5ApGDbSESLSqrcJOw Ws2591E/zTbAoXn68/9dR0bBYfn48RJcOZMAM=
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=B/dPtjGF0QJYXFuYDjj6TKZWxKwQSZ1g87RG0SG3IL8=; b=M1SKg8WhyZHRwoRzKTUwQ8yu/B4unn5yI+mBKRkJDBIs5fyWIChyoij79g23lOid/D ja3YDrFO+T2Ef5vu4qtDqtqpxX8CZBiiKqEFfxlbLQr2/8JEiZoDykWxWUiaajTO+JvL rfVRpXmhyYPevObksao5MOL5UTcH7SPqmzM1uOfIWct+Q0tLGIB6I6bgf0LUqmYgpLep OlrPYy0wbRF6KzB0OfZyB5pquuuBVvuCBrqHa3qrWonlBOfuCiMsoYbF39DirtjHCcXI CLaRnqvg3AdbXo9zXOxznRYH4p8h30qCYRXSk0CJa+tHvUatFRyl+YwdWJZU/4bdDv0E ER3g==
X-Gm-Message-State: AN3rC/4OOHUSticZiibwuECsjUoENXEZSZU9VewCng0FT0BbwlOW+YFZ On4vBacOdjUqgg==
X-Received: by 10.55.185.131 with SMTP id j125mr11069399qkf.6.1492736135264; Thu, 20 Apr 2017 17:55:35 -0700 (PDT)
Received: from [172.16.0.18] ([96.231.229.219]) by smtp.gmail.com with ESMTPSA id f30sm5355333qte.11.2017.04.20.17.55.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 17:55:34 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <CA+9kkMDDfxEHThzKGz6gjxG5VYW7GY_p+Xv7EN0x3htZ0F3CPQ@mail.gmail.com>
Date: Thu, 20 Apr 2017 20:55:33 -0400
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: <90597C26-2C7A-4108-BE54-535453C546A6@sn3rd.com>
References: <149272773758.22277.5303623973493888340.idtracker@ietfa.amsl.com> <CA+9kkMDDfxEHThzKGz6gjxG5VYW7GY_p+Xv7EN0x3htZ0F3CPQ@mail.gmail.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/0A_jxS2mf1_7pWa2DO6xDtaLQoA>
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 00:55:44 -0000

> 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.  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:
  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