My company has just changed to adding
these disclaimers to e-mail. I have started to work the issue with our IT
department and will let people know if there is an easy work-around to pin-hole
through the disclaimer when sending e-mail to particular domains or addresses.
For now one thing that works is to use a personal e-mail account and create a
specific sub-account for ieee business.
From: Geoff Thompson
Sent: Thursday, July 18, 2002 1:26
email@example.com; firstname.lastname@example.org; email@example.com;
firstname.lastname@example.org; email@example.com; firstname.lastname@example.org;
email@example.com; firstname.lastname@example.org; John.J.Verscaj@us.ul.com;
Subject: [802SEC] UL and 802
policy about restriction notices in e-mails.
I just got off of the phone with John Verscaj, Vice President and General Counsel of
Underwriters Labs. He (effectively) said he understands our position and will
not oppose it further. He is investigating options with the IT Department of UL
and with the upper management of UL that will solve the problem at the UL end.
The current situation is that (as far as he knows) the "Internet E-mail
Confidentiality Disclaimer" is automatically appended to all external
e-mails as they leave UL.
Until he gets that problem solved I suggested that UL could correspond with us
via fax, postal mail or an outside e-mail account. I said that we would respond
promptly and were happy to work with them.
So, as far as I am concerned, this is no longer a priority issue. This episode
does point out that it would be useful to have relevant text in our P&P. To
that end (as promised earlier), I would like to put the following text in as a
proposed addition to the IEEE Project 802 Operating Rules. As an interested
party and voting member of 802.3, I would also propose the same text for
adoption in 802.3, to be removed upon adoption by 802. This is only because the
adoption track for non-controversial issues in 802.3 is faster.
Bob O'Hara, please put me down for a November Monday agenda item to propose the
following addition to the Operating Rules:
(We currently have no "Procedure" for how to achieve
"openness" in our meetings. I think this is a start on the more
general topic. I believe that the text is an accurate
representation of our long standing policy.)
(Proposed documentation of existing) 802 Policy regarding restrictive notices
IEEE 802 operates in an open manner. To that end, no material submitted
to IEEE 802, or any of its sub-groups, will be accepted or considered if that
material contains any statement that places any burden on the recipient(s) with
respect to confidentiality or copyright. This policy specifically includes e-mail.
Any material that has such a "Confidentiality Disclaimer" on it is
not acceptable. The purpose of such a disclaimer is to transfer some level of
responsibility to the recipient for deciding whether or not it is appropriate
to disclose, use, disseminate, copy, post or otherwise distribute, the
IEEE 802 accepts no such responsibility.
The most effective way for 802 to decline any such responsibility is to not
accept material with such a disclaimer.
Correspondence with 802 groups will not be confidential. It is very likely that
any such correspondence (in addition to being discussed in open meetings) will
be posted in the open portion of our web-site and thus will be disclosed,
disseminated and distributed. Anyone who wishes to correspond with an 802 group
must understand and accept this as a condition of sending us any documentation.
Inclusion of any restrictive notice is contrary to, and negates, any indication
of acceptance of the IEEE 802 policy of openness.
Copyrighted works may be accepted as submissions for inclusions in drafts only
with an appropriate release. Copyrighted works may be referenced in drafts and
presentations if they are available on reasonable and non-discriminatory terms.
| Geoffrey O.
| Vice Chair, IEEE
| Nortel Networks, Inc. M/S: P79/06/B04 |
| 4655 Great America
| P. O. Box 58185
| Santa Clara, CA 95052-8185
| Phone: +1 408 495
| Fax: +1 408 495
| Please see the IEEE 802 web page at |