IETF Logo Mail Archive

Re: [perpass] draft-farrell-perpass-attack architecture issue

"Fred Baker (fred)" <fred@cisco.com> Wed, 15 January 2014 08:01 UTC

Return-Path: <fred@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 400B91AE31D; Wed, 15 Jan 2014 00:01:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.039
X-Spam-Level:
X-Spam-Status: No, score=-110.039 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.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 J4LYxEZu0Syy; Wed, 15 Jan 2014 00:01:08 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id 09F921AE317; Wed, 15 Jan 2014 00:01:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1113; q=dns/txt; s=iport; t=1389772856; x=1390982456; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=+qt8Wp8e3tnGjyXs5z30MckuWJ3rOqZie71mdJ/+jtc=; b=Dz/DSWC0m1spxmljGaLJeW7/xl2kxZYKQNj3tJ/jgJqaZZ5FDHvRd7Pf 1QAhvz6n1tXP2T9sW2Mc4KB/zfWQnb4NqcExvFvqlUPi25nMn+NXKTxEy SsBL35XzgXJNOZufpKYWyM2jMQoUfSgvtJGUvWHOZKYUwvbUUMKDC4iI0 s=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFAP8+1lKtJV2b/2dsb2JhbABagwuBDrp+gRUWdIIlAQEBBHkQAgEIEgYuIREXDgIEDgUOh2IDEb4ADYVhF4x0ghMHgySBEwSQN4ExhEqBbIxahTuDLYIq
X-IronPort-AV: E=Sophos; i="4.95,661,1384300800"; d="asc'?scan'208"; a="12965277"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-8.cisco.com with ESMTP; 15 Jan 2014 08:00:56 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0F80uTa025058 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Jan 2014 08:00:56 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.230]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Wed, 15 Jan 2014 02:00:56 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: draft-farrell-perpass-attack architecture issue
Thread-Index: AQHPEJW1zBILpAAtaEWpS3JElCG6BZqFJ00AgACGcgCAACV9gA==
Date: Wed, 15 Jan 2014 08:00:55 +0000
Message-ID: <6F7415D3-E58B-46F4-BF51-9E139AD0FDC1@cisco.com>
References: <52D43E69.6090001@cs.tcd.ie> <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com> <CADnDZ89sD-VtetCT6fcNrgzkjSMftZQpu+Khjpe8yPtVKnSqvA@mail.gmail.com>
In-Reply-To: <CADnDZ89sD-VtetCT6fcNrgzkjSMftZQpu+Khjpe8yPtVKnSqvA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.117]
Content-Type: multipart/signed; boundary="Apple-Mail=_E2B94636-9C25-4B4E-992B-0ABB04F57931"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Cc: perpass <perpass@ietf.org>, IETF-Discussion <ietf@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [perpass] draft-farrell-perpass-attack architecture issue
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: Wed, 15 Jan 2014 08:01:09 -0000

On Jan 14, 2014, at 9:46 PM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> The draft must include your questions, so that it can become a clear initial-BCP, or a clear plan draft. IMHO, the initial-BCP draft is not clear or not direct if it does not mention your questions,

I'm just one. But from my perspective, it must not only ask them, but answer them or outline how the answers might be arrived at.

v2.23.0 | Report a Bug | By Email