Re: Confidentiality notices on email messages

Alessandro Vesely <vesely@tana.it> Fri, 15 July 2011 14:55 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 B803021F85C6 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 07:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.836
X-Spam-Level:
X-Spam-Status: No, score=-4.836 tagged_above=-999 required=5 tests=[AWL=-0.117, 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 GN8sQg72+AWE for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 07:55:45 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id C9D0221F85B5 for <ietf@ietf.org>; Fri, 15 Jul 2011 07:55:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1310741743; bh=WFaJJmLTXkycuuRQHgXqXw8SDsC3V3fHb7E/sZ1W9kA=; l=1239; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=ctZF3jU4Rlln35c6IcUnFCvr2ON02OxFPV2nJj5uE9ew3I672CEKaMGkQwPPQLGyL j+jS1SGj7KtwkONzAX+UX7ou6+FcmlTkFB3CQFtG9Tuvx6jCT+rk8ryTRleldQkm/g bduGFsQwHxVNbcF1/rljVNCKXtPLLDw8TsL6tYbI=
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; Fri, 15 Jul 2011 16:55:43 +0200 id 00000000005DC045.000000004E2054EF.00005D93
Message-ID: <4E2054EE.7080108@tana.it>
Date: Fri, 15 Jul 2011 16:55:42 +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> <4E1F0B2C.3070401@tana.it> <2A06ADAE-70E2-4D0C-9809-66E01943B68E@gmail.com>
In-Reply-To: <2A06ADAE-70E2-4D0C-9809-66E01943B68E@gmail.com>
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: Fri, 15 Jul 2011 14:55:49 -0000

On 14/Jul/11 18:37, Will McAfee wrote:
> On Jul 14, 2011, at 11:28 AM, Alessandro Vesely <vesely@tana.it> wrote:
>> 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?
>
> They don't have legal value, period.

It is still an argument that one can bring before a court, e.g. when
claiming damage for unauthorized disclosure of confidential data.  We
all know that misaddressing can (and does) happen.  Stating that a
message is confidential might be worth in certain circumstances.
See http://www.out-law.com/page-5536

The point is that the semantic status of a message should be set by
the sender, properly.  It does not scale to leave it up to the
recipients to determine whether any possible notice is harmless,
inapplicable, or out of context.  Laws may allow it, protocols less so.

-- 
*NOTICE*
Access to this text is restricted to people having the right to do so.
-rwxrwxrwx