Re: Important Information about IETF 76 Meeting Registration

"Doug Ewell" <doug@ewellic.org> Tue, 01 September 2009 04:19 UTC

Return-Path: <doug@ewellic.org>
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 0405E28C673 for <ietf@core3.amsl.com>; Mon, 31 Aug 2009 21:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 CTF4ZNvsjjMO for <ietf@core3.amsl.com>; Mon, 31 Aug 2009 21:19:26 -0700 (PDT)
Received: from p3plsmtpa01-01.prod.phx3.secureserver.net (p3plsmtpa01-01.prod.phx3.secureserver.net [72.167.82.81]) by core3.amsl.com (Postfix) with SMTP id 073E528C61A for <ietf@ietf.org>; Mon, 31 Aug 2009 21:19:25 -0700 (PDT)
Received: (qmail 2372 invoked from network); 1 Sep 2009 04:19:37 -0000
Received: from unknown (24.8.55.39) by p3plsmtpa01-01.prod.phx3.secureserver.net (72.167.82.81) with ESMTP; 01 Sep 2009 04:19:35 -0000
Message-ID: <FA73F2E150D54ACE9ADE44EF7E1F701C@DGBP7M81>
From: Doug Ewell <doug@ewellic.org>
To: ietf@ietf.org
References: <75673255-4128-466B-ABD6-F1F347388344@amsl.com><20090824090631.GB14653@nic.fr> <20090831091528.GA7037@nic.fr><ABFC8E86-1191-447B-BA0C-281FB2FED755@amsl.com><p06240830c6c1a8a9843f@[10.20.30.158]><02ca01ca2a5d$b81799c0$2846cd40$@com><p06240833c6c1b53e7753@[10.20.30.158]> <02d701ca2a63$89005630$9b010290$@com>
Subject: Re: Important Information about IETF 76 Meeting Registration
Date: Mon, 31 Aug 2009 22:19:33 -0600
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
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: Tue, 01 Sep 2009 04:19:27 -0000

Lawrence Rosen <lrosen at rosenlaw dot com> wrote:

>> Please note that you are now also collecting information that *is 
>> not* on the current blue sheets, namely "company/organization 
>> affiliation".
>
> I thought that was the "problem" to which you were alluding. And my 
> question remains: Is there any evidence that participants in IETF 
> should not provide their company/organization affiliation when they 
> participate? Is there something to hide?

Speaking only as an RFC author and WG participant, not as an IETF 
conference attendee, either in the past or in the foreseeable future...

I declined to state either my previous or current employer as my 
"affiliation" for either RFC 4645 or draft-4645bis, and instead listed 
myself as "Consultant," for two reasons: (1) neither employer has ever 
provided any support for my activities in the LTRU WG, and (2) a certain 
particularly ill-willed participant in LTRU had already used another 
participant's "affiliation" against him, writing to the legal department 
of that person's employer and demanding that he be professionally 
disciplined, something I didn't feel like risking for myself.

--
Doug Ewell  *  Thornton, Colorado, 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  ˆ