Re: [dispatch] Dispatch IETF 118 outcomes & minutes

Philippe THOMY <philippe@loco-labs.io> Thu, 16 November 2023 10:22 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 66CB4C151063 for <dispatch@ietfa.amsl.com>; Thu, 16 Nov 2023 02:22:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable 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 GesTc-Ml0QNU for <dispatch@ietfa.amsl.com>; Thu, 16 Nov 2023 02:22:34 -0800 (PST)
Received: from mail-oa1-x36.google.com (mail-oa1-x36.google.com [IPv6:2001:4860:4864:20::36]) (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 BE578C151061 for <dispatch@ietf.org>; Thu, 16 Nov 2023 02:22:29 -0800 (PST)
Received: by mail-oa1-x36.google.com with SMTP id 586e51a60fabf-1eb7a8e9dd0so281634fac.3 for <dispatch@ietf.org>; Thu, 16 Nov 2023 02:22:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loco-labs-io.20230601.gappssmtp.com; s=20230601; t=1700130148; x=1700734948; darn=ietf.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=E2sxw4mMkWMbFv2SHH3DiNx/B7NO5lL32PjAggzqdCA=; b=o+arID0ksZAbD+bGSv8k/K3qMKTVicLrzr1Sw3gr3IbpQR2ZSOpYtCYf7MxqtghhBT udks8To0PBIOngn1q3MEEjkbBsO81+9l0/ve19Uqbobie5OtLeMtt3nEI3psadKywblq aQjH5tgIENnrEqikZWPY/+2fyO+G01QsKzfw5lMGGtlp76AfXmMuZiAKTYa9NVlyQitF ClQDVI59qtTIdaC1JpLWA/0sufvtHfAf7FcGHvlycBpAVl1SOwL3RcVbXK37OiaGiia4 L10W6NwFhrwlwmk01xExsPz7AIZrebuh2fwvwZJSwFc0sTqrm7ZH3LzgljSHK03S/Avu 7KyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700130148; x=1700734948; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=E2sxw4mMkWMbFv2SHH3DiNx/B7NO5lL32PjAggzqdCA=; b=NSpWcVALTBD978htCIFwNdexspIaMmCk7fDpCcz5dpIshuM3Pbp8dJ9ZQXU+cu67dX oRdF7dfn1mfMIJKyWvjXViTdRArzuYg2rm8yA/Sz+xdeHRhRMH5nFQHoLSibkAVHCQy7 P8Wj9ijeAz337f4EN3WzYF+uj8qGjS+IuzKJITbGY1gS/KTSn+09669R66DTY51Qs4vc Sy+vnZ72YBM5Z2WOl3QU458UbqYJ6qZsA75ihbvZw6W6VBTVmpyBoZ3hf/IazG98x89H sdNhGpvcDTmrZmFWfV3zssyZ6VbEp2kTJNGRsb4msv5RgUSUUKZlAjHLbheymYiJlGs0 YFlQ==
X-Gm-Message-State: AOJu0Yy2/Hx5XH+ZMptrp4MdI82/ZD5I69y6rQDuJ47Adwtc9o3icZQG t6Aw3F1smcRm90cvuIPBWbMErvx11aAlOw1W1HahTudHBjPJFiK+mw4=
X-Google-Smtp-Source: AGHT+IFiIhVTRnfERdHzULkWRgYo2+FDBKrPGtFI6G/hnYrrTrsOwaf7hJqKZ96YLGjXw8F0h7oCwkH/mD/8HZSvzwg=
X-Received: by 2002:a05:6870:2b04:b0:1e9:94c1:9179 with SMTP id ld4-20020a0568702b0400b001e994c19179mr21165504oab.21.1700130148561; Thu, 16 Nov 2023 02:22:28 -0800 (PST)
MIME-Version: 1.0
From: Philippe THOMY <philippe@loco-labs.io>
Date: Thu, 16 Nov 2023 11:22:17 +0100
Message-ID: <CAMsZS+T-8C+auqEiJ4_R7dEprN1M2HMNMNnzmXVXCjhY5pQNvA@mail.gmail.com>
To: dispatch-chairs <dispatch-chairs@ietf.org>
Cc: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="00000000000093c626060a4265cc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/CgofRbs-frmwkW0QzHIwB3c5GDM>
Subject: Re: [dispatch] Dispatch IETF 118 outcomes & minutes
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, 16 Nov 2023 10:22:35 -0000

Hi Shuping, Jim,

Thank you for taking the JSON-NTV topic into account in the WG dispatch and
I am sorry that I was not able to function properly during the
question/answer session (I was quite stressed, my level of English is not
good and I was not well prepared for the questions asked).

However, here is what I take away from the questions:


   - Relations with OpenAPI, JSON-Schema, YANG, Schema.org, HTTP media:

The questions are relevant and the JSON-NTV proposal must be clearly
positioned in relation to these standards. This will ensure the merits of
the proposal and to better understand how to use it.
-> work in progress



   - Link with CBOR:

A discussion email was sent on November 6 (but I have not yet received any
feedback from WG CBOR).
I am preparing a specific document on this point which presents the
envisaged interface (which remains in the logic of using the JSON layer as
indicated in the comment). This may help to communicate with WG CBOR.


I propose to work on these two subjects and share them in the form of
Internet-Drafts. Feedback on these documents will make it possible to
define the follow-up to be given on this subject.

Is this approach correct or should a particular procedure be considered as
part of the “dispatch” process ?

Have a nice day