Re: RFC Editor Function SOW Review
Dave Crocker <dhc2@dcrocker.net> Mon, 24 July 2006 18:04 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G54mr-00038Q-FK; Mon, 24 Jul 2006 14:04:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G54mp-00038H-KO; Mon, 24 Jul 2006 14:04:11 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G54mo-0001yX-8T; Mon, 24 Jul 2006 14:04:11 -0400
Received: from [192.168.0.2] (ppp-68-122-73-43.dsl.pltn13.pacbell.net [68.122.73.43]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k6OI4GiR007323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jul 2006 11:04:17 -0700
Message-ID: <44C50B81.8070409@dcrocker.net>
Date: Mon, 24 Jul 2006 11:03:45 -0700
From: Dave Crocker <dhc2@dcrocker.net>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <474EEBD229DF754FB83D256004D02108025849DA@XCH-NW-6V1. nw.nos.boeing.com> <7FB598F0C4886C58F45FFBC8@p3.JCK.COM>
In-Reply-To: <7FB598F0C4886C58F45FFBC8@p3.JCK.COM>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: dhc2@dcrocker.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: IETF Administrative Director <iad@ietf.org>, IETF Announcement list <ietf@ietf.org>
Subject: Re: RFC Editor Function SOW Review
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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>
Errors-To: ietf-bounces@ietf.org
John C Klensin wrote: > Exactly. > > Where Dave and I disagree, I think, is that I consider getting > from "technically correct and coherent but not in English that > is acceptable to non-native speakers who primary language also > differs from that of the author/editor" to be a community > responsibility, while Dave considers it a WG (or other advocacy > group) one... At least I hope I have that right. Sounds correct to me. > That work is arguably best done by professionals because it > requires considerable skill; skill that improves with experience. It certainly requires skill. However it does not require some sort of formal certification and job title. The skill is available from many sources. > There are several reasons I want to see it handled as a > community responsibility rather than as a WG one, but the most > important is that, if people have to be hired to do the work, I > don't want to see our working groups turn into mini-consortia > with their own budgets, funding sources, hired editors, etc. You are vastly too late for that, from a practical standpoint. The reality is that virtually all IETF efforts that succeed, these days, come from some sort of organized industry effort. Whether that organization is formal is irrelevant. In any event, "industry" is already spending quite a bit to get the technical work done, for any given specification. In that context, the incremental cost of the editing work is negligibility -- within the context of that single effort. Meta-point: The resistance to pushing meaningful responsibility to the groups supposed to do the work -- and enforcing that they do it well -- continues to strike me as quite dissonant with the community's claimed goals, both long-standing and recent. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: RFC Editor Function SOW Review Pete Resnick
- Re: RFC Editor Function SOW Review Dave Crocker
- Re: RFC Editor Function SOW Review Brian E Carpenter
- Re: RFC Editor Function SOW Review Todd Glassey
- Re: RFC Editor Function SOW Review Marcus Leech
- Re: RFC Editor Function SOW Review Joe Touch
- Re: RFC Editor Function SOW Review Joe Touch
- Re: RFC Editor Function SOW Review Dave Crocker
- Re: RFC Editor Function SOW Review Dave Crocker
- Re: RFC Editor Function SOW Review Ned Freed
- Re: RFC Editor Function SOW Review Joel M. Halpern
- Re: RFC Editor Function SOW Review todd glassey
- RE: RFC Editor Function SOW Review Fleischman, Eric
- RE: RFC Editor Function SOW Review John C Klensin
- Re: RFC Editor Function SOW Review Dave Crocker