IETF Logo Mail Archive

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

Rob Sayre <sayrer@gmail.com> Tue, 19 July 2022 23:40 UTC

Return-Path: <sayrer@gmail.com>
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 17BCBC15A72F for <architecture-discuss@ietfa.amsl.com>; Tue, 19 Jul 2022 16:40:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Ex7PjCW5a8bX for <architecture-discuss@ietfa.amsl.com>; Tue, 19 Jul 2022 16:40:01 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 491ECC157B48 for <architecture-discuss@ietf.org>; Tue, 19 Jul 2022 16:40:01 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id w12so21640588edd.13 for <architecture-discuss@ietf.org>; Tue, 19 Jul 2022 16:40:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=e/3fnM/Am9x4JjcQI2St4ODNuazvG91Bpz6FCMqGxHo=; b=Vp1vG0LG5XvCpTYKAQxZnUZ36V0dW/qEaJzFRlsfwonDZ5HixX9C09roCdx+f7VfZT kXY7EjLrsck25uQpEbuQSArXTqyz9qcqOkW0uygiebsCtc+/Kqnkm+mC+BE96l9V7Kz4 PNy861fZm4LZPIgRa35EjW0qm6j5wDb40VMinAEGRY+KVZ7JyEX0drqdVHqDvmiCzdGl xMohBQZEnbA/yevYG/bcB9YaNJIWs6zIp0P1TNuDqTcviet5F9f6IgHb5mxTEB994zkp 2r0yGYoWgL4dh9OX3xL9+U0ep72CjpxS2lf1Zxd0i77DZz5F8OYmQ4TsPIocO6IexozI UZMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=e/3fnM/Am9x4JjcQI2St4ODNuazvG91Bpz6FCMqGxHo=; b=XC3pnr5mPa5XmA2hmOVutyyyhMXqCchrBunRgED7PiCEn5rve1HPLWPamu85u3UM0/ ReB+TvOTB+kfl311LH4YB6EIwqxdyvLAN7TcvvRsUNc75/umZtysEh6gX0pVoEL+awJH tbbGywwv7+gYPPQNn7TqSGmZf+z1uTG20ymgmCtALCJKSh0fd9l0MaVRIZpVPasSHLAM ndDGNTknGS+qwdxtbAXvLeNqxQ2UZehdoMM/p/a4XOYZkCaz2Mg9k0uYfFU05v4WsaRP G2rPfTMBxntsGvIVSyjuenUK40n5tz11wXtcWZ7dVJozds/zxBo0E8ufw4L8TuSyNN0T QyVw==
X-Gm-Message-State: AJIora9nRRcP4ARFT9jaR30VkWCkx2pKFtLatzffi7pzQ0m0nLuMGjGg TfTxzZ9ZaWzNwBLaWOXquO9rxMcvBSbcacnFaea1Ttcl
X-Google-Smtp-Source: AGRyM1v69YohKr5z6SOWOwqHxGLyCICyan7/T5Ycj6iRoLCfntsw0R9DlwFjQfg80HYeRAMh/NMN9EbgkaPnu2eFeA4=
X-Received: by 2002:aa7:d74a:0:b0:43b:a51d:4c3c with SMTP id a10-20020aa7d74a000000b0043ba51d4c3cmr3891742eds.127.1658273999239; Tue, 19 Jul 2022 16:39:59 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6Sxy66Yrr=0wnSGOUFBboFBaJsWzrWduvXep9L5akmYiNg@mail.gmail.com> <CAChr6Sx5OtZLf1c27CzV7UMfHHnRgP5pUbga0+Jij7rtzq5krw@mail.gmail.com> <CAChr6SxQV-fW9KkTEsMQ1HaU7tOKmu6Ce4DBUB2eDtCYA0YYjg@mail.gmail.com> <CAMm+LwitigRr4F9Q1chUzDj5UqR97nkBmu3bT3yzyrQu9iUF_w@mail.gmail.com>
In-Reply-To: <CAMm+LwitigRr4F9Q1chUzDj5UqR97nkBmu3bT3yzyrQu9iUF_w@mail.gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Tue, 19 Jul 2022 16:39:47 -0700
Message-ID: <CAChr6SzJVX=3y01uggHriTOoOEgq4oJnR91eFRcsZkFwYofMyw@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="000000000000aa3ef805e43100ec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/f4fYAyL6Jgs65h2FLYbOc0eeQHI>
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: Tue, 19 Jul 2022 23:40:03 -0000

On Tue, Jul 19, 2022 at 4:28 PM Phillip Hallam-Baker <phill@hallambaker.com>
wrote:

> I don't think discussing the history of JSON really helps much at this
> stage, decisions were made and it is impractical to change them.
>
> Insisting that the spec preclude future changes is not a choice I would
> have made but all that it means in practice is that if you want to revise
> the JSON spec, you have to change the name.
>

Exactly right. This is because JSON is self-describing. An intentional
design trade-off.

FWIW, no one really uses it for high traffic use cases unless they are
required to. They use gRPC / Thrift / etc. These things are more efficient
by more than 2x, but less than 10x. The real advantage is that they don't
require a wiki page about what is in the JSON, though. You get something
slightly more efficient, but with built in documentation.

thanks,
Rob

v2.23.0 | Report a Bug | By Email