RE: delegating (portions of) ietf list disciplinary process

"Nick Staff" <nick.staff@comcast.net> Thu, 29 September 2005 08:16 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKtae-0003YO-S5; Thu, 29 Sep 2005 04:16:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKtad-0003Ug-Gb for ietf@megatron.ietf.org; Thu, 29 Sep 2005 04:16:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25869 for <ietf@ietf.org>; Thu, 29 Sep 2005 04:16:25 -0400 (EDT)
Message-Id: <200509290816.EAA25869@ietf.org>
Received: from sccrmhc11.comcast.net ([63.240.76.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKtiF-0002Pl-6o for ietf@ietf.org; Thu, 29 Sep 2005 04:24:20 -0400
Received: from archangel (c-24-130-10-179.hsd1.ca.comcast.net[24.130.10.179]) by comcast.net (sccrmhc11) with SMTP id <2005092908161601100lnrine>; Thu, 29 Sep 2005 08:16:17 +0000
From: Nick Staff <nick.staff@comcast.net>
To: dcrocker@bbiw.net, 'Scott W Brim' <sbrim@cisco.com>, ietf@ietf.org
Date: Thu, 29 Sep 2005 01:16:15 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <433B8F02.6090602@dcrocker.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Thread-Index: AcXEwpfVSS0uxgrqTa24YzVZqJzCdwACeqRA
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc:
Subject: RE: delegating (portions of) ietf list disciplinary process
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: nick.staff@comcast.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On 
> 
> >> 2. An IETF "netiquette" committee, to offload list banning 
> procedures 
> >> from the IESG.
> > 
> > I don't think so.  I prefer that this responsibility stay 
> with a few 
> > individuals, so that it is taken very seriously -- not only by them 
> > but by everyone.  A committee would lead to dilution of 
> responsibility 
> > as well as endless discussion on every dispute.
> 
> Good point.
> 
> As much as I believe the IETF should not give veto authority 
> to any single individual, this is one case where it is 
> probably better.
> 
> My sense is that, without exception, IETF participants 
> involved in deciding process objections has taken their role 
> extremely seriously.  It's difficult to believe that this 
> would be any different.  In addition, any abuse by the 
> ombudsperson will be very quickly reported and corrected.
> 
> d/
> -- 
> 
>   Dave Crocker
Dave-

Of course it's a matter of opinion, so it's not like I'm trying to tell you
I'm right and you're wrong, but think about every high court in the United
states and many in Europe - none of them are 1 person but rather a group.
There are reasons for this, most important of which is no one is right all
the time - no one no matter how wisened sees every situation clearly from
all angles - not to  mention most everyone has their hot issues and areas of
predjudice or misunderstanding.  Having a group of seven or nine helps
neutralize individual errors.  I'd feel much safer being judged by tcp than
udp.

nick


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