Re: [Patient] the IETF participant choice

Benjamin Kaduk <kaduk@mit.edu> Mon, 19 March 2018 23:58 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: patient@ietfa.amsl.com
Delivered-To: patient@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED76B12D964 for <patient@ietfa.amsl.com>; Mon, 19 Mar 2018 16:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 iQ1daNGcU4yl for <patient@ietfa.amsl.com>; Mon, 19 Mar 2018 16:58:31 -0700 (PDT)
Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A13E912D864 for <patient@ietf.org>; Mon, 19 Mar 2018 16:58:31 -0700 (PDT)
X-AuditID: 1209190f-b3bff700000037c7-40-5ab04ea5ab89
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id C9.97.14279.6AE40BA5; Mon, 19 Mar 2018 19:58:30 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id w2JNwQca029494; Mon, 19 Mar 2018 19:58:27 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w2JNwMUw004121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Mar 2018 19:58:25 -0400
Date: Mon, 19 Mar 2018 18:58:22 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Tony Rutkowski <tony@yaanatech.co.uk>
Cc: Brian Witten <brian_witten@symantec.com>, "patient@ietf.org" <patient@ietf.org>
Message-ID: <20180319235822.GW55745@kduck.kaduk.org>
References: <MWHPR16MB14880A12D15AC58FDD5CEC8793370@MWHPR16MB1488.namprd16.prod.outlook.com> <MWHPR16MB1488D43F3B53BC7BBE9D836593370@MWHPR16MB1488.namprd16.prod.outlook.com> <MWHPR16MB1488853B0E4F7BB8E557288D93370@MWHPR16MB1488.namprd16.prod.outlook.com> <MWHPR16MB148845FB069D03625BC399B193370@MWHPR16MB1488.namprd16.prod.outlook.com> <MWHPR16MB1488848D7AC828EBB8DA90B093350@MWHPR16MB1488.namprd16.prod.outlook.com> <DM5PR16MB148477E1FAA4C210A3B013F7930A0@DM5PR16MB1484.namprd16.prod.outlook.com> <alpine.LRH.2.21.1712141805020.15188@bofh.nohats.ca> <MWHPR16MB148859D8FC007D9B9D5005E6930A0@MWHPR16MB1488.namprd16.prod.outlook.com> <988132f9-478d-2012-9ad2-353534f07db7@yaanatech.co.uk> <e89e816d-76da-c062-b3fc-ae2e73c176ae@yaanatech.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <e89e816d-76da-c062-b3fc-ae2e73c176ae@yaanatech.co.uk>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLKsWRmVeSWpSXmKPExsUixG6norvMb0OUwaer2hYHutazWbw8YGzR vJzFgdljyZKfTB47zk9h9nj6eiFbAHMUl01Kak5mWWqRvl0CV8aJSycZC26xV9y9sIK1gXEB WxcjJ4eEgInEtBftQDYXh5DAYiaJa4tOMEM4Gxklbj7azwLhXGWSeL/4PFAZBweLgKrExx31 IN1sAioSDd2XmUFsEQFNiXdts9hBbGaBGImnL68ygtjCAkYSPy5eBKvhBdrW++8jK8TM76wS 09dPZ4JICEqcnPmEBaJZR2Ln1jtgu5gFpCWW/+OACMtLNG+dDTaHU8BZYvreT2C2qICyxN6+ Q+wTGAVnIZk0C8mkWQiTZiGZtICRZRWjbEpulW5uYmZOcWqybnFyYl5eapGuiV5uZoleakrp JkZQmHNK8u9gnNPgfYhRgINRiYdX4876KCHWxLLiytxDjJIcTEqivKeYNkQJ8SXlp1RmJBZn xBeV5qQWH2KU4GBWEuF9emVdlBBvSmJlVWpRPkxKmoNFSZzX3UQ7SkggPbEkNTs1tSC1CCYr w8GhJMEbAYxnIcGi1PTUirTMnBKENBMHJ8hwHqDhf32BaniLCxJzizPTIfKnGI052lY+aWPm uPHidRuzEEtefl6qlDjvJpBSAZDSjNI8uGmgVCWRvb/mFaM40HPCvJdBqniAaQ5u3iugVUxA q3yWrgFZVZKIkJJqYLQIPG8zgT9iu1Ll86dz4k5zqJad6I0qmZflwzZ3vqPAwffrm336Ox4p SLaXKU/qnMDtN+OTGl/C9eWp5W8ZLunkrteTX9xyNUBVZ/Izxp99d8Si95xl+JbsmVjA4/5J eOPtvDV/XxSuYGdgl7h47avSiqw4lz2cG7YsFPd4NfnfjXUb1FYf11FiKc5INNRiLipOBABw 7qx/MAMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/patient/kXr6SrhZoJfdy9jcJTy22El-Y90>
Subject: Re: [Patient] the IETF participant choice
X-BeenThere: patient@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Protecting against Attacks Tunneling In Encrypted Network Tunnels <patient.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/patient>, <mailto:patient-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/patient/>
List-Post: <mailto:patient@ietf.org>
List-Help: <mailto:patient-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/patient>, <mailto:patient-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 23:58:33 -0000

(Why is discussion of the TLS WG's [in]action occurring on PATIENT?)

On Mon, Mar 19, 2018 at 04:01:27PM -0400, Tony Rutkowski wrote:
> In participating remotely, it was apparent that although the proponents 
> of the data centre visibility proposal did an excellent job in 
> articulating the need, the solution was not going to be undertaken by 
> the IETF.  The result in consonant with countless other similar 
> initiatives sought in the IETF over the past several decades.

Need is hardly the only prerequisite.  The (rough) consensus process
is clear that work should not be published in the presence of known,
unaddressed, technical issues.

I agree with Kathleen's assessment of the session that there are
indeed outstanding unresolved technical issues, and do not believe
that path(s) towards resolving those issues have been proposed.  In
the absence of a route to resolve such issues, adopting such
proposed work as a WG item seems premature.

-Benjamin