Re: Re-chartering for extension work

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Fri, 10 January 2020 13:49 UTC

Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCEC61208D3 for <quic@ietfa.amsl.com>; Fri, 10 Jan 2020 05:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 TJ1xdlwnibiS for <quic@ietfa.amsl.com>; Fri, 10 Jan 2020 05:49:16 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 95D3B1208D2 for <quic@ietf.org>; Fri, 10 Jan 2020 05:49:16 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id j5so1910079qtq.9 for <quic@ietf.org>; Fri, 10 Jan 2020 05:49:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=3kEgso1MG9FTrgc13vwHvyZCGFx1rMsy1vAQ3VFVqMk=; b=KmkUTRRQO7Icce6ssjk4szyn2PWD8sgDXWhlEqCBT8ngLcYbyBPkuH9tIkhu1bJ04a gbpUVmYixa7tKn3xk+DNv+5FO1vy6sRjbvJtv2Hq8uelZpvOc4ihMYO4MI0UH02IJrxj BD2MguEmRRYHHvofzQqZCwggr/VxbvegXgd8nCJeFds60H+CDo2kUnTvX+1WA6HgMTmU 3JPVhbT3ePT2bIvpIvzPLdBSA+PqilS45+hwRvKfW/VJcY9rF0fL26WWDOnPJ4QrK3vF u+FYRCeGyg0UQlJPCOltOK3gsVOs47HnqZI3d54M49m2SFUlCsN58U0IT3sNxGJlVHT1 rIvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=3kEgso1MG9FTrgc13vwHvyZCGFx1rMsy1vAQ3VFVqMk=; b=GdSunO3v9fu0H5hcMdDS0GCgBNqZ9jQdwREXJl4VWjt/0TQ7txpoRBP8x+uORWlSqk wBlE9orPg+BEJ0QLvwgaOZT6FLgQsSMWeoFkuE4MnvXtrifLbgZab8SNRRfyO/HOf+K0 BYJdCjtu4Nh6f0Ad2sjaF137B+WPbK6bSMwAEBuJcNI02lPbpKRq8n83yUZnu6GzoEvr 90KRWnHuIq0jBBR5UW58oSZS+baAWsH6xWpXB0yJc9+/w4niX9rVtvKGvCxVp8OVeITv PC4Dw6rbpRS1NTam0qVAMXZTv1F7jl2kTsvB6GC3meB4hTl/20NntAcmXJoxnz/Xh8H5 TQHw==
X-Gm-Message-State: APjAAAVX7koFWe5vutHiFtFMzy7iMiC+nyeq7MpNmAWU9YygZoFbEs7f U32AZF4kh5K7rJs2RwTwspHg8hM+DHg=
X-Google-Smtp-Source: APXvYqx/zSI916wmLpwppWx453SMnwFG63UxUH1S6McRRXkM8qELFsVSOADaUb6qXb9kOZdpY5hfAQ==
X-Received: by 2002:aed:2c03:: with SMTP id f3mr2432928qtd.80.1578664155751; Fri, 10 Jan 2020 05:49:15 -0800 (PST)
Received: from ubuntu-dmitri (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id a144sm892118qkc.30.2020.01.10.05.49.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Jan 2020 05:49:15 -0800 (PST)
Date: Fri, 10 Jan 2020 08:49:10 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: quic@ietf.org
Subject: Re: Re-chartering for extension work
Message-ID: <20200110134909.GA2650@ubuntu-dmitri>
Mail-Followup-To: Martin Thomson <mt@lowentropy.net>, quic@ietf.org
References: <A51C42AD-6D1C-432D-99B4-8BB0FB824348@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD27D34FD8@dggemm526-mbx.china.huawei.com> <18FA3A15-D580-43FD-A64C-E12E79D91419@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD27D35044@dggemm526-mbx.china.huawei.com> <1575ae9dcdcade6a8ec68289fd6b735eae04ed32.camel@ericsson.com> <6E58094ECC8D8344914996DAD28F1CCD27D3512A@dggemm526-mbx.china.huawei.com> <c98ddfd008714672857833383153efb7@ustx2ex-dag1mb5.msg.corp.akamai.com> <EB9765F4-C07E-4142-BCEC-5DA8AA9710E9@mnot.net> <20200109140145.GC7263@ubuntu-dmitri> <72ef65b4-0a12-4fba-975b-a35b1a425ec7@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <72ef65b4-0a12-4fba-975b-a35b1a425ec7@www.fastmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tvAUnLv9JLnjBV7p4LCaPMe3Su0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2020 13:49:20 -0000

Thank you for the comprehensive and insightful answer, Martin.

On Fri, Jan 10, 2020 at 12:41:15PM +1100, Martin Thomson wrote:
> On Fri, Jan 10, 2020, at 01:01, Dmitri Tikhonov wrote:
> > What is the security evaluation process?  Can just anyone do it
> > (for example, myself sitting down and thinking about it really
> > hard) or are there designated IETF people or entities that do
> > this sort of thing?
> 
> The goal is to reach consensus on what the properties of the
> proposal are.  Maybe we might not agree on the value proposition,
> but we should be able to agree on the impact a proposal has to the
> privacy and security of different participants.  When we did the
> spin bit, we formed a design team that discussed potential threats
> and produced an assessment of the overall impact of the proposal.
> That design team reported their findings to the group, people asked
> questions that were answered, we each reached our own conclusions, and
> ultimately we concluded that the findings were sound.  That meant that
> we were able to make a decision about adoption that wasn't confused
> by a disagreement about the facts.
>
> It's probably not the case that everything needs a design team or that
> level of process as long as we are able to reach consensus, but for
> contentious or complicated topics, you could need even more support
> or background work when it comes to establishing what the facts are.
> For instance, when we did HPACK, Google funded academic research into
> the proposal and the researchers set out to break the scheme.  That was
> hugely helpful in informing our decision to adopt that approach.
>