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

Marshall Eubanks <tme@multicasttech.com> Fri, 09 January 2009 16:19 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 ABD1328C16D; Fri, 9 Jan 2009 08:19: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 6C8E13A6A30; Fri, 9 Jan 2009 08:19:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.352
X-Spam-Level:
X-Spam-Status: No, score=-103.352 tagged_above=-999 required=5 tests=[AWL=0.247, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 IsllGalwThGw; Fri, 9 Jan 2009 08:19:49 -0800 (PST)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 44D533A68F2; Fri, 9 Jan 2009 08:19:49 -0800 (PST)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 14206574; Fri, 09 Jan 2009 11:19:35 -0500
Message-Id: <4FE8E970-A93A-43B7-85B5-34E2DC613534@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: Thomas Narten <narten@us.ibm.com>
In-Reply-To: <200901091516.n09FGJsI023601@cichlid.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewand comments on a proposed Work-Around to the Pre-5378 Problem
Date: Fri, 09 Jan 2009 11:19:34 -0500
References: <70873A2B7F744826B0507D4B84903E60@noisy> <FB8A848E-E415-4CDE-9E3F-5C74A5614F18@cisco.com> <F857DDBB-CDEE-48A8-B59C-56AEDA65CE79@cs.tcd.ie> <4966CEF3.8080506@gmail.com> <6.0.0.20.2.20090109143653.05e3ebd8@localhost> <200901091516.n09FGJsI023601@cichlid.raleigh.ibm.com>
X-Mailer: Apple Mail (2.930.3)
Cc: Trustees <trustees@ietf.org>, Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, Fred Baker <fred@cisco.com>, RFC Editor <rfc-editor@rfc-editor.org>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Jan 9, 2009, at 10:16 AM, Thomas Narten wrote:

> Martin Duerst <duerst@it.aoyama.ac.jp> writes:
>
>> WHO exactly are we supposed to get permissions from.
>
>> The situation of a deceased author is a tought one, but it's an
>> obvious one. But I haven't seen any clear answer to whether
>> permission from all the authors/editors (the people listed in
>> the front of the document) is sufficient, whether we have to
>> ask everybody above a certain percentage of email contributions
>> in the WG, everybody who's mentioned in the Acks section, or
>> what. It's a significant nuissance for everybody to go around
>> and beg people (maybe including for their former employer)
>> to confirm something they probably couldn't care less, even if
>> they otherwise think the IETF does great stuff and everything.
>> So it would really be good to know who exactly has to be
>> bothered, and who not.
>
> IANAL, but if you are expecting anyone (like the IETF) to give a clear
> final, legally defensible answer to "who do you need permission from",
> you won't get it. That is the nature of legal questions and is what
> makes this entire discussion so difficult. And why what is an
> accptable risk for you may not be an acceptable risk for me or someone
> else.

My personal feeling is that is it is reasonable to ask authors to give  
their
permission, and to obtain their company's permission, if need be, but  
that
it is not reasonable to ask _authors_ to obtain permissions from third  
parties.

Regards
Marshall



>
>
> To answer the question, you have to look at who bears the risk if they
> make an assertion (i.e, by claiming that all contributers have signed
> off) that someone later challenges. And what the potential
> consequences would be.
>
> How likely is such a challenge? (the answer is almost always "it
> depends").
>
> What is the likelyhood of a challenge having merit? (answer is "it
> depends").
>
> What is the cost (time/money/aggrevation) of having to deal with such
> a situation? ("it depends" -- see the pattern?)
>
> While you (personally) may think the risk is negligble and silly, does
> your employer (who also probably bears some risk) share your opinion
> ("it depends").
>
> Etc.
>
> And, it is all made that much worse by having to go through the same
> excercise for each document. Having done the analysis on 10 documents,
> doesn't help you much when it comes to the next document.
>
> Thomas
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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