Re: [saag] draft-mm-wg-effect-encrypt-03
Stephen Farrell <stephen.farrell@cs.tcd.ie> Sun, 16 October 2016 14:58 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF691294D4 for <saag@ietfa.amsl.com>; Sun, 16 Oct 2016 07:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.732
X-Spam-Level:
X-Spam-Status: No, score=-4.732 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.431, SPF_PASS=-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 PPIpK-7nrbYs for <saag@ietfa.amsl.com>; Sun, 16 Oct 2016 07:58:08 -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 241D612948B for <saag@ietf.org>; Sun, 16 Oct 2016 07:58:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AC10BBE3E; Sun, 16 Oct 2016 15:58:05 +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 pYvfn1JG9Zc1; Sun, 16 Oct 2016 15:58:04 +0100 (IST)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E8F55BE39; Sun, 16 Oct 2016 15:58:03 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1476629884; bh=fXmveroeOB1ZPspQQtApia15vcPZFk19NigHyojk+I0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=eWsZvVw3eEWxHa0DDkDZbVW2kWQfNQALzBMMMNT2OH1oCxNdvaHyxl8tzibJHKeBH ntHIholnRkwpVbY6Tmpdojff3/l1QXs9DI60WgQfEGdQ5mpYJZb6NKaFE3nzn0s3dk HXcHxqI+B9DPd02zyd4lpvS8+JR2F9pwHjlb5GmU=
To: "MORTON, ALFRED C (AL)" <acmorton@att.com>, "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com>, "saag@ietf.org" <saag@ietf.org>
References: <1901933387.417923.1476328888389.ref@mail.yahoo.com> <1901933387.417923.1476328888389@mail.yahoo.com> <2122275166.97735.1476361683603@mail.yahoo.com> <4AF73AA205019A4C8A1DDD32C034631D45A1F2E5A4@NJFPSRVEXG0.research.att.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <b1e82376-68b9-f2d5-d06e-225b84b5e9ba@cs.tcd.ie>
Date: Sun, 16 Oct 2016 15:58:04 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <4AF73AA205019A4C8A1DDD32C034631D45A1F2E5A4@NJFPSRVEXG0.research.att.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms030203040203080508000102"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/wyor2Rsu11VcP7bFP-XLeR9rWqU>
Subject: Re: [saag] draft-mm-wg-effect-encrypt-03
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Oct 2016 14:58:10 -0000
Hi Al, I've a general question about this text but will just use the one example below. There are other examples in the text you just sent to the list... On 16/10/16 15:36, MORTON, ALFRED C (AL) wrote: > For an enterprise to avoid costly application down time and deliver > expected levels of performance, protection, and availability, some > form of traffic analysis sometimes including examination of packet > payloads can be a valuable asset. What is the goal of this text? Is it to a) describe current or historic practice or b) describe the changes that are needed when we properly protect things or c) argue that MITM behaviour is somehow necessary or correct? I think if the goal were (a) or (b) we would not use the language above ("valuable asset"), so I'm left wondering if this text is really aimed at (c). My understanding is that this draft aims at a mixture of (a) and (b), and I would have a problem with anything that seems to me like it has goal (c). To be clear: if asked to sponsor a document as AD I will not start a last call for anything with chunks of text that I think has goal (c). Goals (a) and (b) are of course useful so I'd be happy to progress such a document. I hope you and Kathleen take that into account when doing edits to the draft so that we can all save ourselves some cycles and angst:-) Thanks, S. PS: I realise that this is your initial edit of Nalini's text so it could be that additional edits are all that's needed here.
- Re: [saag] draft-mm-wg-effect-encrypt-03 nalini.elkins
- Re: [saag] draft-mm-wg-effect-encrypt-03 MORTON, ALFRED C (AL)
- Re: [saag] draft-mm-wg-effect-encrypt-03 Stephen Farrell
- Re: [saag] draft-mm-wg-effect-encrypt-03 MORTON, ALFRED C (AL)
- Re: [saag] draft-mm-wg-effect-encrypt-03 Stephen Farrell
- Re: [saag] draft-mm-wg-effect-encrypt-03 nalini.elkins
- Re: [saag] draft-mm-wg-effect-encrypt-03 Kathleen Moriarty
- Re: [saag] draft-mm-wg-effect-encrypt-03 Kathleen Moriarty