Re: [saag] draft-mm-wg-effect-encrypt-03

<nalini.elkins@insidethestack.com> Mon, 17 October 2016 01:48 UTC

Return-Path: <nalini.elkins@insidethestack.com>
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 C426A1294AB for <saag@ietfa.amsl.com>; Sun, 16 Oct 2016 18:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 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_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 jW5VhsoqGr7L for <saag@ietfa.amsl.com>; Sun, 16 Oct 2016 18:48:14 -0700 (PDT)
Received: from nm27.bullet.mail.ne1.yahoo.com (nm27.bullet.mail.ne1.yahoo.com [98.138.90.90]) (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 26FB41293FE for <saag@ietf.org>; Sun, 16 Oct 2016 18:48:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1476668893; bh=0u9aeANclpN62l0cooBAhDXX8QxnqMKiDFEGy77n7wo=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=eohWj8cxl1PCf1cm6kuGX0SbTGRYfrlsBC+CAOMlGYkO6UBAjGLLzR7Sqh223m4KWyQF2a6wFCDt0xlqdb43tjcgs5Yj17kHh1OVZxD8qPjOzmeZLtqNyQeHhq0wfgDRKX9+m2yC+OzE3g+HRKy0jF0HkXy3eVryXZm64EZ+9B9Qd6fvaUOeff3TEeaqpibHrXxVqkqNmV42aOqulbLHcpg9zyVcssJz2ERiNOgpdzcorARFwB8ve9/lnc1ZfgNMon+8LhmXkN1fdJZGdjIPhZ9US8x9QUNZRNhE579bwLub2EyN2MgVLOdtZB47FGS+2iziDtqisLpe0fxoTNrZBw==
Received: from [98.138.100.118] by nm27.bullet.mail.ne1.yahoo.com with NNFMP; 17 Oct 2016 01:48:13 -0000
Received: from [98.138.89.164] by tm109.bullet.mail.ne1.yahoo.com with NNFMP; 17 Oct 2016 01:48:13 -0000
Received: from [127.0.0.1] by omp1020.mail.ne1.yahoo.com with NNFMP; 17 Oct 2016 01:48:13 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 612103.58107.bm@omp1020.mail.ne1.yahoo.com
X-YMail-OSG: lsA5q_IVM1lvCy_IrSPxx5V49ApMP_TgqlqLMcw89mBPEwTK4nIfPBQBdeaW7Xo IDZviJ0Se875GjEaWOla1ECTZfIbwcnpEn4wOOZzEoRK0M1KKlr.WS7RSUP1SXgAgf6pmRBXyC7r V6J3qVii8yeHJA2.f.61Gv2qwqQCgGhariAiSFtS4ooajcrBCaJBylOTTdsRzn1Wqik_mpg8Kqa9 TYDCyhkjCorDPeVnrTmN95zLdaZRKhDF_OVw3..vStEZJa.1INtQS2exoJeCLrPbO_NWl8IoGeMK rvddQh4FCVnhoKee0YvTiASpCRb3E57FOmnpeaC1FVk6O5IgDqIz29tGCV9OjKJq0u_ypel8CPVf oQBd7V7MlO6oc3ubd1TC9glIGPkPJQBYmAycNOJyOTki1RHVsNhuOqaB90XdSmjhH87Xb4tpIFJ9 EGb_coLgjopQ3K1zeDp3iHpxGH12eHkNb0C3MsGyC5FoD6CzgpnkWyK5_Qoh7zAJHNMp3N9qmNVV ENQxwM_LfB9GwaqwnI56ozPm85sfS2OU_Uwfb7S_qITk-
Received: from jws200118.mail.ne1.yahoo.com by sendmailws144.mail.ne1.yahoo.com; Mon, 17 Oct 2016 01:48:13 +0000; 1476668893.206
Date: Mon, 17 Oct 2016 01:48:12 +0000
From: nalini.elkins@insidethestack.com
To: "MORTON, ALFRED C (AL)" <acmorton@att.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "saag@ietf.org" <saag@ietf.org>
Message-ID: <966336503.869322.1476668892606@mail.yahoo.com>
In-Reply-To: <4AF73AA205019A4C8A1DDD32C034631D45A1F2E5A8@NJFPSRVEXG0.research.att.com>
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> <b1e82376-68b9-f2d5-d06e-225b84b5e9ba@cs.tcd.ie> <4AF73AA205019A4C8A1DDD32C034631D45A1F2E5A8@NJFPSRVEXG0.research.att.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_869321_586531185.1476668892600"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/5qOobE2HY98FYxM4u5kbi2rLhvE>
Subject: Re: [saag] draft-mm-wg-effect-encrypt-03
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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: Mon, 17 Oct 2016 01:48:16 -0000

Stephen & Al,
My comments inline. Thanks,
Nalini ElkinsInside Products, Inc.www.insidethestack.com(831) 659-8360

      From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
 To: Stephen Farrell <stephen.farrell@cs.tcd.ie>; "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com>; "saag@ietf.org" <saag@ietf.org> 
 Sent: Sunday, October 16, 2016 10:19 AM
 Subject: RE: [saag] draft-mm-wg-effect-encrypt-03
   
>Hi Stephen, thanks for sharing an example that needs fix.
>I re-worded a paragraph that repeated statements
>from an earlier section. I believe Nalini was describing
>current capabilities, and implying a gap if there is 
>no replacement to aid network management in the future.
>This is the fundamental tension, as I understand it.
Definitely.    Sorry if the wording is awkward.   I was trying to not imply any solutions as that is not in the spirit of this draft.
I hope that the many issues (including a few of the ones that I suggested) in network management and diagnostics that have been pointed out by this draft will spark the conversation about how we might go about resolving them.   Maybe this is new tools, strategies or protocols.

>>Stephen wrote:
>> 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).

>I agree to substitute another phrase for "valuable asset"
>since it's distracting; "current capability" or other, WFM.
>I didn't write "is a required capability", that would be 
>more consistent with goal c).

>Clearly, changes in current management practices will be needed,
>and that process could be more efficient with constructive input
>from all involved. Understanding the many gaps is the first step,
>and IMO, what this memo is about.  No arguing for solutions,
>MITM or otherwise.

>I hope this helps,
>Al


> -----Original Message-----
> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
> Sent: Sunday, October 16, 2016 10:58 AM
> To: MORTON, ALFRED C (AL); nalini.elkins@insidethestack.com;
> saag@ietf.org
> Subject: Re: [saag] draft-mm-wg-effect-encrypt-03
> 
> 
> 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.
>