[Techspec] Re: RFC Author Count and IPR

Ken Raeburn <raeburn@MIT.EDU> 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-0006n3-Nq; 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 1FiyZG-0002UR-Aj; Wed, 24 May 2006 14:58:50 -0400
Received: from biscayne-one-station.mit.edu ([18.7.7.80]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiyZF-0008Mb-2d; Wed, 24 May 2006 14:58:50 -0400
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.13.6/8.9.2) with ESMTP id k4OIwl9I002035; Wed, 24 May 2006 14:58:47 -0400 (EDT)
Received: from [18.18.1.160] (NOME-KING.MIT.EDU [18.18.1.160]) (authenticated bits=0) (User authenticated as raeburn@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id k4OIwh1U017583 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Wed, 24 May 2006 14:58:44 -0400 (EDT)
In-Reply-To: <7.0.0.16.2.20060524144104.05718a70@vigilsec.com>
References: <7.0.0.16.2.20060524115045.06eb0a80@vigilsec.com> <tslhd3fjo12.fsf@cz.mit.edu> <7.0.0.16.2.20060524142029.06ef7e40@vigilsec.com> <tslslmzi83i.fsf@cz.mit.edu> <7.0.0.16.2.20060524144104.05718a70@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <564F97AA-E7B7-4291-B4B9-4B6B3BEFFE64@mit.edu>
From: Ken Raeburn <raeburn@MIT.EDU>
Date: Wed, 24 May 2006 14:58:38 -0400
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.750)
X-Spam-Score: 1.217
X-Spam-Level: * (1.217)
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
X-Mailman-Approved-At: Wed, 24 May 2006 15:37:54 -0400
Cc: ipr-wg@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, 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

On May 24, 2006, at 14:42, Russ Housley wrote:
> If the people with copyright interest are the combination of the  
> authors plus the contributors, then we need to specify this in a BCP.

We might also want to suggest that the acknowledgment specifically  
indicate if someone contributed text, as a text-contributor may have  
rights that an idea-contributor does not.  With the default  
assumption being that "contributed", if not clarified, means  
"contributed text and/or ideas".

There's also the related issue of text taken from a previous RFC -- I  
would think it would suffice to acknowledge the source of the text,  
rather than merging contributor/author lists.  (Though if the  
previous author list is small and the copied text is large, specific,  
explicit acknowledgment in the new document is probably the polite  
thing to do.)  But either way, those authors may also retain  
copyright interest in the new document.

> Does the RFC Editor have to contact the members of both lists  
> during Auth48?  If so, I would suggest that the RFf Editor only  
> needs a positive reply from the authors, but that the contributors  
> only need to respond if they discover a change that is needed.

I would think the RFC Editor probably does not need to; after all,  
isn't the short list also (a superset of) the people already acting  
as editors on behalf of the working group, other contributors, etc?   
Those people may choose to include various contributors in the Auth48  
review, or not.

Ken


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