Re: [arch-d] draft-iab-protocol-maintenance / JSON feedback

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 18 July 2022 14:05 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25332C14F743 for <architecture-discuss@ietfa.amsl.com>; Mon, 18 Jul 2022 07:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rXuNv51jhQ9z for <architecture-discuss@ietfa.amsl.com>; Mon, 18 Jul 2022 07:05:22 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 5AF16C14F732 for <architecture-discuss@ietf.org>; Mon, 18 Jul 2022 07:05:22 -0700 (PDT)
Received: from [10.32.60.108] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id 26IE3R1k065291 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <architecture-discuss@ietf.org>; Mon, 18 Jul 2022 07:03:28 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] claimed to be [10.32.60.108]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: architecture-discuss@ietf.org
Date: Mon, 18 Jul 2022 07:05:19 -0700
X-Mailer: MailMate (1.14r5798)
Message-ID: <FC92582C-C77B-4EA2-BAC4-B1CCBA941B05@vpnc.org>
In-Reply-To: <02490878-5A5F-43EB-AFD4-265A3FD6849B@tzi.org>
References: <CAChr6Sxy66Yrr=0wnSGOUFBboFBaJsWzrWduvXep9L5akmYiNg@mail.gmail.com> <5a9857d7-9923-46e1-9535-16663f51bc6f@www.fastmail.com> <02490878-5A5F-43EB-AFD4-265A3FD6849B@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/KG0tNyZ3FzT4VlMUAaVjxzfpXzI>
Subject: Re: [arch-d] draft-iab-protocol-maintenance / JSON feedback
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2022 14:05:26 -0000

Carsten's detailed history of JSON (which I fully agree with, having 
been there for it in different roles) again points out the difficulty of 
draft-iab-protocol-maintenance: many of the definitive statements in it 
about what worked/works and what didn't/doesn't are easy to get wrong 
due to limited viewpoints. Having bad examples weakens the overall goal 
of the document, and many readers might be turned off to the document 
once they hit the second example they disagree with.

--Paul Hoffman