Re: [Detnet] Regarding IPR on draft-joung-detnet-taxonomy-dataplane-01

peng.shaofu@zte.com.cn Mon, 25 March 2024 01:07 UTC

Return-Path: <peng.shaofu@zte.com.cn>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8FEDC14F616; Sun, 24 Mar 2024 18:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=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, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 79DFHma4IWbT; Sun, 24 Mar 2024 18:07:12 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A104C14F60D; Sun, 24 Mar 2024 18:07:10 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4V2vsj49nkz8XrRL; Mon, 25 Mar 2024 09:07:05 +0800 (CST)
Received: from njb2app06.zte.com.cn ([10.55.23.119]) by mse-fl1.zte.com.cn with SMTP id 42P16r9L017211; Mon, 25 Mar 2024 09:06:53 +0800 (+08) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njy2app02[null]) by mapi (Zmail) with MAPI id mid201; Mon, 25 Mar 2024 09:06:54 +0800 (CST)
Date: Mon, 25 Mar 2024 09:06:54 +0800
X-Zmail-TransId: 2afa6600ce2e784-76114
X-Mailer: Zmail v1.0
Message-ID: <20240325090654108YWAs_cAmkU629OYn2RD92@zte.com.cn>
In-Reply-To: <f401d15e-3e71-4a72-9f2e-913d7ed40b12@labn.net>
References: f401d15e-3e71-4a72-9f2e-913d7ed40b12@labn.net
Mime-Version: 1.0
From: peng.shaofu@zte.com.cn
To: lberger@labn.net
Cc: jjoung@smu.ac.kr, gengxuesong@huawei.com, tte@cs.fau.de, detnet-chairs@ietf.org, detnet@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 42P16r9L017211
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6600CE39.001/4V2vsj49nkz8XrRL
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/1Rdx0kd-MqgE4fCVu5S3dbEAcf0>
Subject: Re: [Detnet] Regarding IPR on draft-joung-detnet-taxonomy-dataplane-01
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2024 01:07:16 -0000

Hi Chairs, WG,

No, I'm not aware of any IPR that applies to this draft.

Regards,
PSF




Original


From: LouBerger <lberger@labn.net>
To: 정진우_교수_휴먼지능정보공학전공 <jjoung@smu.ac.kr>;Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com>;彭少富10053815;Toerless Eckert <tte@cs.fau.de>;
Cc: DetNet Chairs <detnet-chairs@ietf.org>;DetNet WG <detnet@ietf.org>;
Date: 2024年03月22日 20:14
Subject: Regarding IPR on draft-joung-detnet-taxonomy-dataplane-01


Authors, Contributors, WG, In preparation for WG Adoption Are you aware of any IPR that applies to drafts identified above? Please state either: "No, I'm not aware of any IPR that applies to this draft" or "Yes, I'm aware of IPR that applies to this draft" If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3669, 5378 and 8179 for more details)? If yes to the above, please state either: "Yes, the IPR has been disclosed in compliance with IETF IPR rules" or "No, the IPR has not been disclosed" If you answer no, please provide any additional details you think appropriate. If you are listed as a document author or contributor please answer the above by responding to this email regardless of whether or not you are aware of any relevant IPR. This document will not advance to the next stage until a response has been received from each author. NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES. If you are on the WG email list or attend WG meetings but are not listed as an author or contributor, we remind you of your obligations under the IETF IPR rules which encourages you to notify the IETF if you are aware of IPR of others on an IETF contribution, or to refrain from participating in any contribution or discussion related to your undisclosed IPR. For more information, please see https://www.ietf.org/standards/ipr/ Thank you, Lou (Co-Chair) PS Please include all listed in the headers of this message in your response.