Re: how to contact the IETF

Cullen Jennings <fluffy@cisco.com> Tue, 10 February 2009 18:06 UTC

Return-Path: <fluffy@cisco.com>
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 092883A6B52 for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 10:06:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level:
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 6HJOLEcXxxrg for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 10:06:50 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 2FFE63A6852 for <ietf@ietf.org>; Tue, 10 Feb 2009 10:06:50 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,187,1233532800"; d="scan'208";a="246740895"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 10 Feb 2009 18:06:53 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n1AI6rJS017437 for <ietf@ietf.org>; Tue, 10 Feb 2009 10:06:53 -0800
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1AI6p3h016182 for <ietf@ietf.org>; Tue, 10 Feb 2009 18:06:52 GMT
Message-Id: <1006C42E-B6EC-4C7C-8D03-CFA08F2E06D5@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: IETF discussion list <ietf@ietf.org>
In-Reply-To: <20090210160246.GM13560@shinkuro.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: how to contact the IETF
Date: Tue, 10 Feb 2009 11:06:51 -0700
References: <20090210142744.GJ13560@shinkuro.com> <C5B7054D.2F9A%mshore@cisco.com> <20090210160246.GM13560@shinkuro.com>
X-Mailer: Apple Mail (2.930.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2808; t=1234289213; x=1235153213; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20how=20to=20contact=20the=20IETF |Sender:=20; bh=eLwdmUpCM6CN1ePKnzPTUAt/WwGv6qDWzdWBKZzw5nE=; b=MyIa+EsN/fzYUEz3NRu2fvGsqkvS3gSag62FjnnSuCkgYSi0RJnXWtLYfK 4s7ZdMiRqpGi6zFpKeLE4P4bg9zVC0f8EECyFnbFvC/F6bxCNYCpcI7v5Inz 4MEsVX7FXJ;
Authentication-Results: sj-dkim-4; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
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-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Tue, 10 Feb 2009 18:06:51 -0000

In fairness, the posts resulting from the FSF, uh, call to action, of  
this issue have been polite and tried to make a point. Some of them  
may be more or less informed about the facts at hand but they have  
been on topic and do express an opinion. I'm sure we can all think of  
examples of far less useful conversations that have happened on ietf@ietf.org 
.

The IETF has standardized some of the protocols that became the  
relevant and widely used protocols. I believe one of the things that  
keeps the IETF's work relevant is that it is not just "profession  
standards people" but also actually involves people that write code  
and build products. If some programmer who is not deeply involvement  
with standards or the IETF is implementing something and wants to come  
and make some one time "drive by" comment to the IETF, well, theses  
can be valuable insight. These might be in a slightly different  
category but I think we should pay attention to people that are  
implementing or using a protocol even if they aren't long term IETF  
people. At the other end of the spectrum, we have had case on an IETF  
list where a single person with multiple "sock puppet" email accounts  
was trying to assert undue influence and we had many cases where  
people that knew nothing about the topic just said "me too". It is  
impossible to come up with any algorithm that separates these - it  
requires good judgment of the chairs and others that need to call  
consensus. I don't envy the poor AD that gets to sort out the  
relevancy of these comments.

Cullen <in my individual contributor role>

PS. I have been sort of surprised that no one has asked all these  
people if they plan to implement or use this draft. I was under the  
impression that the community of interest in the draft was very small.  
If there is more widespread interest, it generally helps up the  
chances of the IESG approving a draft.


On Feb 10, 2009, at 9:02 AM, Andrew Sullivan wrote:

> On Tue, Feb 10, 2009 at 10:19:57AM -0500, Melinda Shore wrote:
>
>> Well, no, I don't agree with that last bit, in the
>> sense that I don't think "replied on the mailing list"
>> really means the same thing as "participated."
>
> I think we're in agreement.  All I'm suggesting is that there's no _a
> priori_ way of knowing whether someone is participating, except by
> looking at the lists.  Therefore, we can't dismiss postings from
> people we don't know on the grounds we don't know them.  This means
> that those "driving by" have to be tolerated, I think.
>
> A
>
> -- 
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf