IETF Logo Mail Archive

Re: [OPSAWG] Christian's review of draft-mm-wg-effect-encrypt-22

Christopher Morrow <morrowc.lists@gmail.com> Mon, 26 February 2018 19:02 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: expand-draft-mm-wg-effect-encrypt.all@virtual.ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id C3C3E124D6C; Mon, 26 Feb 2018 11:02:13 -0800 (PST)
X-Original-To: xfilter-draft-mm-wg-effect-encrypt.all@ietfa.amsl.com
Delivered-To: xfilter-draft-mm-wg-effect-encrypt.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 983F0126C3D; Mon, 26 Feb 2018 11:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 N5C0GjwHM2ZD; Mon, 26 Feb 2018 11:02:11 -0800 (PST)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (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 94711124D6C; Mon, 26 Feb 2018 11:02:11 -0800 (PST)
Received: by mail-ua0-x233.google.com with SMTP id b23so8855246uak.9; Mon, 26 Feb 2018 11:02:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=wVcnbpO3ZxH0+NIJqf1pkj9OFt+ACXbA0CuKd+ACfwQ=; b=guGsQ69RKHQMHOmouEsgA++VDnNAVCka7r2Eu+gULGLfzbHfOlJ7BaU9wskf1kljj8 cga+qvm/boZzfDu1SFrlB2NhkHy5u98s9J6zWa+TT+EWhf4X61Xz4D9IZWCaxrpQV5ey 3D4tLr/Mk3x9GnfdMFZXPG6YvXcfmmSMXyRuvACmqqI/9bOe5GRgJ4ZgTZ78W5miJzNj a6DtkYblhYIFuMb/+KQzrsphQsao6Uxne518wLvNql6mBHxb3QjQgkhRQe/OKUTVSr28 4/PniaNidZU4sutxgQhD2RNjadvIq7siyn7d6gRzNJUZkTfkYu6YeilWIhRZZa7XdGCM 0L9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=wVcnbpO3ZxH0+NIJqf1pkj9OFt+ACXbA0CuKd+ACfwQ=; b=ejAq+CNotNXvDEQWTmfePZYavF83+lsOVCM/H6Tl35GsR48A3HKMxd5uWOqAN8ozgp N/he3n7hv33cnaCJqFNezbBb8XPHyLe+INf1aKoTkS2xS2YRnocO7iYgjljHODZBE7TR TtCBI/bVoDSJtLEo4jyz3zPmr128doQ/cm78sotq1HsaM2c5ngqolxDnAn1dN6a2uaMy oTTpYmwYqTNpacKEaaX5PsNNP3E2ZWyDhnkyIu/L2Y35xDOPRr11rwf/5mTbjBZXuv3q EW1l29wtZUoeaE9orWGyz3cBA5dZUYkhB8GDsfKGCo+Zh4sNj/TZMNrenP8AsYAjwXvD a3yA==
X-Gm-Message-State: APf1xPDsg60nH1yL8jtzcDpuNm2XtkH7dgS/vtA8yHUa2dVkW8XehyTg ImKMOT51uttcETF7JS9CXGPtRzdh6T8mfQC89Hg=
X-Google-Smtp-Source: AG47ELtXIIEUQfa5ueHRs7Ttzm0rpq1ApBanwmJFKLFCMxi5vqBzKumxU61KXVuCyosn/eTwxpPlhT610S3SPW9UdYM=
X-Received: by 10.176.112.134 with SMTP id m6mr9058871ual.105.1519671730272; Mon, 26 Feb 2018 11:02:10 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.176.49.23 with HTTP; Mon, 26 Feb 2018 11:02:08 -0800 (PST)
In-Reply-To: <A20D3E03-627D-4F72-B6E8-8FFD88258C57@strayalpha.com>
References: <bbdd9000-84b3-a700-dd3a-d23faaad8604@huitema.net> <CAL9jLaZd-19NDFGkF-03vTdddtDym+AtZmLVYBR-6aKPBx0JtQ@mail.gmail.com> <A20D3E03-627D-4F72-B6E8-8FFD88258C57@strayalpha.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Mon, 26 Feb 2018 14:02:08 -0500
X-Google-Sender-Auth: 4Rq4TMttkkj29nC1zA-cmG5nTrA
Message-ID: <CAL9jLabn-bvdL1=ED1zubTCGtG-0TxWjR-oLPAeKtdRxh7nZnw@mail.gmail.com>
To: Joe Touch <touch@strayalpha.com>
Cc: Christian Huitema <huitema@huitema.net>, draft-mm-wg-effect-encrypt.all@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="089e0832d9e0a87e6705662225a1"
Resent-From: alias-bounces@ietf.org
Resent-To: Kathleen.Moriarty@dell.com, acmorton@att.com, Kathleen.Moriarty.ietf@gmail.com, warren@kumari.net, ekr@rtfm.com, kaduk@mit.edu, Paul Hoffman <paul.hoffman@vpnc.org>, opsawg@ietf.org, paul.hoffman@vpnc.org
Resent-Message-Id: <20180226190213.C3C3E124D6C@ietfa.amsl.com>
Resent-Date: Mon, 26 Feb 2018 11:02:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/Iclzp-hgeYpXT2hOcYZdIXDj1FE>
Subject: Re: [OPSAWG] Christian's review of draft-mm-wg-effect-encrypt-22
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Feb 2018 19:02:14 -0000

On Mon, Feb 26, 2018 at 12:21 AM, Joe Touch <touch@strayalpha.com> wrote:

>
>
> On Feb 25, 2018, at 8:51 PM, Christopher Morrow <morrowc.lists@gmail.com>
> wrote:
>
> I am very skeptical of the justification for performance enhancing
>> proxies in section 2.2.4. It develops the idea that having a form of
>>
>
> These are primarily 'satellite games' proxies.. that early-ack and such to
> make the long satellite portion of the transport seem short(er).
> They only REALLY need to see TCP headers, so ipsec is problematic, but not
> (probably) tls.
>
>
> Enabling TCP Hijacking should never be justification for “needing” to
> avoid transport header privacy, IMO.
>
> Games or other apps that “need” such support ought to “need” to explicitly
> permit it by peering their security with those proxies directly.
>


apologies: "games" in my reply could better be called: "shennanigans" ...
not games like farmville, but messy things the satellite ( in the past
anyway) providers would do to make tcp appear to perform better in their
environment.

Yes, people COULD ipsec around that problem.
Yes, people COULD md5-tcp around that problem. (tcp-ao, ha!)

generally none of that has happened though.

v2.23.0 | Report a Bug | By Email