Re: Re-chartering for extension work

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Thu, 09 January 2020 14:01 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 5975E12004E for <quic@ietfa.amsl.com>; Thu, 9 Jan 2020 06:01:52 -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 JIsg4mo4yyRp for <quic@ietfa.amsl.com>; Thu, 9 Jan 2020 06:01:50 -0800 (PST)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (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 EEC51120227 for <quic@ietf.org>; Thu, 9 Jan 2020 06:01:49 -0800 (PST)
Received: by mail-qk1-x72e.google.com with SMTP id z14so5999063qkg.9 for <quic@ietf.org>; Thu, 09 Jan 2020 06:01:49 -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=wNRHtBzvpTGOUDyw2oNoO0mDyeM50Eu1dadXVq24bz8=; b=LnBaA40OLDUqf8RxZ4HXXhl01In2wxio22DxvQlb4h9+9+QHu/OJzRiKMWp6k1H9b+ DM1c+pmklp8+60IidaOEK8dFzkl4vkEb8M2peY9W8FTBxSYnwmKiyW8uWgcoLGBmW+tM RCNYv797+gbYlHxp+GiJYxVXuRaC2c2aY/Py1MjalIS1eYE9PTZk9HpNJTD6RXekHkMf XB6QRD6C8Bp2cby2Wk7V8onerSHsKADbhM2x6m+0BTLmQ3jIzi5UKV5bRTI1QCrpsZcm UQv76qPqNPfYYrcNbOtdnX4Mc6pWp5nWSgQCTG8QCcAHXs0JljijlvQHZq4yk0U0LE8D amaw==
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=wNRHtBzvpTGOUDyw2oNoO0mDyeM50Eu1dadXVq24bz8=; b=BDW395yb+z5P7nsh8UZ6EPkmim8q5qFIb8aQ9cRrm1svbB2iuf/IK1EKfc6CuHz7Dn LeQs/GZia8bq29gqSH/D8bL/r5sMPFZ3h/lav3BKtA/zDHwkvsIZuz5LFJPtL8+hFJE2 O126KVQBSnNksOYAYAD70jtLRnpBhJpwfPqx8ugAUfO9OmZgeejG/qLnrUXxAgJPlpvV 4nhV9fErcBHw2YyfEk0MupjFaGvx5JzUClS3siJ9UQWzhe+L9Affa9kAKo1xu/w9Ov2h IPozLEd6k1OK4xi0qbAmS+2fQQme4zSBhbqj5g94DhNr21FHYBjF1shv8SH6PfyS9uVt XBmw==
X-Gm-Message-State: APjAAAVG0wUF15d/za0gRlnDZrLbwRUafIpwecC7JwsKmOI3kY6NJbml 2dbvuzT2h+CHVSIzwZpAXzH0+g==
X-Google-Smtp-Source: APXvYqy5m4YRu76swvv0U7XjJpmOtyxWy7KYV+TAqV2UAzeALcd99+29b1s/zis7vphDDQUaO/jp6A==
X-Received: by 2002:ae9:ee11:: with SMTP id i17mr9657460qkg.333.1578578509174; Thu, 09 Jan 2020 06:01:49 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id a36sm3394108qtk.29.2020.01.09.06.01.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Jan 2020 06:01:48 -0800 (PST)
Date: Thu, 09 Jan 2020 09:01:46 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: "Lubashev, Igor" <ilubashe@akamai.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "Roni Even (A)" <roni.even@huawei.com>, "quic@ietf.org" <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Subject: Re: Re-chartering for extension work
Message-ID: <20200109140145.GC7263@ubuntu-dmitri>
Mail-Followup-To: Mark Nottingham <mnot@mnot.net>, "Lubashev, Igor" <ilubashe@akamai.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "Roni Even (A)" <roni.even@huawei.com>, "quic@ietf.org" <quic@ietf.org>, Lars Eggert <lars@eggert.org>
References: <A56547B6-2E3B-4ABE-8C9B-BA9ACC489FB2@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD27D34F98@dggemm526-mbx.china.huawei.com> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <EB9765F4-C07E-4142-BCEC-5DA8AA9710E9@mnot.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/g2BRnMBt5VUOYe9sxb4GPtraopU>
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: Thu, 09 Jan 2020 14:01:52 -0000

On Fri, Dec 13, 2019 at 10:16:45AM +1100, Mark Nottingham wrote:
> > On 13 Dec 2019, at 3:14 am, Lubashev, Igor <ilubashe@akamai.com> wrote:
> > We were planning to present the draft of lossbits as a negotiated
> > extension in Zurich, but given that the time for the inclusion
> > in the Charter is now, we can get the draft out next week.
> > Given the prior discussion and expressed willingness of at
> > least a part of the WG to work on this, would you include
> > that extension draft in the WG adoption call prior to the
> > charter update?  (As usual, adoption != publication, which is
> > subject to the deliberations of the WG, including a positive
> > privacy/security analysis.)
> 
> If we performed a Call for Adoption now, I strongly suspect it
> would fail, because the privacy and security evaluation hasn't
> been performed; we went through the same process for the spin bit.

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?

  - Dmitri.