IETF Logo Mail Archive

Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewandcomments on a proposed Work-Around to the Pre-5378 Problem

"Randy Presuhn" <randy_presuhn@mindspring.com> Sun, 11 January 2009 00:25 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 [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1A293A69B6; Sat, 10 Jan 2009 16:25:51 -0800 (PST)
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 60CA13A6921 for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 16:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level:
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599]
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 aIHS3zIXqIWo for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 16:25:49 -0800 (PST)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by core3.amsl.com (Postfix) with ESMTP id 8481B3A6834 for <ietf@ietf.org>; Sat, 10 Jan 2009 16:25:49 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=ejcRFX6mSK3g9dNlnXgc/dU9PPdkh8U0NdAKk7CoaJabgKOvEOj0jzev8IpkE9aG; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [66.167.204.13] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1LLo91-0007TV-HA for ietf@ietf.org; Sat, 10 Jan 2009 19:25:35 -0500
Message-ID: <002b01c97383$886992a0$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: 'IETF Discussion' <ietf@ietf.org>
References: <70873A2B7F744826B0507D4B84903E60@noisy><FB8A848E-E415-4CDE-9E3F-5C74A5614F18@cisco.com><49678B2A.8000100@dcrocker.net> <20090109181503.GP24908@verdi><6E372F257B0C42E7AB9B7DA6231FF4E4@LROSENTOSHIBA><p06240800c58d5466241b@[10.227.48.131]><DBAA71AA401E5398212B1E03@PST.jck.com><9AA833EF821F45538CCE8C28B85B931A@LROSENTOSHIBA><20090110111627.GA5090@boreas.isi.edu><F5012CBF1E0242069FA63B218E901C5A@LROSENTOSHIBA> <20090110224257.GA28290@boreas.isi.edu>
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewandcomments on a proposed Work-Around to the Pre-5378 Problem
Date: Sat, 10 Jan 2009 16:28:31 -0800
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f173ecfea91378640de0dd669d66a6e8314b350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 66.167.204.13
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi -

> From: "Bill Manning" <bmanning@ISI.EDU>
> To: "Lawrence Rosen" <lrosen@rosenlaw.com>
> Cc: "'IETF Discussion'" <ietf@ietf.org>
> Sent: Saturday, January 10, 2009 2:42 PM
> Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewandcomments on a proposed Work-Around to the Pre-5378
Problem
...
> er... thats -NOT- what I was trying to point out.  The IETF
> was given permission to publish an authors work but was not
> allowed to impune joint authorship. The IETF did not create the
> work - it provided a publication vehicle.
...

That certainly was *not* my understanding when I offered my services
as an editor for the various IDs and RFCs where I've functioned in
that role.  I, and I'm sure many others in those working groups,
thought those documents were products of the working group,
which did that work for the IETF.  For me to claim authorship of,
e.g., RFC 3417, would be intellectually dishonest.  For the IETF
to claim that I was its author, rather than merely an editor acting
on the instruction of a working group, is downright delusional.

Randy


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email