Re: silly legal boilerplate, was Regarding RIM's recent IPR disclosures

John Levine <johnl@iecc.com> Fri, 20 November 2009 05:36 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AD813A692E for <ietf@core3.amsl.com>; Thu, 19 Nov 2009 21:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -19.199
X-Spam-Level:
X-Spam-Status: No, score=-19.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QLQfiUwToh0R for <ietf@core3.amsl.com>; Thu, 19 Nov 2009 21:36:22 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 2D4643A6823 for <ietf@ietf.org>; Thu, 19 Nov 2009 21:36:22 -0800 (PST)
Received: (qmail 96684 invoked from network); 20 Nov 2009 05:36:19 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 20 Nov 2009 05:36:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0910; olt=johnl@user.iecc.com; bh=1AMWB6IDo+PlRyD9+8+AqrWJN5xhVKT0VogbZWXw1qU=; b=WtfJb1gv0c3YaND/TkFr3nnVuPotbs7Q4IRQqn6SMkPsj9dyNVXbXP3ZWi1WQl5Kx8TDYlJKyNMZ0Jxl/QWUnCEopdGxHvFEGDdm+O9hjdgiogeZuOcU/5C0ceWY4NrMuWYEN1jHrQdBHEir+IKg48+FyYqBfSTYzDA+CPWQMvE=
Date: Fri, 20 Nov 2009 05:36:18 -0000
Message-ID: <20091120053618.8729.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: silly legal boilerplate, was Regarding RIM's recent IPR disclosures
In-Reply-To: <4B06279D.8090201@dcrocker.net>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 20 Nov 2009 05:36:23 -0000

>It is a standard footer attached automatically by many attorney's
>email systems to all outgoing mail.

Many non-attorneys' mail, too, as in this case.

Yes, it's silly: as far as I can tell, confidentiality claims like
this are entirely unenforcable in the US except in a few arcane
situations that only apply to messages from one attorney to another.
It's just another example of pseudo-legal nonsense running amok.

But I have often been sorely tempted to return messages like this with
boilerplate of my own explaining that since I cannot accept the
sender's alleged restrictions, the message has been returned unread,
and since I have no way to evaluate the sender's status relative to
the party applying the notice, disclaimers in a message saying to
ignore the boilerplate won't help.

R's,
John


>>> From: "Andrew Allen" <aallen@rim.com>
>>> To: <ietf@ietf.org>
>>> Sent: Thursday, November 19, 2009 6:11 PM
>>> Subject: Regarding RIM's recent IPR disclosures
>> ...
>>> This transmission (including any attachments) may contain confidential
>>> information, privileged material (including material protected by the
>>> solicitor-client or other applicable privileges), or constitute non-public
>>> information. Any use of this information by anyone other than the intended
>>> recipient is prohibited. If you have received this transmission in error,
>>> please immediately reply to the sender and delete this information
>>> from your system. Use, dissemination, distribution, or reproduction
>>> of this transmission by unintended recipients is not authorized and
>>> may be unlawful.
>> ...
>> 
>> This is just plain silly.  Or is it willful ignorance of the "Note Well" terms?