Re: [apps-discuss] We have no lambs
Pete Resnick <presnick@qualcomm.com> Thu, 12 May 2011 21:23 UTC
Return-Path: <presnick@qualcomm.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F38FE067C for <apps-discuss@ietfa.amsl.com>; Thu, 12 May 2011 14:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level:
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9qdHVuTJ384 for <apps-discuss@ietfa.amsl.com>; Thu, 12 May 2011 14:23:39 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 315ADE066E for <apps-discuss@ietf.org>; Thu, 12 May 2011 14:23:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1305235419; x=1336771419; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: x-originating-ip; z=Message-ID:=20<4DCC4FD6.4040205@qualcomm.com>|Date:=20Th u,=2012=20May=202011=2016:23:34=20-0500|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Barry=20Leiba=20<barryleiba@co mputer.org>|CC:=20Apps=20Discuss=20<apps-discuss@ietf.org >|Subject:=20Re:=20[apps-discuss]=20We=20have=20no=20lamb s|References:=20<4DCAC1CB.3050905@qualcomm.com>=09<6.2.5. 6.2.20110511115259.051cd3f8@resistor.net>=09<4DCAF61F.100 00@qualcomm.com>=09<6.2.5.6.2.20110511141027.032dd408@res istor.net>=20<BANLkTimsunzpH1afh8WY54nSk6z2Hw2siA@mail.gm ail.com>|In-Reply-To:=20<BANLkTimsunzpH1afh8WY54nSk6z2Hw2 siA@mail.gmail.com>|Content-Type:=20multipart/alternative =3B=0D=0A=09boundary=3D"------------000204050901040005070 906"|X-Originating-IP:=20[172.30.39.5]; bh=cE72E98K1xX2Vw+9GBclp2K5S+c3mXiqZhy2S3CO5x0=; b=Dw9s8SS5IqLo55VmX7LQN24KpWXTkj11y293JOHYbtMHldCn8vsP2YGi IvOonVggXIlqBwOgn5L8Vbrw9OUwUZ+KotW5omfn9wm67bkBFx/rmKUEe zRhoFnFeUWwoNyRs4ciBFPYFDKqediP64wJgfOTu/Mz3bD58zr1ryx4xP c=;
X-IronPort-AV: E=McAfee;i="5400,1158,6344"; a="90894208"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine02.qualcomm.com with ESMTP; 12 May 2011 14:23:38 -0700
X-IronPort-AV: E=Sophos; i="4.64,358,1301900400"; d="scan'208,217"; a="41620599"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 12 May 2011 14:23:38 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 12 May 2011 14:23:36 -0700
Message-ID: <4DCC4FD6.4040205@qualcomm.com>
Date: Thu, 12 May 2011 16:23:34 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
References: <4DCAC1CB.3050905@qualcomm.com> <6.2.5.6.2.20110511115259.051cd3f8@resistor.net> <4DCAF61F.10000@qualcomm.com> <6.2.5.6.2.20110511141027.032dd408@resistor.net> <BANLkTimsunzpH1afh8WY54nSk6z2Hw2siA@mail.gmail.com>
In-Reply-To: <BANLkTimsunzpH1afh8WY54nSk6z2Hw2siA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000204050901040005070906"
X-Originating-IP: [172.30.39.5]
Cc: Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] We have no lambs
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2011 21:23:41 -0000
Let me say up front that I think this entire conversation is great, and I think we are all getting a great deal out of having it. I know I am. And I do agree with Barry on some of the more specific points, but I suspect that we will end up simply agreeing to disagree on the broader issue. And I do think it is worth having this conversation, because I hope it will lead to some understanding of not just my style, but my motives. On 5/11/11 5:43 PM, Barry Leiba wrote: > Hm. I thought I wouldn't comment on this, but I think I will, because > I want to make something clear about how I think about this. > > On Wed, May 11, 2011 at 5:39 PM, SM<sm@resistor.net> wrote: > >> At 13:37 11-05-2011, John C Klensin wrote: >> >>> So, I wouldn't have said "useless". I might have said "of very >>> limited value in helping the IESG with its determination of >>> consensus about technical quality and adequacy of review". >>> >> That is the politically correct way of stating it. It may help some people >> understand what the IESG would like. However, sentences like that are >> against IETF best practices. :-) >> >> Pete has taken a rather unusual approach. I would qualify it as open. It >> is to encourage discussion on an equal footing. >> > Here's why I think being "politically correct" is important: > If it's someone's manner to be blunt, and to expect that we won't take > him *too* much at his exact words, that's fine, and we learn that. > And if someone is wont to say "Eff all y'all. I'm going to ignore any > comments I choose to," well, again, we consider who's saying it and to > what extent we think he really means that... and everyone has a right > not to pay attention to anyone in particular. Except.... > First, I don't think you'll find anywhere in my original note on the "support publication" thread that I said I would absolutely ignore or be closed to the input. I did say that I "find these statements...well...useless." I did say that such commentary on the publication itself is "really, truly, not important." And I did joke (smiley face included) that I would have to assume that the reason for such a statement is "because you have a wager on how soon we will get to RFC 10000. :-)" But I never did say I'd ignore them. I did say later (in reference to Ted's comments) that I "*might* ignore comments that come without context because there really is no way to evaluate what they mean", but that's just to say that if I can't figure out the meaning of a statement, it's simply not going to impact my thinking on a particular topic. But all of this is somewhat less important than what follows: > When someone accepts a position on the IESG, the IAB, or the IAOC -- > I*, as we collectively call them -- s/he no longer gets to be the > gruff "eff all y'all" person s/he once may have been. S/he has to > support the open system we have, and not be closed to input. That's > why someone on I* saying "I won't listen unless you say it the way I > want to hear it," bothers me. That's why I think it's important to > put it more the way John did -- so people understand that you're not > just brushing people off, but see what you need and why. > As I said above, I don't think that anything I said means that "I won't listen". However, let's talk for a moment about style: There is a circumstance in which I think one really does have to take care to act and sound as open to all input and impartial as possible: when you are in a position of power in a truly hierarchical organization. In that case, the fact that you have power over other people requires that you not only have be open, but you have to act more open than you normally would. A position of power means that the less powerful folks will be reluctant to confront you, so you have to be exceedingly careful to listen for quieter voices and coax people into expressing their views frankly and honestly. And my real concern here is the inverse effect of the above: When someone starts acting measured in their statements and Solomon-like in their judgments and pronouncements, it creates an air of authority. It puts people in mind that you are, by virtue of your position, in power. Call me naïve, but the IETF is not supposed to be a hierarchical organization like that (behavior of some folks and some adopted procedures notwithstanding). We're supposed to be a consensus organization, where we all listen to well-reasoned technical arguments, even if they come from someone new; where the mere fact of having grey hairs (on the face, head, legs, or otherwise shaved off of any of those) does not entitle you to say, "It must be this way and I don't have to explain why"; where the people in "leadership" are just other passengers on the bus, not kings, to whom one can say, "You're wrong, and here's why, and that makes you, Mr./Ms. Leader, in the 'rough' part of the rough consensus"; and where the participants in the IETF are the ones who take responsibility for the documents being of good quality, not the leadership. Some of that is happening now. Some is definitely not. Not being hierarchical and having everyone be responsible makes lots of folks (leadership and regular participants alike) very uncomfortable. Being in a hierarchy means that there is normally someone above you who can direct you to the right path if you need, or take the heat when you make a mistake. Being in leadership in a hierarchy means you can make a decision and not be pushed back on by people under you. These are all very comforting thoughts and not having that backstop is worrisome. And many of us now come out of corporate culture (as against academia), where hierarchy is what we know. But I'm doing my best to push back on that. So, when I say that "I support the publication of this document" is useless, what I'm saying is: Sure, you can choose to assume that I, or other ADs, or the rest of participants, "know who you are" and therefore must take such contextless statements seriously. But really, I don't think you should say things that way. I think you should state the technical (or other) grounds that you think this document is useful or important or implementable (or not). Or you might choose to assume that such statements count as a vote for the document. But really, this is a consensus organization, and you don't get to "count" just because you grunted "yes". New folks shouldn't think that "silence followed by voting" is a reasonable modus operandi, and you shouldn't act that way either. You might count, if I happen to have enough context, but if another AD or another participant comes up to me and says, "Who is this bozo? I don't believe he ever even read the document", it would be rather nice to be able to point back to something more concrete than "+1". Yes, I definitely want people to feel that I am open to their input. (I want people to feel that everyone is open to their input.) On the flip side, I also want people to feel responsibility for the output of the IETF. And I don't want people thinking that I am some oracle from on high that has any particular power over them. I take my role to be (a) judging the consensus of the community and (b) inputting my experience and expertise when I can, and I take them in that order. So it comes down to my style to get that ethos instilled. I'm inclined to say to people (new and old alike), "You'd better explain your reasoning or you're not going to get heard". Now, I take your point that such talk might put off some people. And that means that I also have a responsibility to mentor new folks (or even not-so-new folks who are disinclined to challenge authority) to understand that nobody gets to rely on their station to justify their statements, and that anyone can push back on anyone else, myself included. But I am taking a risk that people will think I'm not going to listen to them. However, I prefer that risk to the one where I act "exalted" and speak in such ways and end up where people think I'm "in charge". I am not (as a friend of all of ours said to me recently) "the Last Defender of Camelot". I'm not going to talk like that, and I don't want you to talk to me like that. You may all feel free to decide that I'm completely full of it. That's what this organization is supposed to allow. In fact, if 20 of you think that I am sufficiently full of it at any point, we have a procedure to deal with that. But I do hope that I am setting up the world in such a way that anybody feels they can yell at me first and convince me that I am "in the rough." > So I don't really look at it as being "politically correct", but as > being clear without being exclusive. > As do I. pr -- Pete Resnick<http://www.qualcomm.com/~presnick/> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
- [apps-discuss] Applicability Statements Pete Resnick
- Re: [apps-discuss] Applicability Statements John C Klensin
- Re: [apps-discuss] Applicability Statements Barry Leiba
- Re: [apps-discuss] Applicability Statements SM
- Re: [apps-discuss] Applicability Statements Brian E Carpenter
- Re: [apps-discuss] Applicability Statements Peter Saint-Andre
- Re: [apps-discuss] Applicability Statements Pete Resnick
- [apps-discuss] We have no lambs (was: Applicabili… SM
- Re: [apps-discuss] We have no lambs (was: Applica… Barry Leiba
- Re: [apps-discuss] We have no lambs Stephen Farrell
- Re: [apps-discuss] Applicability Statements Martin J. Dürst
- [apps-discuss] On "supporting the publication of … John C Klensin
- Re: [apps-discuss] Applicability Statements Hannes Tschofenig
- Re: [apps-discuss] Applicability Statements John C Klensin
- Re: [apps-discuss] Applicability Statements Dave CROCKER
- Re: [apps-discuss] Applicability Statements Nico Williams
- Re: [apps-discuss] On "supporting the publication… SM
- Re: [apps-discuss] Applicability Statements Pete Resnick
- Re: [apps-discuss] Applicability Statements Nico Williams
- Re: [apps-discuss] Applicability Statements Pete Resnick
- Re: [apps-discuss] Applicability Statements Nico Williams
- Re: [apps-discuss] Applicability Statements Dave Crocker
- Re: [apps-discuss] Applicability Statements Nico Williams
- Re: [apps-discuss] Applicability Statements Dave Crocker
- Re: [apps-discuss] Applicability Statements Nico Williams
- Re: [apps-discuss] Applicability Statements John C Klensin
- Re: [apps-discuss] Applicability Statements Pete Resnick
- Re: [apps-discuss] We have no lambs Pete Resnick
- Re: [apps-discuss] We have no lambs Peter Saint-Andre
- Re: [apps-discuss] We have no lambs Barry Leiba
- Re: [apps-discuss] Applicability Statements John Levine
- Re: [apps-discuss] Applicability Statements t.petch
- Re: [apps-discuss] Applicability Statements Scott Brim
- Re: [apps-discuss] Applicability Statements Pete Resnick
- Re: [apps-discuss] Applicability Statements Pete Resnick