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

Martin Duerst <duerst@it.aoyama.ac.jp> Tue, 13 January 2009 02:03 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 ABD8E3A69D2; Mon, 12 Jan 2009 18:03:41 -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 766AF3A69C5 for <ietf@core3.amsl.com>; Mon, 12 Jan 2009 18:03:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.585
X-Spam-Level:
X-Spam-Status: No, score=0.585 tagged_above=-999 required=5 tests=[AWL=-0.917, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_23=0.6]
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 Cs2PNm+0dROs for <ietf@core3.amsl.com>; Mon, 12 Jan 2009 18:03:39 -0800 (PST)
Received: from scmailgw2.scop.aoyama.ac.jp (scmailgw2.scop.aoyama.ac.jp [133.2.251.195]) by core3.amsl.com (Postfix) with ESMTP id 594423A68F0 for <ietf@ietf.org>; Mon, 12 Jan 2009 18:03:38 -0800 (PST)
Received: from scmse3.scbb.aoyama.ac.jp ([133.2.253.23]) by scmailgw2.scop.aoyama.ac.jp (secret/secret) with SMTP id n0D23Mj7010522 for <ietf@ietf.org>; Tue, 13 Jan 2009 11:03:22 +0900 (JST)
Received: from (unknown [133.2.206.133]) by scmse3.scbb.aoyama.ac.jp with smtp id 4f71_5b1ce01c_e116_11dd_9a86_001d0969ab06; Tue, 13 Jan 2009 11:03:22 +0900
Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:34161) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S86A888> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 13 Jan 2009 10:55:16 +0900
Message-Id: <6.0.0.20.2.20090112162714.08bc2cc8@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Mon, 12 Jan 2009 16:30:12 +0900
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, John C Klensin <john-ietf@jck.com>
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewandcomments on a proposed Work-Around to the Pre-5378 Problem
In-Reply-To: <4967CAA1.9020608@gmail.com>
References: <70873A2B7F744826B0507D4B84903E60@noisy> <FB8A848E-E415-4CDE-9E3F-5C74A561 4F18@cisco.com> <49678B2A.8000100@dcrocker.net> <20090109181503.GP24908@verdi> <6E372F257B0C42E7AB9B7DA6231FF4E4@LROSENTOSHIBA> <p06240800c58d5466241b@[10.227.48.131]> <DBAA71AA401E5398212B1E03@PST.jck.com> <4967CAA1.9020608@gmail.com>
Mime-Version: 1.0
Cc: Ted Hardie <hardie@qualcomm.com>, 'IETF Discussion' <ietf@ietf.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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Re. pre-5378 vs. post-5378 material, please note that in many
cases, an RFC may be post-5378, but the Internet-Drafts having
lead up to it may be pre-5378, or the lastest available Internet-
Draft may be post-5378, but earlier ones may be pre-5378.
In other words, just looking at things at the RFC level is not
enough. That may be obvious to many, just wanted to make sure
it doesn't get forgotten.

Regards,    Martin.


At 07:07 09/01/10, Brian E Carpenter wrote:
>John,
>
>On 2009-01-10 10:32, John C Klensin wrote:
>...
>> And note that makes a clear and plausible transition model:
>> 
>>      (1) Pre-5378 documents exist under pre-5378 rules, so
>>      any potential user for non-traditional purposes needs to
>>      either figure out who the relevant authors are and get
>>      their permission or decide the risk isn't worth worrying
>>      about.  If some of those authors/ contributors make
>>      explicit transfers to the Trust, that is great, but none
>>      of them have to take responsibility for identifying all
>>      of the others.
>>      
>>      (3) Post-5378 new documents are posted according to 5378
>>      rules, with no exceptions.
>>      
>>      (2) Post-5378 documents that incorporate pre-5378
>>      materials must used 5378 rules for any material that is
>>      new.  For the earlier materials, and for sorting out
>>      which is which, the burden falls on the potential user
>>      for non-traditional purposes to either figure out who
>>      the relevant authors are and get their permission,
>>      determine that all relevant authors have already given
>>      permission, or assume the risks.   No one else --neither
>>      the author(s)/ editor(s) of the new document nor the
>>      Trust-- is required to take responsibility for pre-5378
>>      contributors or contributions.  Even an editor of the
>>      new document that worked on the old material is not
>>      required to make assertions about new rights on behalf
>>      of his or her former employer.
>
>Thanks John, I believe that is an excellent summary of the
>viable options. My draft implicitly adds
>
>  (2.5) Post-5378 documents that incorporate pre-5378
>  materials whose original contributors have duly agreed are
>  posted according to 5378 rules, with no exceptions.
>
>To my mind the main open issue is whether we want to
>require authors to try for (2.5) before proceeding to (2).
>
>    Brian
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp     

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