Re: [Tsv-art] do we need a checklist or guidelines?

Joe Touch <touch@isi.edu> Thu, 20 July 2017 14:28 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA3A13146C for <tsv-art@ietfa.amsl.com>; Thu, 20 Jul 2017 07:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 dFIzfVPsQsEA for <tsv-art@ietfa.amsl.com>; Thu, 20 Jul 2017 07:28:35 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (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 23CBD13188F for <tsv-art@ietf.org>; Thu, 20 Jul 2017 07:28:35 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v6KERXHW005113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 20 Jul 2017 07:27:43 -0700 (PDT)
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>
References: <44b6345c-359b-65b3-d71e-3210f676fbbc@isi.edu> <A6661E71-E830-4402-A09F-744B6544200C@kuehlewind.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <33fa433f-52bf-172a-9151-c7dd8153407a@isi.edu>
Date: Thu, 20 Jul 2017 07:27:31 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <A6661E71-E830-4402-A09F-744B6544200C@kuehlewind.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/q_imgwiipLL-waT98UFyyGUHGR8>
Subject: Re: [Tsv-art] do we need a checklist or guidelines?
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 14:28:45 -0000


On 7/20/2017 5:22 AM, Mirja Kuehlewind (IETF) wrote:
> Hi Joe,
>
> I would say that the points under c) are usually already discussed and considered in the IETF (in tcpm where we sooner or later have all these proposals presented at least once). However, I don’t see a need to further formalize anything here because I don’t see how this could help.
>
> I also think that „attack“ is really not the right word here. People are free and should be encouraged to bring their idea to the IETF/tcpm and then have a discussion with the experts there figuring out if their proposed solution is the right approach or if there are other better alternatives. Just trying to send these people away doesn’t help.
The issue is similar to security considerations, congestion issues with
UDP, etc - the community *is* extending and adapting TCP and certainly
we're providing feedback, but that feedback would be a lot more
efficient if the community knew what our expectations were, IMO.

Especially when some of these requests for transport analysis happen in
days/hours before IESG review, as is too often the case.

Joe