IETF Logo Mail Archive

[dispatch] 答复: Dispatch IETF 118 outcomes & minutes

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Fri, 17 November 2023 02:22 UTC

Return-Path: <pengshuping@huawei.com>
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 26D14C151064; Thu, 16 Nov 2023 18:22:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.206
X-Spam-Level:
X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, 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
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 uNnC9nWiTil6; Thu, 16 Nov 2023 18:22:07 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A44FBC14CE53; Thu, 16 Nov 2023 18:22:07 -0800 (PST)
Received: from lhrpeml500005.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SWgcJ2hbrz6D8yp; Fri, 17 Nov 2023 10:20:48 +0800 (CST)
Received: from canpemm100007.china.huawei.com (7.192.105.181) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Fri, 17 Nov 2023 02:22:03 +0000
Received: from canpemm500008.china.huawei.com (7.192.105.151) by canpemm100007.china.huawei.com (7.192.105.181) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Fri, 17 Nov 2023 10:22:01 +0800
Received: from canpemm500008.china.huawei.com ([7.192.105.151]) by canpemm500008.china.huawei.com ([7.192.105.151]) with mapi id 15.01.2507.031; Fri, 17 Nov 2023 10:22:01 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Philippe THOMY <philippe@loco-labs.io>, dispatch-chairs <dispatch-chairs@ietf.org>
CC: "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: [dispatch] Dispatch IETF 118 outcomes & minutes
Thread-Index: AQHaGHbXl5SKo0qrTkC7Q2z/gou2KbB9wpmw
Date: Fri, 17 Nov 2023 02:22:01 +0000
Message-ID: <a49f9775a99c4722b1fd3b683b3b4529@huawei.com>
References: <CAMsZS+T-8C+auqEiJ4_R7dEprN1M2HMNMNnzmXVXCjhY5pQNvA@mail.gmail.com>
In-Reply-To: <CAMsZS+T-8C+auqEiJ4_R7dEprN1M2HMNMNnzmXVXCjhY5pQNvA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.43.32]
Content-Type: multipart/alternative; boundary="_000_a49f9775a99c4722b1fd3b683b3b4529huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/CkoLoWz-PzBnSBwqa6oLS_SJhBI>
Subject: [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: Fri, 17 Nov 2023 02:22:12 -0000

Hi Philippe,

No worries, you did well.

Based on the discussions during the meeting, the dispatch outcome is: CBOR is not the right place, try to get
feedback from JSON Shema. You could focus more on getting feedback from the JSON Shema. If you think that it is not clear with CBOR, you could continue to consulting the corresponding working group chairs to get their feedback and opinions. Drafts are good to convey your ideas.

BTW, the recording of our dispatch meeting is also available in Youtube.
https://www.youtube.com/watch?v=KMjX7atFfpo

Thank you!

Best Regards,
Shuping

发件人: Philippe THOMY <philippe@loco-labs.io>
发送时间: 2023年11月16日 18:22
收件人: dispatch-chairs <dispatch-chairs@ietf.org>
抄送: dispatch@ietf.org
主题: Re: [dispatch] Dispatch IETF 118 outcomes & minutes

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

v2.23.0 | Report a Bug | By Email