RE: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

Eric Gray <eric.gray@ericsson.com> Wed, 10 July 2019 17:18 UTC

Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE27E1202A6 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2019 10:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 TIDGd3prazfq for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2019 10:18:41 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on060b.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe45::60b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C80351202BB for <ietf@ietf.org>; Wed, 10 Jul 2019 10:18:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+i8t1i5M7Z6qrIMHqYL+b08MwB2UcJQeOXjUtVd7/L8=; b=rIErd5wz4+L2M0aShaAm+Gb7nN1f61LkeqlxFHFdfb4f32164kOmz1yHbWPMOwM/OiNazBKarvnuxrH6Ba5k6ZNNSoN3xtOKhhosjum8W+vgIIL8lJNED4Fha3orTw7N171GPJ4NB3bTHW310KlZ9gkb7lZvL/6spe4cn29bSbw=
Received: from BN8PR15MB2644.namprd15.prod.outlook.com (20.179.138.27) by BN8PR15MB3346.namprd15.prod.outlook.com (20.179.75.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.19; Wed, 10 Jul 2019 17:18:38 +0000
Received: from BN8PR15MB2644.namprd15.prod.outlook.com ([fe80::155b:861f:389b:3434]) by BN8PR15MB2644.namprd15.prod.outlook.com ([fe80::155b:861f:389b:3434%7]) with mapi id 15.20.2052.020; Wed, 10 Jul 2019 17:18:37 +0000
From: Eric Gray <eric.gray@ericsson.com>
To: Richard Barnes <rlb@ipv.sx>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
CC: Julian Reschke <julian.reschke@gmx.de>, IETF Rinse Repeat <ietf@ietf.org>
Subject: RE: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
Thread-Topic: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
Thread-Index: AQHVMggcXk+jhSPBd0KEtTl3wmU5cKa5shaAgAA7GwCAAAQGAIAAgmmAgAALfQCAADLVAIAB0nqAgAFv7YCAAA33AIADMGWAgAAHygCAAANZgIAAGIcAgAANiwCAAANxgIAB3M2AgABG2oCAAFy3gIAAAuIAgAAEMwCAABIuAIAAEL3A
Date: Wed, 10 Jul 2019 17:18:37 +0000
Message-ID: <BN8PR15MB2644AAB9613EB10DA5F080EC97F00@BN8PR15MB2644.namprd15.prod.outlook.com>
References: <20190704140552.GE49950@hanna.meerval.net> <b0943792-1afc-0c94-51b7-f2d393ef39c5@network-heretics.com> <20190705205723.GI55957@shrubbery.net> <20190706185415.GB14026@mit.edu> <CABcZeBPgNr5UqQ0pLwwNu5wh0g9L9wCd6YyYKCUDO37SPru-_Q@mail.gmail.com> <20190708202612.GG60909@shrubbery.net> <9ae14ad1-f8d5-befb-64e4-fff063c88e02@network-heretics.com> <CABcZeBOH9LH8Jrz-A5eu9arqUb+bx8xs_eKWi0pyoh7a3qpOPA@mail.gmail.com> <20190708223350.GO3508@localhost> <af3b25d6-af16-a96a-c149-61d01afb4d01@network-heretics.com> <20190708233438.GP3508@localhost> <ea0b9894-ae9d-55a9-a082-af7aac5be66a@huitema.net> <944332dc-bb2a-0717-8b9f-254b036fe59f@gmx.de> <m2pnmingsi.wl-randy@psg.com> <CAL02cgTBL7w02sWx4kaqGLQe8bGm4jRMyMY9v7yJw57_Sp=PgA@mail.gmail.com> <013801d53729$708c5710$51a50530$@olddog.co.uk> <CAL02cgQPuvVdO6UXkXYLwvD41+2_pBRwj0MXG=qA1oPt73BFmw@mail.gmail.com>
In-Reply-To: <CAL02cgQPuvVdO6UXkXYLwvD41+2_pBRwj0MXG=qA1oPt73BFmw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=eric.gray@ericsson.com;
x-originating-ip: [198.24.6.220]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 576f05e3-eb5a-405a-24af-08d7055aa59a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BN8PR15MB3346;
x-ms-traffictypediagnostic: BN8PR15MB3346:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BN8PR15MB3346AD3C1BA50A4F0993504097F00@BN8PR15MB3346.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3044;
x-forefront-prvs: 0094E3478A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(396003)(39860400002)(346002)(136003)(376002)(199004)(189003)(55674003)(64756008)(66556008)(66446008)(66946007)(76116006)(66476007)(71190400001)(71200400001)(52536014)(74316002)(7736002)(256004)(2906002)(5660300002)(66066001)(86362001)(5024004)(14444005)(76176011)(99286004)(7696005)(2501003)(26005)(186003)(44832011)(53546011)(6506007)(68736007)(66574012)(8936002)(486006)(81156014)(8676002)(81166006)(476003)(102836004)(446003)(11346002)(9686003)(54896002)(55016002)(236005)(4326008)(478600001)(229853002)(25786009)(6306002)(14454004)(316002)(3846002)(6436002)(790700001)(6116002)(33656002)(54906003)(110136005)(6246003)(53936002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN8PR15MB3346; H:BN8PR15MB2644.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 5Z85ad79V+ooRxYU5oLQsFHa2vdWPN4YcifDJxnYGNWqpCNsPj81E8koWo/JplPhZTsNfD6bPk6qlwNxwUv8vkv9U+RUIO+Hk6NsUMnccXalt7YvL6cmy8+mkTdbZ+X7tEKLPSQC1sxoYA4ZF5JR3Cd2XEIKxaiV4ahnAo+MHfpDCYpBuHuTMXLUvXtGuEDZPE8pTgbV0SBXxd7mJcNieRm956oiR8LH+t7Lhu5ruRQ8IgQ+XDkJXaY9v9D4yTGldex2t2nnRyx20XvsJQdS82AZZmi6z7wUYa2JdE/zokjLtAWBzvsm1R94aB0TPX/PK33ohqPuU5ULIbcsq4FydTFh6NqgLu8VUl7/bCIBIcfkzRMqThuPDAa0MocwuvL0chmKahGpgyvo+AVr4BHMpUEOh48Grql9CW9iUSrFjvo=
Content-Type: multipart/alternative; boundary="_000_BN8PR15MB2644AAB9613EB10DA5F080EC97F00BN8PR15MB2644namp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 576f05e3-eb5a-405a-24af-08d7055aa59a
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jul 2019 17:18:37.7463 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: eric.gray@ericsson.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR15MB3346
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DcGJT5Y9dtdSc-IeqdZUMSLE64c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2019 17:18:45 -0000

Richard,

A few things that people who suggest a complete replacement of tools should think about:

  1.  frequently introducing yet another learning curve doesn’t shorten the overall learning curve for anyone.  If there is any benefit in it for anyone, it is that it tends to level the playing field. I doubt there is any way to determine definitively whether that is a good thing, or a bad thing.  YMMV.
  2.  wholesale replacement of tools has a direct analog in many other areas.  Imagine for instance if, in trades (wood working, metal working, etc.), someone suggested obsoleting the tools used by experienced craftsmen (ignore any seeming gender specificity) in order to (theoretically) simplify the learning curve for apprentices.  The theory behind any such move would be that this would allow apprentices to more quickly become qualified tradesmen – but that theory would require time to validate and would likely severely impact skilled production in the meantime.
  3.  in this particular work (i.e. – standardization) – as with a number of other areas – “tools” is actually the area with the least significant learning curve.  A far more significant learning curve is associated with learning the many things that have been tried, and determined to be unworkable, over a time period far greater than the tools learning curve for even the most casual tools user.

I suspect that a prolonged discussion of the benefits of introducing new tools is misplaced effort.

--
Eric

From: ietf <ietf-bounces@ietf.org> On Behalf Of Richard Barnes
Sent: Wednesday, July 10, 2019 11:17 AM
To: adrian@olddog.co.uk
Cc: Julian Reschke <julian.reschke@gmx.de>; IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

You're absolutely correct that any tool comes with a learning curve.  The trick is "bringing the mountain to Mohammed" as it were; using tools for which many people have already climbed the curve.  By definition, anything that is IETF-custom is brand-new learning curve for a newcomer.

--Richard


On Wed, Jul 10, 2019 at 10:12 AM Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>> wrote:
Is it really that hard?
Even crusty old idiots like me have worked out how to use an editor to make XML that is acceptable to XML2RFC. I doubt that I am clever or more talented than Fellows of major engineering organizations.
All tools (even github) require to be learned.

Replace tools with better tools, by all means.
But don’t make changes for personal preference: that way lies unending debates about whose preference is best.

Thanks,
Adrian

From: ietf <ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org>> On Behalf Of Richard Barnes
Sent: 10 July 2019 14:57
To: Randy Bush <randy@psg.com<mailto:randy@psg.com>>
Cc: Julian Reschke <julian.reschke@gmx.de<mailto:julian.reschke@gmx.de>>; IETF Rinse Repeat <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

I'm glad it works for you.  The non-IETF-habituated new authors I've worked with have found it mystifying.  Including everyone from junior engineers to Fellows of major engineering organizations.

As Christian says, our continued attachment to bespoke tools is a barrier to getting new work in the IETF, and thus detrimental to the long-term health of the organization.

--RLB


On Wed, Jul 10, 2019 at 9:47 AM Randy Bush <randy@psg.com<mailto:randy@psg.com>> wrote:
>> Tooling is just one of the problems with XML2RFC. The real issue is
>> that XML2RFC is completely specific to the IETF. This translate into
>> training ...
> It also has been optimized for the production of RFCs. Also note that
> many changes in the v3 vocab just align the language with HTML (lists
> and tables come to mind).

from an xml non-lover:

xml2rfc rocks!  it produces the baroqe, designed by committee, internet
draft format from input which i can easily produce in my text editor.

and the support, maintenance, and responsiveness of the tools team is
simply stunning.

[ and for the poster who wished for a gooey, there is one ]

thank you!

randy