[OPSAWG] 答复: 🔔 IPR Call for draft-feng-opsawg-incident-management-04
yuchaode <yuchaode@huawei.com> Fri, 09 February 2024 11:31 UTC
Return-Path: <yuchaode@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17921C14F684; Fri, 9 Feb 2024 03:31:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 MArqKIXGf2G2; Fri, 9 Feb 2024 03:31:49 -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 BEF66C14F6A3; Fri, 9 Feb 2024 03:31:49 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TWWnL1tg9z6K5vB; Fri, 9 Feb 2024 19:28:22 +0800 (CST)
Received: from lhrpeml100002.china.huawei.com (unknown [7.191.160.241]) by mail.maildlp.com (Postfix) with ESMTPS id CE52C140A35; Fri, 9 Feb 2024 19:31:46 +0800 (CST)
Received: from canpemm500002.china.huawei.com (7.192.104.244) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Fri, 9 Feb 2024 11:31:46 +0000
Received: from canpemm500002.china.huawei.com (7.192.104.244) by canpemm500002.china.huawei.com (7.192.104.244) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Fri, 9 Feb 2024 19:31:44 +0800
Received: from canpemm500002.china.huawei.com ([7.192.104.244]) by canpemm500002.china.huawei.com ([7.192.104.244]) with mapi id 15.01.2507.035; Fri, 9 Feb 2024 19:31:44 +0800
From: yuchaode <yuchaode@huawei.com>
To: Henk Birkholz <henk.birkholz@ietf.contact>, OPSAWG <opsawg@ietf.org>, "draft-feng-opsawg-incident-management@ietf.org" <draft-feng-opsawg-incident-management@ietf.org>
Thread-Topic: 🔔 IPR Call for draft-feng-opsawg-incident-management-04
Thread-Index: AQHaWqgObMkZwrFLKUWhqg6q/7OfebEB4btQ
Date: Fri, 09 Feb 2024 11:31:43 +0000
Message-ID: <4873adcbb0314b0cb58b6141cf7ee5ea@huawei.com>
References: <42322df6-0ef5-a0ab-51b9-0a8d1c5ec755@ietf.contact>
In-Reply-To: <42322df6-0ef5-a0ab-51b9-0a8d1c5ec755@ietf.contact>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.0.235]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/EihWuGZfbVAF1MOoHBnySTNh4bE>
Subject: [OPSAWG] 答复: 🔔 IPR Call for draft-feng-opsawg-incident-management-04
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Feb 2024 11:31:54 -0000
Hi Chairs: I am not aware of any IPR related to this work. -----邮件原件----- 发件人: Henk Birkholz [mailto:henk.birkholz@ietf.contact] 发送时间: 2024年2月9日 0:00 收件人: OPSAWG <opsawg@ietf.org>; draft-feng-opsawg-incident-management@ietf.org 主题: 🔔 IPR Call for draft-feng-opsawg-incident-management-04 Dear authors and contributors, as a part of the adoption process, the chairs would also like to issue a first IPR call on the content of adoption candidates (there will also be a second IPR call after successful WGLC). Please respond on-list as to whether or not you are aware of any IPR that pertains to draft-feng-opsawg-incident-management-04. If you are aware of IPR, please also indicate whether or not this has been disclosed per IETF IPR rules (see RFCs 3669, 5378, and 8179). For the OPAWG co-chairs, Henk
- [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-inciden… Henk Birkholz
- Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-inc… Qin Wu
- [OPSAWG] 答复: 🔔 IPR Call for draft-feng-opsawg-inc… yuchaode
- Re: [OPSAWG] 答复: 🔔 IPR Call for draft-feng-opsawg… chong feng
- Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-inc… Thomas.Graf
- Re: [OPSAWG] IPR Call for draft-feng-opsawg-incid… 赵星
- Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-inc… LUIS MIGUEL CONTRERAS MURILLO
- Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-inc… hutong
- Re: [OPSAWG] [警惕!外部邮件]转发: IPR Call fordraft-feng… 郑滟雷(联通集团本部)
- Re: [OPSAWG] [**EXTERNAL**] 🔔 IPR Call for draft-… Davis, Nigel
- Re: [OPSAWG] 转发: IPR Call for draft-feng-opsawg… xuyunbin@caict.ac.cn