Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02

Eliot Lear <lear@cisco.com> Mon, 09 December 2013 14:53 UTC

Return-Path: <lear@cisco.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B51B1AE316; Mon, 9 Dec 2013 06:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level:
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 kHYXliM4jfO9; Mon, 9 Dec 2013 06:53:23 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 17B991AE308; Mon, 9 Dec 2013 06:53:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1589; q=dns/txt; s=iport; t=1386600799; x=1387810399; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=ohCOPrjeKA2qe0J5RJgyJNXM4oHa2cMFRtyET91duTQ=; b=Cfo5FfUrUqSbfQdkaEgjEFqrXwDjgPQDffQWgafxtDF5YvrP0Qn0o0tj EzGoL41vTYpQv5OnYm/RvAda9Q9hgk0qI1hKHv6xhDyav5hlZQIbpG87A fQvCqowjeBO8ULuPIx4aW4v0IQMKGEFctZXL58dzMr2xNWQvPqh41jeAs Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8FAIjYpVKQ/khN/2dsb2JhbABZgwc4g1K2FoEvFnSCJQEBAQMBAQIgMSQGCwsaAgUWCwICCQMCAQIBFi8GAQwIAQGHeAYNsX2PLReBKY0WAQFWgmuBSAOVRYJPgTCQY4FrgT87gTU
X-IronPort-AV: E=Sophos;i="4.93,858,1378857600"; d="scan'208";a="1304075"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 09 Dec 2013 14:53:18 +0000
Received: from ams3-vpn-dhcp5161.cisco.com (ams3-vpn-dhcp5161.cisco.com [10.61.84.40]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rB9ErDuM022387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Dec 2013 14:53:14 GMT
Message-ID: <52A5D962.3090708@cisco.com>
Date: Mon, 09 Dec 2013 15:53:22 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, perpass <perpass@ietf.org>, IETF@ietf.org
References: <52A5B79E.2040202@cisco.com> <52A5C458.200@cs.tcd.ie>
In-Reply-To: <52A5C458.200@cs.tcd.ie>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Dec 2013 14:53:25 -0000

Hi Stephen,

I'm not comfortable with having this discussion just in perpass, since
the impact of what you are proposing is quite broad, as is my concern. 
This is an IETF last call comment.  The IESG directed those comments to
go to the IETF list.

On 12/9/13 2:23 PM, Stephen Farrell wrote:

>  The chair you mean is Mark
> Nottingham in this [1] mail to the httpbis list.
>
>    [1] http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/1453.html
>
> I definitely did not read him the way you appear to have and
> that distinction matters. If you are the only one to take him
> as saying that then I guess you'd agree that your changes
> would be based on a fallacy. Maybe Mark can clarify but I think
> its already crystal clear that he was not saying "ignore
> everything else" - I'd be stunned if that was what he meant.

The point was and is that I wanted to respond to him to clarify that one
should not ignore everything else, when in fact I found the opposite:
since you laid out explicitly only network management considerations,
the implication is that all other considerations are excluded.  The
purpose of my change is to remove that implied exclusion, and leave this
to working groups to wrestle with.  I'm happy with Robin's wording as
well, and I don't mind you proposing other wording further to your
liking, so long as we recognize that there are other considerations.

If you can show me where in your text it allows for those other
considerations as I believe I've done in the reverse, I'll be happy to
stand corrected.

Eliot