RE: Blue Sheet Change Proposal

"Richard Shockey" <richard@shockey.us> Mon, 07 April 2008 15:09 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 core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A87C23A69F7; Mon, 7 Apr 2008 08:09:47 -0700 (PDT)
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 D426A3A68FF; Mon, 7 Apr 2008 08:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.566
X-Spam-Level:
X-Spam-Status: No, score=-3.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 CkLkTtuLQbVk; Mon, 7 Apr 2008 08:09:42 -0700 (PDT)
Received: from mail.songbird.com (mail.songbird.com [208.184.79.10]) by core3.amsl.com (Postfix) with ESMTP id 1D11928C2C9; Mon, 7 Apr 2008 08:09:42 -0700 (PDT)
Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id m37F8Wlp009141 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Apr 2008 08:08:33 -0700
From: "Richard Shockey" <richard@shockey.us>
To: "'John C Klensin'" <john-ietf@jck.com>
References: <8282D6B77F4B287BF995B8F7@p3.JCK.COM>
In-Reply-To: <8282D6B77F4B287BF995B8F7@p3.JCK.COM>
Subject: RE: Blue Sheet Change Proposal
Date: Mon, 7 Apr 2008 11:08:48 -0400
Message-ID: <0d9101c898c1$4a8e9ef0$dfabdcd0$@us>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AciX4nRSOx4ihqvPRO+kmwGnchrP7AA3mbMg
Content-Language: en-us
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: richard@shockey.us
Cc: 'Working Group Chairs' <wgchairs@ietf.org>, '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

Exactly .. I don't see the problem. I've not seen any evidence of abuse.
IMHO if the procedure is not broken why are we trying to fix it?

Why is the IETF so continuingly dragged about in these, frankly trivial,
process issues? 

>  I won't repeat what others have said about the presence or
>  absence of the problem, but I'm not convinced either.
>  
>      john

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