Re: [apps-discuss] Stephen Farrell's No Objection on draft-ietf-appsawg-sieve-duplicate-09: (with COMMENT)
Barry Leiba <barryleiba@computer.org> Thu, 26 June 2014 11:13 UTC
Return-Path: <barryleiba@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D33C01B2B12; Thu, 26 Jun 2014 04:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 tsSp9yAssiBr; Thu, 26 Jun 2014 04:13:43 -0700 (PDT)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 694A11B2A61; Thu, 26 Jun 2014 04:13:42 -0700 (PDT)
Received: by mail-lb0-f176.google.com with SMTP id w7so2760482lbi.7 for <multiple recipients>; Thu, 26 Jun 2014 04:13:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=xzarMRqKFdMClecRtCYbiK/YZ2JE0pM0WXKSFgluzOc=; b=BS2GrvYohRK/OgTvgd9IhFmniKKNG/MdCGLg+MzL2zb7a+Rk3YebL4jFYYAriNQMBl +4Iz6rwLYxKZySI7lHNBx5LBuRUE94n6gp6q9uZ3siKBJIW5SGRiU7ZR4CxxCAwGo97A xJkPNoB52mg5S5+4KQX6432oApPHXNgpKkOa/38Qt/MZJNkw/Dl9x1sFlpttO3R8yX/w 2ZbJsuG7YHjohwcLcm0yCCEb2EVkCl/XAlUngZ3r1BcZ7hu/cvpVBAOjLl2hyxxSKtTP hFKEchEt3Q0YdpItNChxWiAk1Wm4fAMbi2r0QhDJBz1QuTuo2FoAiXCF9iO953cY9Fmw mUUw==
MIME-Version: 1.0
X-Received: by 10.112.173.201 with SMTP id bm9mr10005217lbc.16.1403781220621; Thu, 26 Jun 2014 04:13:40 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.152.104.80 with HTTP; Thu, 26 Jun 2014 04:13:40 -0700 (PDT)
In-Reply-To: <20140626104727.25948.90086.idtracker@ietfa.amsl.com>
References: <20140626104727.25948.90086.idtracker@ietfa.amsl.com>
Date: Thu, 26 Jun 2014 07:13:40 -0400
X-Google-Sender-Auth: 1s7Ouwep1h-15tAUQA4h5YuO-i4
Message-ID: <CALaySJK=vR=hF2=icKT=o_PHYTGiGxnZmBnXiLZR_PW2KKO6ow@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/oPkn1ie8WbpgNxJi_DjGQvobru0
Cc: "appsawg-chairs@tools.ietf.org" <appsawg-chairs@tools.ietf.org>, "ned+ietf@mrochek.com" <ned+ietf@mrochek.com>, The IESG <iesg@ietf.org>, Apps Discuss <apps-discuss@ietf.org>, "draft-ietf-appsawg-sieve-duplicate@tools.ietf.org" <draft-ietf-appsawg-sieve-duplicate@tools.ietf.org>
Subject: Re: [apps-discuss] Stephen Farrell's No Objection on draft-ietf-appsawg-sieve-duplicate-09: (with COMMENT)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 11:13:44 -0000
> I wondered what'd happen if you used a DKIM-Signature > header with this, but I guess it should just work. Yeh, I think it should just work. For that case, I actually think the best approach would be to use the Variables extension to extract the hash from the DKIM "b=" tag, and use that for the unique ID. But even using the whole header field should work fine. > However, I don't recall if that header value is ok to > compare case-sensitive (e.g. "d=" might not be?). I'd think that shouldn't be an issue. If you're really looking for duplicates, it's probably fine to only consider them duplicates if they're exact matches. > Nothing to do with this draft in the end, but I think the > security/privacy discussion ended up raising a couple of > interesting issues that might be worth revisiting if/when > someone has energy: those were a) if we could make some > good privacy-friendly (but also admin friendly) > recommendations about logging mail and b) if we could > consider the privacy implications of sieve scripts or > other filters (I liked the "stupid boss" folder name one, > and am guilty of that for some of my own mail:-) and what > those might expose. For (a) I could imagine a useful > informational RFC, not sure for (b). Yeh. I think a "privacy issues with email deployment" document might be interesting to have. I don't know who would have the interest and energy to do it. Barry
- [apps-discuss] Stephen Farrell's No Objection on … Stephen Farrell
- Re: [apps-discuss] Stephen Farrell's No Objection… Barry Leiba