RE: RFC Editor Function SOW Review
"Fleischman, Eric" <eric.fleischman@boeing.com> Mon, 24 July 2006 16:20 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G53AD-0004rb-Dc; Mon, 24 Jul 2006 12:20:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G53AB-0004qh-8k; Mon, 24 Jul 2006 12:20:11 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G53AB-0005jF-2N; Mon, 24 Jul 2006 12:20:11 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56] helo=stl-smtpout-01.ns.cs.boeing.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G52zk-0002rx-A9; Mon, 24 Jul 2006 12:09:26 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id k6OG9E4a018305; Mon, 24 Jul 2006 11:09:14 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id k6OG9D312815; Mon, 24 Jul 2006 11:09:14 -0500 (CDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.55]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Jul 2006 09:08:32 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 24 Jul 2006 09:07:42 -0700
Message-ID: <474EEBD229DF754FB83D256004D02108025849DA@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <100683ABC471EA88FEE8E373@p3.JCK.COM>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RFC Editor Function SOW Review
Thread-Index: AcatQfvMUfTYvaQ3Qk2PFUGTcKUKtQB9qe5A
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: John C Klensin <john-ietf@jck.com>, Dave Crocker <dhc2@dcrocker.net>, Joe Touch <touch@ISI.EDU>
X-OriginalArrivalTime: 24 Jul 2006 16:08:32.0584 (UTC) FILETIME=[68FADC80:01C6AF3B]
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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
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
- 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