Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 11 April 2017 08:51 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 492CC1200F1 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 01:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 u6KvCqGNE021 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 01:51:23 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED15D120727 for <ietf@ietf.org>; Tue, 11 Apr 2017 01:51:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E6568BE4D; Tue, 11 Apr 2017 09:51:16 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R6flA7Jv3qQS; Tue, 11 Apr 2017 09:51:15 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3BCB5BE47; Tue, 11 Apr 2017 09:51:15 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1491900675; bh=UfRYkuClog0+CheGPTaMNxHqz+9OPVU0DVqxIjYb6Jg=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=AjMVakXk/QWDyzsGyfpBq5O6uC3LxFS3i7NlzCjLN/Srye8JZDdKDpaXqVFwCr5JK ZuG2bOOl97GQx/WujUQPT18/lk6vEUmPPgvrXiSEg4ur6S3/LLYNZuBz3BN6TnNgOb lGdxMrwNZSpbyGjxGFwbKjI+QNvBA6dVBDnLiCnc=
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: mohamed.boucadair@orange.com, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
Date: Tue, 11 Apr 2017 09:51:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="QU5DrroLB7f46CBMdIHothGu8PP5JWLVs"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7p4J082moEf7uKoKKU2KMkHx7Rs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 08:51:25 -0000

Hi Med,

On 11/04/17 09:15, mohamed.boucadair@orange.com wrote:
>> I hope that the IETF never publishes
>> draft-dolson-plus-middlebox-benefits; it makes claims about the
>> benefits of specific solutions for different use cases with the
>> goal of justifying those solutions.

> [Med] I'm afraid this is speculating about the intent of
> draft-dolson. Assured this is not the purpose of that document. The
> motivation is to document current practices without including any
> recommendation or claiming these solutions are superior to others.

Just to note that I completely agree with Martin's interpretation
of the thrust of this draft and I totally fail to see how your
argument above can be justified given that draft title, abstract
and even filename (and also the content;-). When the abstract
says "This document summarizes benefits" then I cannot interpret
that as other than being intended to justify the uses described.

A fairly thorough re-write to aim to describe the pros and cons
would be a different and more useful document. Similarly a draft
that strives to neutrally describe existing reality could maybe
be useful (*) but one that only describes middlebox friends with
"benefits" is not IMO beneficial ;-)

Cheers,
S.

(*) That is the argument for draft-mm-effect-encrypt, for which I
do support publication (apparently in disagreement with Martin in
that case:-)