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

"MORTON, ALFRED C (AL)" <acmorton@att.com> Sun, 16 October 2016 17:20 UTC

Return-Path: <acmorton@att.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 E27F2126D73 for <saag@ietfa.amsl.com>; Sun, 16 Oct 2016 10:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
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 BYMCsVsJc5pn for <saag@ietfa.amsl.com>; Sun, 16 Oct 2016 10:20:24 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E78F712943B for <saag@ietf.org>; Sun, 16 Oct 2016 10:20:24 -0700 (PDT)
Received: from pps.filterd (m0048589.ppops.net [127.0.0.1]) by m0048589.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id u9GHEdqB015883; Sun, 16 Oct 2016 13:20:21 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0048589.ppops.net-00191d01. with ESMTP id 264b1vu28v-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 16 Oct 2016 13:20:21 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u9GHKJR4017399; Sun, 16 Oct 2016 13:20:20 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u9GHKBCq017272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 16 Oct 2016 13:20:14 -0400
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Sun, 16 Oct 2016 17:19:54 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id u9GHJsF9025601; Sun, 16 Oct 2016 12:19:54 -0500
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.178.11]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id u9GHJjdp025296; Sun, 16 Oct 2016 12:19:46 -0500
Received: from exchange.research.att.com (njfpsrvexg0.research.att.com [135.207.255.124]) by mail-blue.research.att.com (Postfix) with ESMTP id D6E87F0412; Sun, 16 Oct 2016 13:19:44 -0400 (EDT)
Received: from NJFPSRVEXG0.research.att.com ([fe80::108a:1006:9f54:fd90]) by NJFPSRVEXG0.research.att.com ([fe80::108a:1006:9f54:fd90%25]) with mapi; Sun, 16 Oct 2016 13:19:44 -0400
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>
Date: Sun, 16 Oct 2016 13:19:43 -0400
Thread-Topic: [saag] draft-mm-wg-effect-encrypt-03
Thread-Index: AdInvbmBCRUIHXluRh2qI0NOpmy2CgADEYUw
Message-ID: <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>
In-Reply-To: <b1e82376-68b9-f2d5-d06e-225b84b5e9ba@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-10-16_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1610160315
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/KpEQadMWwtB1vMfz_SGzwL3oWAg>
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 17:20:28 -0000

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.

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.
>