Re: [tsvwg] dispute (Re: Results of consensus call on ECT(1) usage)
Wesley Eddy <wes@mti-systems.com> Fri, 22 May 2020 20:15 UTC
Return-Path: <wes@mti-systems.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD9B83A0AFB for <tsvwg@ietfa.amsl.com>; Fri, 22 May 2020 13:15:47 -0700 (PDT)
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, 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=mti-systems-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 9zDAMPqI4cTz for <tsvwg@ietfa.amsl.com>; Fri, 22 May 2020 13:15:46 -0700 (PDT)
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 304B53A0AFA for <tsvwg@ietf.org>; Fri, 22 May 2020 13:15:46 -0700 (PDT)
Received: by mail-il1-x131.google.com with SMTP id r2so711436ila.4 for <tsvwg@ietf.org>; Fri, 22 May 2020 13:15:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=EgrVSr9KXXiVk3umwOFiTlzJf9v+KSq13fmeKPw1YF8=; b=pibnx98GvasTwM5dAWnPiNO024NXKf7eMUaW6QirqwbPf6/e26ZIpxv6oGIUWBIt4a gm32izpZywQ+OUUPsQuZ1d18rkOhaxWNicJUynR5WLQcEXhVLUDRQnIic33vwl9l5qJ7 ih5/Awqvgr9RQMIy+DlenjawVW5uZcYEdfdJx72Vc85sVzQ26d1FMUZTrBl9CkYlfzk0 fM0xy5sBqQl2KNWq4AwpxusTHmLao6p6DgCxirg+uM9MlB8wcjCBJVNNwuMmPugb85AB aEKOENtFoh4/UXmszXVpPQRzj9RZLJTmoBHCfSCxCfGximmxmdrkOL40a1f61Gk5jh4s TKLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=EgrVSr9KXXiVk3umwOFiTlzJf9v+KSq13fmeKPw1YF8=; b=tJCPvttI3OggK9zo0XdrvXVK3zxbePAhbIIqbPkyFIJBt5Wv2n87O0yzhpiaxY95qn //AUIL4y0HgufyhBa4qcPwfeKo5cPV+A3mKGLv6xqOVlI68NUDSYT5zxxDJUA8ILsfXI aNhpM3t7UzHLalhFxS7XY9ufY6brLJ6mUP1BQ32hQuWa5XM+Pl8N/5Oso7e7JLfFiPVR l+N/AKI5+HBlKZSNtgWnB4lhhNfeYZJPZliSEsj1SJAOF7g4HFo0OBUNqAeGQUR0gBnL atN1fz0DKFYFoSGCu1jS59V0wbbpwiv0L4dPezzXgP8omIrs8AbN4ocmO3QGqTopHppc JDJA==
X-Gm-Message-State: AOAM531/TB0tE74fb6LR5vMdBLEu9Pgq+LKkDRClrH6ZOQzlTLTmsFz4 fFh4x4Occa7C6vcvFZZLeBetAOU5puEXKQ==
X-Google-Smtp-Source: ABdhPJwDiFctONCW17zq9SwXT8pr9oiQq3LnCY5P59E5X1Znk46ytCovzgCsjUoG8X8vRJDnbj6ovg==
X-Received: by 2002:a92:cf46:: with SMTP id c6mr15488974ilr.4.1590178544997; Fri, 22 May 2020 13:15:44 -0700 (PDT)
Received: from [172.31.98.31] ([104.193.30.26]) by smtp.gmail.com with ESMTPSA id 199sm2469943ilb.11.2020.05.22.13.15.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 22 May 2020 13:15:44 -0700 (PDT)
To: Paul Vixie <paul@redbarn.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <d182f539-e0a2-e924-9556-db6577f47357@mti-systems.com> <3228077.bNJ4EoEDyu@linux-9daj>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <59853a16-9c83-bcf2-7f1d-49bddffab9b8@mti-systems.com>
Date: Fri, 22 May 2020 16:15:41 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <3228077.bNJ4EoEDyu@linux-9daj>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/2giEGBEHGrqR7NznKUR805bbeMw>
Subject: Re: [tsvwg] dispute (Re: Results of consensus call on ECT(1) usage)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 May 2020 20:15:48 -0000
Hello, this is my own attempt to answer your questions/concerns, not necessarily matching what other co-chairs or our ADs would say, though we did coordinate on evaluating the consensus call, and the original statement of results. Just to make sure it's clear, this was not a WGLC on any of the drafts. It was about finding direction on one particular issue that has been an active part of the discussion for around a year ("what to do with ECT(1)?"), and for which there is a broad desire to move forward somehow on. We tried to be clear that there is still work to be done in this selected direction for the WG to make sure the technology is safely deployable, before we do a WGLC. Pruning the other possible directions helps to focus on that work, and getting to the WGLC will be based on technical merit. Specifically on your question of why choice 3 ("more testing") was not the rough consensus on how to use ECT(1), I don't think the responses indicated that we had enough energy or bodies to work in this direction, though there were some helpful points that people with choice 3 response made about what we should be looking for while proceeding in the choice 1 direction, that I think we are all taking into account. Joe and others have asked about a "do nothing" (or "none of the above") choice that was missing from the poll. If there were inconclusive results to the poll, I suppose that would have been a default state we would fall into. This would basically be maintaining the status quo with regard to ECT(1) usage, and have both L4S and SCE needing to find alternative ways to function. The inputs we received show that this would not have been a favorable option to the group. I hope this is all more clear and addresses your questions/concerns, and sorry if it wasn't evident in the original response we chairs had coordinated on.
- Re: [tsvwg] dispute (Re: Results of consensus cal… Joe Touch
- [tsvwg] dispute (Re: Results of consensus call on… Paul Vixie
- [tsvwg] Results of consensus call on ECT(1) usage Wesley Eddy
- Re: [tsvwg] dispute (Re: Results of consensus cal… Rodney W. Grimes
- Re: [tsvwg] dispute (Re: Results of consensus cal… Lars Eggert
- Re: [tsvwg] dispute (Re: Results of consensus cal… Rodney W. Grimes
- Re: [tsvwg] dispute (Re: Results of consensus cal… Wesley Eddy
- Re: [tsvwg] dispute (Re: Results of consensus cal… Bob Briscoe
- Re: [tsvwg] dispute (Re: Results of consensus cal… Joseph Touch
- Re: [tsvwg] dispute (Re: Results of consensus cal… Black, David
- Re: [tsvwg] dispute (Re: Results of consensus cal… Paul Vixie
- Re: [tsvwg] dispute (Re: Results of consensus cal… Joseph Touch
- Re: [tsvwg] dispute (Re: Results of consensus cal… Sebastian Moeller
- Re: [tsvwg] dispute (Re: Results of consensus cal… Sebastian Moeller
- Re: [tsvwg] dispute (Re: Results of consensus cal… Paul Vixie
- Re: [tsvwg] dispute (Re: Results of consensus cal… Wesley Eddy
- Re: [tsvwg] dispute (Re: Results of consensus cal… Black, David