IETF Logo Mail Archive

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

Dave CROCKER <dhc2@dcrocker.net> Sat, 10 January 2009 20:52 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 3F22728C13D; Sat, 10 Jan 2009 12:52:34 -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 9DF2F3A69F3 for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 12:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.818
X-Spam-Level:
X-Spam-Status: No, score=-1.818 tagged_above=-999 required=5 tests=[AWL=-0.458, BAYES_00=-2.599, SARE_LWSHORTT=1.24]
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 2PRVppV5KebY for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 12:52:31 -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 2834B3A6768 for <ietf@ietf.org>; Sat, 10 Jan 2009 12:52:30 -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 n0AKq7h5026482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Jan 2009 12:52:12 -0800
Message-ID: <49690A77.70705@dcrocker.net>
Date: Sat, 10 Jan 2009 12:52:07 -0800
From: Dave CROCKER <dhc2@dcrocker.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>
In-Reply-To: <496905AF.7090209@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 12:52:13 -0800 (PST)
Cc: John C Klensin <john-ietf@jck.com>, Simon Josefsson <simon@josefsson.org>, Theodore Tso <tytso@mit.edu>, 'IETF Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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:
> Which is why I suggest that we should support the Trustees' proposed
> short term fix, to allow normal work to continue +/- cutting and pasting
> some boilerplate. We do have a glitch in 5378 to mend, but let's get that
> off the critical path.


I can't begin to guess at the logic that uses Larry's somewhat bizarre assertion 
as a basis for trying to press approval of this clearly and substantially 
problematic proposal.

To create a paraphrase, what part of "neither short term nor a fix" did you not 
understand?

The concept of "short term" never applies to infrastructure changes, and as Fred 
pointed out -- ableit again my paraphrase -- we are messing with something deep 
in the IETF's processing infrastructure.

Equally, taking something that already imposes unnecessarily broad impact, and 
layering onto it a hack that imposes even more impact, is not a fix.


d/
-- 

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

v2.23.0 | Report a Bug | By Email