Re: Possible RFC 3683 PR-action
"Doug Ewell" <doug@ewellic.org> Mon, 31 March 2008 04:01 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C70F28C419; Sun, 30 Mar 2008 21:01:28 -0700 (PDT)
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 03EC628C1E8 for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 21:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.285
X-Spam-Level:
X-Spam-Status: No, score=0.285 tagged_above=-999 required=5 tests=[AWL=0.469, BAYES_40=-0.185, STOX_REPLY_TYPE=0.001]
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 wJfb99YmKwXv for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 21:01:25 -0700 (PDT)
Received: from smtpauth04.prod.mesa1.secureserver.net (smtpauth04.prod.mesa1.secureserver.net [64.202.165.95]) by core3.amsl.com (Postfix) with SMTP id 9A1E328C405 for <ietf@ietf.org>; Sun, 30 Mar 2008 21:00:48 -0700 (PDT)
Received: (qmail 14124 invoked from network); 31 Mar 2008 04:00:45 -0000
Received: from unknown (76.167.184.182) by smtpauth04.prod.mesa1.secureserver.net (64.202.165.95) with ESMTP; 31 Mar 2008 04:00:32 -0000
Message-ID: <005b01c892e3$c3cfb4e0$6501a8c0@DGBP7M81>
From: Doug Ewell <doug@ewellic.org>
To: ietf@ietf.org
References: <mailman.13371.1206459532.4854.ietf@ietf.org><DDB6DE6E9D27DD478AE6D1BBBB83579562DEC72DED@NA-EXMSG-C117.redmond.corp.microsoft.com><871w5yn5ou.fsf@mocca.josefsson.org> <20080325163756.GF16358@mit.edu>
Subject: Re: Possible RFC 3683 PR-action
Date: Sun, 30 Mar 2008 21:00:30 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
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-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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
Theodore Tso <tytso at MIT dot EDU> wrote: > A valid technical concern is easy to deal with. If they provide an > idea, I suspect a cautious working group chair might insist on knowing > their real name and company affiliation, since there have been past > examples where companies have tried to inject patented technologies > into a standards specification. I suppose a few personal notes might be in order regarding "company affiliation," since I've served as editor for both RFC 4645 and draft-ietf-ltru-4645bis, both products of the LTRU Working Group that started this thread, and both under the title "Consultant" instead of a company or other organizational affiliation. There are a couple of reasons. One is that my company, which had apparently been embarrassed by employees posting personal opinions on an industry message board in a way which made them sound like official company positions, instituted a set of "Internet and Electronic Communications Guidelines" some years ago which prohibits employees from "stating their [company] affiliation over the Internet" unless required as part of their job description. This went way too far in my opinion -- stating that you work for XYZ Company is quite different from stating that you represent the official position of XYZ Company -- but it is the approved policy, it allows for termination in the event of violation, and we all signed it. The other reason is that three years ago, there was an attempt by -- surprise! -- JFC Morfin to contact the professional employer of one of the LTRU participants and single him out for corporate disciplinary action, in retaliation for his support of a PR-action against Morfin. Together with the "Internet and Electronic Communications Guidelines," this hostile and unprofessional action further convinced me that it was not in my best interests to disclose my employer in documents published on the Internet, and especially not in an RFC where the text: D. Ewell, Ed. XYZ Company might present the impression, rightly or wrongly, of company sponsorship or representation. Next week I start work for a new employer, and I hope they will have a more enlightened attitude toward employees "stating their [company] affiliation over the Internet" and will understand that stating one's affiliation in an IETF document is a matter of author identification, not corporate sponsorship. In passing, I will restate that my involvement with the LTRU has always been individual in nature, and has never been sponsored or sanctioned by any commercial interest nor driven by any corporate goal, although I believe the work may be of value to any entity (corporate or otherwise) concerned with the identification of linguistic content. -- Doug Ewell * Fullerton, California, USA * RFC 4645 * UTN #14 http://www.ewellic.org http://www1.ietf.org/html.charters/ltru-charter.html http://www.alvestrand.no/mailman/listinfo/ietf-languages ˆ _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: [Ltru] Possible RFC 3683 PR-action LB
- Re: [Ltru] Possible RFC 3683 PR-action Randy Presuhn
- Re: [Ltru] Possible RFC 3683 PR-action Russ Housley
- Re: [Ltru] Possible RFC 3683 PR-action LB
- Re: [Ltru] Possible RFC 3683 PR-action Sam Hartman
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: [Ltru] Possible RFC 3683 PR-action Russ Housley
- RE: [Ltru] Possible RFC 3683 PR-action Christian Huitema
- Re: [Ltru] Possible RFC 3683 PR-action Theodore Tso
- Re: [Ltru] Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- RE: [Ltru] Possible RFC 3683 PR-action Russ Housley
- RE: [Ltru] Possible RFC 3683 PR-action Wes Beebee (wbeebee)
- Re: [Ltru] Possible RFC 3683 PR-action LB
- RE: Possible RFC 3683 PR-action Tamir Melamed
- Re: [Ltru] Possible RFC 3683 PR-action Harald Tveit Alvestrand
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Spencer Dawkins
- Re: Possible RFC 3683 PR-action David Conrad
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action John Levine
- Re: Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Michael Thomas
- Re: Possible RFC 3683 PR-action Melinda Shore
- RE: [Ltru] Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Simon Josefsson
- RE: Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Melinda Shore
- Re: [Ltru] Possible RFC 3683 PR-action Spencer Dawkins
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Edward Lewis
- Re: Possible RFC 3683 PR-action Melinda Shore
- Re: Possible RFC 3683 PR-action Michael Thomas
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Joel Jaeggli
- Re: Possible RFC 3683 PR-action Edward Lewis
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Hallam-Baker, Phillip
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Thierry Moreau
- Re: Possible RFC 3683 PR-action Simon Josefsson
- RE: Possible RFC 3683 PR-action Darryl (Dassa) Lynch
- Pseudonym side-effects [Re: Possible RFC 3683 PR-… Brian E Carpenter
- Corporate side-effect [Re: Possible RFC 3683 PR-a… Brian E Carpenter
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action stewe
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Doug Ewell
- Re: Possible RFC 3683 PR-action Stephan Wenger
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Bert
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- <draft-ietf-ipr-3978-incoming-08.txt> as a BCP (w… Frank Ellermann
- Re: Possible RFC 3683 PR-action John C Klensin
- RE: Possible RFC 3683 PR-action Hadriel Kaplan
- Re: Possible RFC 3683 PR-action Doug Ewell
- Re: Possible RFC 3683 PR-action John C Klensin
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Brian E Carpenter
- Re: Possible RFC 3683 PR-action Harald Tveit Alvestrand
- Re: Possible RFC 3683 PR-action John C Klensin
- Re: Possible RFC 3683 PR-action Dean Anderson