RE: RFC Editor Function SOW Review
John C Klensin <john-ietf@jck.com> Mon, 24 July 2006 17:44 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G54TW-0002Ld-To; Mon, 24 Jul 2006 13:44:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G54TU-0002LC-Kv; Mon, 24 Jul 2006 13:44:12 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G54TS-0007oC-5h; Mon, 24 Jul 2006 13:44:12 -0400
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1G54TO-0004Z0-9E; Mon, 24 Jul 2006 13:44:06 -0400
Date: Mon, 24 Jul 2006 13:44:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>, Dave Crocker <dhc2@dcrocker.net>, Joe Touch <touch@ISI.EDU>
Message-ID: <7FB598F0C4886C58F45FFBC8@p3.JCK.COM>
In-Reply-To: <474EEBD229DF754FB83D256004D02108025849DA@XCH-NW-6V1.nw.nos.boeing.com>
References: <474EEBD229DF754FB83D256004D02108025849DA@XCH-NW-6V1. nw.nos.boeing.com>
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
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
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. That work is arguably best done by professionals because it requires considerable skill; skill that improves with experience. 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. It seems to me, based on both thought experiments and experience with other standards bodies, that would lead to side effects we just do not want. john --On Monday, 24 July, 2006 09:07 -0700 "Fleischman, Eric" <eric.fleischman@boeing.com> wrote: > I spent the first many years of my professional life overseas > working as a Linguist writing and speaking other people's > languages. Even though my own proficiency was inadequate by > their standards, I relied upon talented native speakers to > enhance my publications so that they became well written in > the target language. This is what the IETF also needs to do. > > The IETF authors needn't be very proficient in English, but > they need to be proficient enough to coherently explain their > technical points so that others can understand them. What is > needed is to ensure that somebody, with the authors' > oversight, is enlisted to improve the drafts so that the > ultimate IETF documents themselves are in very good English. > > Because the IETF is now International, all the IETF documents > must be in well-written English because we now come from so > many languages and cultures. It is hard enough dealing in > foreign languages without exacerbating the problem for the > non-native English speaker by asking them to understand > garbled versions of English. If it is difficult for the native > English speaker to understand, it is much worse for the > non-Native speakers (unless they happen to speak the same > language as the garbler). > > BTW, some native English speakers also produce horrid > documents because they are poor writers. These individuals > also need to leverage editors who can translate their thoughts > into coherent English. > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ 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