Re: [tao-discuss] First draft of new version

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 01 June 2018 12:18 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: tao-discuss@ietfa.amsl.com
Delivered-To: tao-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D85A412D7EF for <tao-discuss@ietfa.amsl.com>; Fri, 1 Jun 2018 05:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sh5l3Gz5RFRb for <tao-discuss@ietfa.amsl.com>; Fri, 1 Jun 2018 05:18:33 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EDB412D7F1 for <tao-discuss@ietf.org>; Fri, 1 Jun 2018 05:18:32 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id w51CHr7M026555; Fri, 1 Jun 2018 13:18:31 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E38AD2204E; Fri, 1 Jun 2018 13:18:30 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs3.iomartmail.com (Postfix) with ESMTPS id D29932204A; Fri, 1 Jun 2018 13:18:30 +0100 (BST)
Received: from 950129200 (243.125.113.87.dyn.plus.net [87.113.125.243]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id w51CISAD008730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Jun 2018 13:18:29 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Niels ten Oever' <mail@nielstenoever.net>
Cc: tao-discuss@ietf.org, rfc-ise@rfc-editor.org
References: <ba4790a6-e950-1a6b-0178-b834bbee8c82@nielstenoever.net> <015201d3f908$e7354940$b59fdbc0$@olddog.co.uk> <785b9d4f-f1a6-4132-4810-f0d9d2c2fc71@nielstenoever.net>
In-Reply-To: <785b9d4f-f1a6-4132-4810-f0d9d2c2fc71@nielstenoever.net>
Date: Fri, 01 Jun 2018 13:18:28 +0100
Message-ID: <00c901d3f9a2$a71fbe90$f55f3bb0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG/fOjLliYXaJGIaYlr9LJXcEsaaAHsKLJKAikZOcmkU6Cz0A==
Content-Language: en-gb
X-Originating-IP: 87.113.125.243
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-23880.006
X-TM-AS-Result: No--13.492-10.0-31-10
X-imss-scan-details: No--13.492-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-23880.006
X-TMASE-Result: 10--13.492300-10.000000
X-TMASE-MatchedRID: oTBA/+sdKaaqMZyz/RcGLuYAh37ZsBDCLi2dwKiMR9zCPXSO232P77mn rGB/kwGM+kHqi4GBLEmdVua74H3f/XS0x46LMJIagV26YsWy3m2B0mqjupFs5WM+uU0H6AyrZ1H cplu19kgYzGQlCtBP/ugAXWK39NLrt8o90+0aU3IwiJTf3kjwfQeCHewokHM/QPQHfu9DbpPPe7 3EBVQLDr9Qtf141M5/gXRcHp+cCG61DfGM6db7X2Oho7buv7d9fS0Ip2eEHnzUHQeTVDUrItRnE QCUU+jzjoczmuoPCq1VWsrR72UnFfLsBeQWIwrts6sSTm7kyqarkCAggdtrviJVB3YUAqwP
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/azdJOe8UfhCIYnfBvNbsi3B92q4>
Subject: Re: [tao-discuss] First draft of new version
X-BeenThere: tao-discuss@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of the Tao of the IETF <tao-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tao-discuss/>
List-Post: <mailto:tao-discuss@ietf.org>
List-Help: <mailto:tao-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2018 12:18:37 -0000

Many thanks.

Responses to your responses...

> > 2.2.5
> > s/the RFC Editor and IANA involved/the RFC Editor and IANA are involved/
> >
> 
> This is the full sentence:
> 
> Although both the RFC Editor and IANA involved the same people for many
> years, the RFC Editor is a separate job. Today,
> 
> Your suggestion would make it grammatically incorrect, right? (But am a
> bit hesitant to say this as a non-native english speaker to a native
> one, so happy to learn :) ).

Sorry, my bad!

Original text stands.

> > 2.2.5
> > I think this may be the right place to cover another significant misconception.
> We should certainly cover it somewhere and this looks as good a place as any.
> Something like...
> > "Another misconception common in the IETF and across the industry as a whole
> is that all RFCs are the work of the IETF. In fact, of the four sources of RFCs listed
> above (IETF, IAB, IRTF, and Independent Submissions), only those coming direct
> from the IETF  through working groups or sponsored by ADs are capable of having
> IETF consensus and being described as IETF specifications or standards."
> >
> 
> Accepted, but suggest we remove 'in the IETF and across the industry as
> a whole'.
> 
> So I'd suggest:
> 
> Another common misconception is that all RFCs are the work of the IETF.
> In fact, of the four sources of RFCs listed above (IETF, IAB, IRTF, and
> Independent Submissions), only those coming direct from the IETF
> through working groups or sponsored by ADs are capable of having IETF
> consensus and being described as IETF specifications or standards.

wfm

Adrian