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

Dave CROCKER <dcrocker@bbiw.net> Sat, 10 January 2009 21:55 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 A0DEF28C1BF; Sat, 10 Jan 2009 13:55:38 -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 706EA3A6A84 for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 13:55:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 R30hFCNeb18q for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 13:55:36 -0800 (PST)
Received: from sbh17.songbird.com (mail.mipassoc.org [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id B7EBF3A6A5C for <ietf@ietf.org>; Sat, 10 Jan 2009 13:55:35 -0800 (PST)
Received: from [192.168.0.4] (adsl-68-122-40-145.dsl.pltn13.pacbell.net [68.122.40.145]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n0ALtDfl028380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Jan 2009 13:55:19 -0800
Message-ID: <49691941.70109@bbiw.net>
Date: Sat, 10 Jan 2009 13:55:13 -0800
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem
References: <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> <4967CAA1.9020608@gmail.com> <B2385D8E5F5BA599A174BD43@PST.jck.com> <4967E348.7050300@joelhalpern.com> <87d4evgu35.fsf@mocca.josefsson.org> <20090110191055.GB31579@mit.edu> <7D0E9557A84E06BFB4E120CA@PST.jck.com> <496905AF.7090209@gmail.com> <49690A77.70705@dcrocker.net> <49691476.6070506@gmail.com>
In-Reply-To: <49691476.6070506@gmail.com>
X-Virus-Scanned: ClamAV 0.92/8849/Fri Jan 9 20:18:40 2009 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 10 Jan 2009 13:55:19 -0800 (PST)
Cc: '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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


Brian E Carpenter wrote:
> Er, is that a Last Call comment on draft-ietf-ipr-outbound-rights
> and draft-ietf-ipr-3978-incoming? A bit late, if so.

Brian, "too late" makes sense for stray comments.

It doesn't make sense when we discover that a spec doesn't work. There have been 
quite a few comments and events that make concretely clear that this 'spec' 
doesn't work, and that the proposed fix introduces significant new problems, 
even assuming that it 'fixes' the primary problem.


>> and layering onto it a hack that imposes even more impact, is
>> not a fix.
> 
> Look, the IPR WG, and all those who reviewed its drafts, including
> me, missed that fact that there was a transition problem that should
> have been covered in those drafts. I'm sorry, I made a mistake, as
> Basil Fawlty once said. We need to fix that mistake.

You keep referring to this as a 'transition' problem as if that minimizes the 
problem.  Even assuming that the label is formally correct, it's clear that 
there is nothing brief about the transition nor minimal about the impact.

Like most infrastructure changes, "transition" is a strategic, long-term concern.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf