Re: [Patient] the IETF participant choice

Ted Lemon <mellon@fugue.com> Mon, 19 March 2018 21:23 UTC

Return-Path: <mellon@fugue.com>
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 A30A9127058 for <patient@ietfa.amsl.com>; Mon, 19 Mar 2018 14:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 ZbrKGrpSViU3 for <patient@ietfa.amsl.com>; Mon, 19 Mar 2018 14:23:52 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 64AEC1200A0 for <patient@ietf.org>; Mon, 19 Mar 2018 14:23:52 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id v194-v6so12127479itb.0 for <patient@ietf.org>; Mon, 19 Mar 2018 14:23:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=L0jC4FGVPoRC5JcO01W1SvWQ50mQ/yHjXsKiNuiucfU=; b=VgtU5YLfmfD8q4ansB2LApj/emvqG4E37DrGZdDQx5Gt1yyAp/FonLnTWhzBIw2GQP wC2sAOjZSoEOQlGhBmeTH6kT3IES9qR33TQPYRaa22hCZukuUCG85qSvn0L90c7xj14I pQZvl5nQgFgOFnOwA0Ode1FsZ69nQ2pYvYezWOmXwt0kdMm/WdoOfjS0EVK6zL/eUyr0 IFXWTra4m8HYik+BvmZ3LYMJg7hwpHZUxIfRInAQxbBuPtl5+oAF1kLZRosKR0DAdrj7 vjp29L27PPEgU7dE82mXOSfGpMxIDrZFiX8eqoGK9CIj7kgZf29qLoHw/w3v66g2ygUI saYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=L0jC4FGVPoRC5JcO01W1SvWQ50mQ/yHjXsKiNuiucfU=; b=CCXPLFiAI2kcHGlVduQW91ZtaIo56gA3x1zgJJJsPPNi/R6g9tWUcY6BbFjM6hDB3F l7Fftzk8Fq7YLPmyty6G+cMvkZJwEV4pfLVcHN/m3Pdvodt7HvVFAFrEwVTllPw4yeHR +MK3Y1B+KG14Bjnn7oUZEjk9rvc3gHp8+DM8tDw9P4Fvjqaq1abBMwiWfy0dqzz2xr/q kgRtQsnc+oDKsXq3EoxOffTGnkqEpBD/PfAIxNEHNyAhRJaf/fgXbf8b0qWmnthjxWjf B6uKOeDiRuhWTup5xV7nmEHyW0BwpME2958mE6PHXI3g6YRcx8XRbn7x3Ln1veTdGgTX wDuw==
X-Gm-Message-State: AElRT7FURuEXM7diOBOMDlrdS+fmDVaJn1ZbJC5Bi31CI1MMaX+b1AUy qm5MZpLJqhz8vJMPCvm5GPukCNSoDxICVGwMMkdV+w==
X-Google-Smtp-Source: AG47ELsQy5RCQTuN3Rp0/CNcYdnEhq7bQQGPKG4Ndn0nr27Ys5R8ogkK8v7vy+hjmzfvBoGP2TVKt3XOESfOH0sPJfI=
X-Received: by 2002:a24:9b8a:: with SMTP id o132-v6mr337227itd.82.1521494631653; Mon, 19 Mar 2018 14:23:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.226.203 with HTTP; Mon, 19 Mar 2018 14:23:51 -0700 (PDT)
Received: by 10.79.226.203 with HTTP; Mon, 19 Mar 2018 14:23:51 -0700 (PDT)
In-Reply-To: <2638b64d-ec63-b862-38e5-929f9ae6ad66@yaanatech.co.uk>
References: <MWHPR16MB14881688FE400E3277CA8A9393310@MWHPR16MB1488.namprd16.prod.outlook.com> <MWHPR16MB14889B7535153E5844649CA393370@MWHPR16MB1488.namprd16.prod.outlook.com> <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> <DF3346A5-89C8-4299-AA8F-A4C14F98B7EF@fugue.com> <2638b64d-ec63-b862-38e5-929f9ae6ad66@yaanatech.co.uk>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 19 Mar 2018 21:23:51 +0000
Message-ID: <CAPt1N1n-wxVjPsLprbfgBYCmRy1Ha0ZPHigAgmnv4vu8fxiSrQ@mail.gmail.com>
To: tony@yaanatech.co.uk
Cc: "patient@ietf.org" <patient@ietf.org>, Brian Witten <brian_witten@symantec.com>
Content-Type: multipart/alternative; boundary="0000000000000c3eef0567ca93c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/patient/G-ve06g3W6NcKGUd4pmCi9f9l8c>
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 21:23:55 -0000

There are individuals who show up here to talk about why they need stuff
and use their own operational problems as examples. That's how we always do
this. It's really a process of successive approximation.

On Mar 19, 2018 20:38, "Tony Rutkowski" <tony@yaanatech.co.uk>; wrote:

> The concern here begs the question, "whose" systems analysis?  The IETF is
> not some kind of Land of Oz where a wizard has the answers to all manner of
> complex systems requirements.  There are many competing requirements across
> all manner of data centres, architectures, providers, and user
> communities.  Meaningful implementations will also require acceptance and
> adoption by an equally broad array of communities.
>
> There are no solution singularities here, and multiple tailored
> specifications are certain to emerge.  The academic and patent literature
> evidences several dozen of them. Indeed, whatever any standards body does
> will be competing with a large number of proprietary solutions.  The only
> certainty is the demand for effective solutions.
>
> In TC CYBER, we are moving ahead with our own and evolving them in light
> of this reality - hopefully with essential reflection and criticism from
> IETF participants.
>
> --tony
>
>
> On 19-Mar-18 4:07 PM, Ted Lemon wrote:
>
> On Mar 19, 2018, at 8:01 PM, Tony Rutkowski <tony@yaanatech.co.uk>; 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.
>
>
> The thing is, at least from my perspective, we haven't done a systems
> analysis yet, and so it was just premature to try to get the TLS working
> group to weaken TLS in order to solve the problem.   For example, the claim
> was made that it would be "too expensive" to do anything _other_ than
> modify TLS, but where's the analysis to support that position?   Too
> expensive to use middleboxes, but where's the analysis there?
>
> This is really an ops problem.   IETF can do ops work, but ops isn't about
> changing protocols—it's about figuring out good solutions to problems.
> Sometimes the answer to an ops problem is "we need some protocol work
> done," but that's not the starting point.
>
> As a consequence, I feel like some very well-meaning people came to the
> IETF with hat in hand and didn't get what they'd hoped for, and probably
> have the impression that people here don't care about their problem, when
> that's not actually the case.   Lots of people I talked to who were against
> the proposed solution care very much about the problem.
>
>
>
> _______________________________________________
> PATIENT mailing listPATIENT@ietf.orghttps://www.ietf.org/mailman/listinfo/patient
>
>
>