Re: Confidentiality notices on email messages

Alessandro Vesely <vesely@tana.it> Thu, 14 July 2011 15:28 UTC

Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 002B021F85E3 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 08:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.842
X-Spam-Level:
X-Spam-Status: No, score=-4.842 tagged_above=-999 required=5 tests=[AWL=-0.123, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JqRRIaOa1t5d for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 08:28:47 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 5739021F85E2 for <ietf@ietf.org>; Thu, 14 Jul 2011 08:28:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1310657325; bh=hWb8v6KJmewjdkdZDCUCNTm+k9zBs+/G6Ow0eXZsBYo=; l=1116; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=LrIQayXCjCJscq5K/IWeCsVA1LvqLSax8jJ8hB/HbdF0INY0xQ2HOoBirjpNGOfFf ZwvImEKDpcpTPmIceAtT302sFARDBdnlLVLceSoNZeKW3FwOPf/yoveagKs5SsadLq v8s34e+SsbKYuinh5dy0sQXwj/LC1v8TV97laLdQ=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Thu, 14 Jul 2011 17:28:45 +0200 id 00000000005DC035.000000004E1F0B2D.00005C1A
Message-ID: <4E1F0B2C.3070401@tana.it>
Date: Thu, 14 Jul 2011 17:28:44 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Confidentiality notices on email messages
References: <20110714014835.9480.qmail@joyce.lan>
In-Reply-To: <20110714014835.9480.qmail@joyce.lan>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 15:28:52 -0000

On 14/Jul/11 03:48, John Levine wrote:
>>Yes, and perhaps disclaimers/confidentiality notices should be
>>standardized with their own MIME type to make automatic processing
>>easier so receivers of this kind of notice (mailing-list or other)
>>can respect the wishes of the sender.
> 
> That respect would of course be demonstrated by rejecting or
> discarding the mail unread, to avoid any possibility that it could
> fall into the wrong hands.

Yes, with the possible exception of recipients deploying a Treacherous
Computing environment that includes checks against forwarding or
replying with non fair use quotations of confidential messages.

> PS: Perhaps I should propose a revised RFC 5617 adding dkim=confidential.

One can sign the "Sensitivity" header field defined by RFC 2156.  It
can have the values "Personal" / "Private" / "Company-Confidential".

However, I received some messages bearing a confidentiality notice but
missing this field entirely.  Even the TC system above could hardly
cope with such inconsistent settings.  Do notices still retain any
legal value in such cases?