Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

john heasley <heas@shrubbery.net> Fri, 19 July 2019 19:05 UTC

Return-Path: <heas@shrubbery.net>
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 961A3120326 for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2019 12:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 M_3mUrHSz9fu for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2019 12:05:34 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8916A120223 for <ietf@ietf.org>; Fri, 19 Jul 2019 12:05:34 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 432EE244E5; Fri, 19 Jul 2019 19:05:34 +0000 (UTC)
Date: Fri, 19 Jul 2019 19:05:34 +0000
From: john heasley <heas@shrubbery.net>
To: John C Klensin <john-ietf@jck.com>
Cc: ietf@ietf.org
Subject: Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
Message-ID: <20190719190534.GG38674@shrubbery.net>
References: <F2D5DCCF-4051-444B-9522-9E11F9F93005@fugue.com> <869599E9-7571-4677-AB9A-961027549C54@network-heretics.com> <144ff436-a7a2-22f7-7b06-4d0b3bcfefac@joelhalpern.com> <20190719041456.GL33367@vurt.meerval.net> <254fc5f6-3576-a62f-b84f-a7c5d29b0055@joelhalpern.com> <a1561aa7-5f41-0e2a-1892-cfb587196ac0@gmail.com> <C3D53639-C2C0-42CE-9708-99294091E012@puck.nether.net> <a17a8648-14c8-1889-4ee3-86996ff6281e@gmail.com> <3B0C189A-D56B-430F-82FF-19DE0DC788DE@puck.nether.net> <BA80E73F53C26B9191294131@JcK-HP5.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BA80E73F53C26B9191294131@JcK-HP5.jck.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zVd2n6JLBKRW-Em6vquEfeoyCnQ>
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: Fri, 19 Jul 2019 19:05:35 -0000

Fri, Jul 19, 2019 at 10:48:41AM -0400, John C Klensin:
> and review only by
> self-selected specialist groups.

No one has said/suggested 'self-selected'.  anyone can review any document.

> I don't see what value doing the
> work in the IETF provides other than an apparent endorsement

Because it is related to products of the ietf and that is where,
presumably, the expertise for the given product lies.  If you want to
fix the pluggable optic MSA, I presume you would go to the IEEE - not
my area of expertise, so don't bother correcting which group mangled it.

> that can be presented as involving more than a working group.

This seems like a claim that a LD with the aforementioned review process
would affect the reputation of RFCs, which I reject.  it is presented as
involving the process and those whom the document type claims.  RFC has
a process, BCP has one, LD would have one, and PRETZEL would have one.
BCP, mpov, carries far more weight than RFC.

> Exactly.  And if I wanted to push parts of my i18n work forward,

which is what?  What is your i18n work?  I do not know.  If it is
definition of the wire formats, etc - no, that is not the goal here.
Not mine, nor Job's.  A 7525-like document about i18n would be, again
mpov.