IETF Logo Mail Archive

Re: [dispatch] Request for feedback on draft-thomy-json-ntv-01

Philippe THOMY <philippe@loco-labs.io> Thu, 14 September 2023 19:55 UTC

Return-Path: <philippe@loco-labs.io>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7098C151071 for <dispatch@ietfa.amsl.com>; Thu, 14 Sep 2023 12:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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=loco-labs-io.20230601.gappssmtp.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 33y9gPl51Dbn for <dispatch@ietfa.amsl.com>; Thu, 14 Sep 2023 12:55:09 -0700 (PDT)
Received: from mail-oo1-xc2e.google.com (mail-oo1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (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 51427C14CE55 for <dispatch@ietf.org>; Thu, 14 Sep 2023 12:55:09 -0700 (PDT)
Received: by mail-oo1-xc2e.google.com with SMTP id 006d021491bc7-57355a16941so824370eaf.2 for <dispatch@ietf.org>; Thu, 14 Sep 2023 12:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loco-labs-io.20230601.gappssmtp.com; s=20230601; t=1694721308; x=1695326108; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=S4pgsmFlBAvVqgWaUNdRgwECqhCWrhaoDC0nwpXr0R0=; b=TXx7doHJuYOVHHZxesyZ0nD94m2H9fmDSSSnquXEApKylyqMhVbqnfhnGBtRzcwX2f fixWwPT+QttvHM1kmxpEWD9tR2jMvXRtOV43E65NriqSKR5nkeEKQ/TMWLOlEO/ORojW yyIPUZ3u/kWu7GF3E34v4y8exku60oD3zpMCjNmgYM/2hKA96uNPE98jLOnpHeTd9wd7 WGoE17PLs+rt/UtkYM1c4w1c10FlsHKsLJX/TofpLWpIcSjh78w2DFCvKsw193q4Ae6I lPBZahZL6umLFw0kg1h+B8IauDBF79FqiE6mgOp92GirZ6Z1ERrcrlJcaEjRWGnGmfpF 7MUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694721308; x=1695326108; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=S4pgsmFlBAvVqgWaUNdRgwECqhCWrhaoDC0nwpXr0R0=; b=OKoA7fXav3koHydnR6WcV3P7pMLtcDqewAbNBC6qixzQEHrstaFEjLCtFvMGmz05gR sVcX7JvCA0M631eupTHeQZGIai4xUJgz1m5fbYlbdrSK48e7zIYBWNQ/6DIGAI1mV5G+ m1jkkD0coBUi4dKo2zGYZm2nVnrgwhdDjAaWE323ar9nVytufdrsqHT7a24jB3VIEI9S H4FNYbV41nDlsAA/mwlp+PuOCgIgYM+c90c66tgrtqsVEJVZQFXZfTL7wc4Zw6JN7NcN W4PBEqYcoeqh5KFJNPQUAXmOSEM4xGRtd6/BJYAHApfjV2R9PMbkkQ5adyTU6GCSFO1e LpYQ==
X-Gm-Message-State: AOJu0YyS/uVnQCIlIR2b78BSIMwvOmDZuRXvs3hJnPlvR/UxJvzOih0v 82TghEDmrrcErmQ1IgOgf4VvIHdElucRQI9tud8ErUxo46dRcXQECwI=
X-Google-Smtp-Source: AGHT+IHZgAJ/7h9lVfKcsGLci3KozYu2+P3BCGVaKWHnOmN0dB//n3gJK8MdDOswj0hNBFjSvnEslJ5ENl/UWOAyoYg=
X-Received: by 2002:a05:6870:46a7:b0:1c0:c42f:6db2 with SMTP id a39-20020a05687046a700b001c0c42f6db2mr7081626oap.37.1694721308528; Thu, 14 Sep 2023 12:55:08 -0700 (PDT)
MIME-Version: 1.0
References: <CAMsZS+RALbxZNVZwbkRdinAJp_=e9LskROJmQR=41woN6EEsMA@mail.gmail.com> <87o7i4si0h.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87o7i4si0h.fsf@hobgoblin.ariadne.com>
From: Philippe THOMY <philippe@loco-labs.io>
Date: Thu, 14 Sep 2023 21:54:57 +0200
Message-ID: <CAMsZS+T+ocd+AAvjr2xOi8zD15=T-NddrLFWwKHQp3RwkmcL-Q@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Cc: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="00000000000096a4650605570ddf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/mu7kHsCdyw2_dcWe4cEYrVltZCY>
Subject: Re: [dispatch] Request for feedback on draft-thomy-json-ntv-01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2023 19:55:11 -0000

On Thu, Sep 14, 2023 at 8:54 PM Dale R. Worley <worley@ariadne.com> wrote:

At first look, the proposals in draft-thomy-json-ntv-01 look sound.


Thanks a lot !

But
> I'm not sure that JSON-NTV is used enough in the IETF to be suitable as
> an RFC.


 Two interpretations are possible:
- JSON-NTV is not used enough in the IETF, so it will not be able to evolve
into RFC
- JSON-NTV is not used enough in the IETF, it must therefore be used more
in the IETF to evolve into RFC
(I prefer the second interpretation !!)

Naively, JSON-NTV seems like part of, or an extension of, NTV
> itself, and would better fit as an addition to "[JSON-NTV] Thomy, P.,
> "JSON-NTV", 2022".
>

I interpreted this point as an answer to the 3rd and 4th questions but I'm
not sure I understood correctly:
- does the [JSON-NTV] notation refer to a possible WG?
- is it appropriate to approach the NTV concept and the associated JSON-NTV
concept separately or, on the contrary, to treat them together?

Philippe

v2.27.8 | Report a Bug | By Email | System Status