IETF Logo Mail Archive

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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 18 October 2016 21:36 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 1255412989F for <saag@ietfa.amsl.com>; Tue, 18 Oct 2016 14:36:05 -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 unaUGUf_e2QY for <saag@ietfa.amsl.com>; Tue, 18 Oct 2016 14:36:02 -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 789C51294E7 for <saag@ietf.org>; Tue, 18 Oct 2016 14:36:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E2DB1BE2E; Tue, 18 Oct 2016 22:35:59 +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 EpjUEIOs8XHn; Tue, 18 Oct 2016 22:35:53 +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 4AD7BBE2C; Tue, 18 Oct 2016 22:35:53 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1476826553; bh=uHRzbNAcrQePRGPn8n4Dzp3oBc/821/aqoxoExDeqkY=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=v6HjGOGfbth+G7uwBa2Z3OTAqdP4P+IRdQn4AinBwvaBkd2ur/o6RlZ2/E6/XSQSo Ksdu+xHE7STMJ0GNyOGRpO3kmt+MFfWo12xD1h+Y9+dNnDT54CIx2dmwOzv49GutWY rxv4zxCn0ffLAhjzTlacL6WPbo47nz9f5BVQTaG8=
To: nalini.elkins@insidethestack.com, Security Area Advisory Group <saag@ietf.org>
References: <1291206601.2408471.1476826341029.ref@mail.yahoo.com> <1291206601.2408471.1476826341029@mail.yahoo.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <e2b988c2-dda7-018d-4c26-fbf106ad51c2@cs.tcd.ie>
Date: Tue, 18 Oct 2016 22:35:53 +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: <1291206601.2408471.1476826341029@mail.yahoo.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms070307070904020007030000"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/6HtB7Vm8U1PVyDk-CYbJsTSZ5K4>
Cc: "MORTON ALFRED C (AL)" <acmorton@att.com>
Subject: Re: [saag] draft-mm-wg-effect-encrypt-03 - Next Steps
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: Tue, 18 Oct 2016 21:36:05 -0000


On 18/10/16 22:32, nalini.elkins@insidethestack.com wrote:
> A very interesting question.  It leads me to wonder if there are
> other classes of information which need to be exposed (or logged)
> also?  And then doing so while maintaining privacy & security.  (I am
> also looking forward to the information that may be provided by the
> new PLUS WG.)

Please consult the archives/minutes for the SPUD/PLUS BoF.
(Not so far a tremendous success - the most recent mail I
saw on that explicitly said that rumours of the idea's
demise were exaggerated;-)

S.

v2.23.0 | Report a Bug | By Email