[Techspec] RE: RFC Author Count and IPR

"Gray, Eric" <Eric.Gray@marconi.com> Wed, 24 May 2006 19:37 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FizB6-0006mb-H9; Wed, 24 May 2006 15:37:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiyP4-0007Gm-Tr; Wed, 24 May 2006 14:48:18 -0400
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiyP3-0007lz-Gi; Wed, 24 May 2006 14:48:18 -0400
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id k4OImGLB011003; Wed, 24 May 2006 14:48:16 -0400 (EDT)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA13789; Wed, 24 May 2006 14:48:16 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2657.72) id <K7CACPX6>; Wed, 24 May 2006 14:48:15 -0400
Message-ID: <313680C9A886D511A06000204840E1CF0E2488AD@whq-msgusr-02.pit.comms.marconi.com>
From: "Gray, Eric" <Eric.Gray@marconi.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, Russ Housley <housley@vigilsec.com>
Date: Wed, 24 May 2006 14:48:08 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
X-Mailman-Approved-At: Wed, 24 May 2006 15:37:54 -0400
Cc: ipr-wg@ietf.org, ietf@ietf.org, techspec@ietf.org, rfc-editor@rfc-editor.org
Subject: [Techspec] RE: RFC Author Count and IPR
X-BeenThere: techspec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" <techspec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/techspec>
List-Post: <mailto:techspec@ietf.org>
List-Help: <mailto:techspec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=subscribe>
Errors-To: techspec-bounces@ietf.org

Sam, et al,

	There are so many things tied up in this, that I am
afraid it is bound to turn into a rat-hole.

	For one thing, I thought Russ was talking about the
complication that arise from whether or not the BCP 78/79
stuff applies to people who made some contribution but are
not listed as "Authors".  I may have missed his point, but
this probably is an issue as there are other things in IPR
than "copyrights".

	For another, there is a clear distinction between
attribution and being listed as an author.  Most drafts I've
seen acknowledge the people making contributions.

	Also, RFCs are not (at least usually) a compilation of
related works by separate authors. An RFC typically requires
some unification and typically this is performed by one or 
more editors.  Because of churn-and-merge complexity, it is
usually the case that there is only one "editor" at any given
moment, and the list of "token holders" is both well defined
and small - consequently is is quite reasonable to ask that
a long list of authors be replaced by a shorter list of the
people who actually took turns as editors.

	I think the biggest issue is that the RFC Editor has
established guidelines that use a fixed number.  This can
lead to rather arbitrary decisions about who is an editor,
author or contributor.  Probably a better approach would be
to explicitly define what the RFC Editor means by the terms
contributor, author, editor and - perhaps - something even
more specific that that (e.g. - final editor?) and then
saying that some number of names MAY be listed on the first 
page and that the approach to determining what names should
be included is to pick the category that has no more than
that many in the list.

	I was pretty much under the impression that this is 
the informal approach used now. 

--
Eric

--> -----Original Message-----
--> From: Sam Hartman [mailto:hartmans-ietf@mit.edu] 
--> Sent: Wednesday, May 24, 2006 2:06 PM
--> To: Russ Housley
--> Cc: rfc-editor@rfc-editor.org; ietf@ietf.org; 
--> techspec@ietf.org; ipr-wg@ietf.org
--> Subject: Re: RFC Author Count and IPR
--> 
--> >>>>> "Russ" == Russ Housley <housley@vigilsec.com> writes:
--> 
-->     Russ> I am concerned that the current RFC Editor practice that
-->     Russ> limits the number of authors is in conflict with the IETF
-->     Russ> IPR policies.  The RFC Editor currently limits the author
-->     Russ> count to five people.  Recent IPR WG discussions make it
-->     Russ> clear to me that authors retain significant copyright.
--> 
--> [There is this concept in US copyright law called a joint work.  I'm
--> ignoring that concept for the moment basically because I don't
--> understand how it applies to either software or text developed using
--> an open process.  As far as I can tell, no one else understands it
--> either.  Please be aware that this may be a huge gap in my advice.]
--> 
--> So, here we have a conflicting definitions problem.
--> 
--> The author of a work retains the copyright interest.  That's true if
--> if I'm listed as an author or not.
--> 
--> If I write text and do not assign the copyright to someone, I retain
--> copyright interest in that text.
--> 
--> So the sixth person still owns the copyright interest in 
--> the text they
--> write even if they are not listed.
--> 
--> That means if you have unlisted authors who have contributed
--> significant chunks of text, you still need to get their clearance to
--> do anything interesting with that text.
--> 
--> _______________________________________________
--> Ietf mailing list
--> Ietf@ietf.org
--> https://www1.ietf.org/mailman/listinfo/ietf
--> 

_______________________________________________
Techspec mailing list
Techspec@ietf.org
https://www1.ietf.org/mailman/listinfo/techspec