IETF Logo Mail Archive

Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-incident-management-04

hutong <hutong@cmhi.chinamobile.com> Sun, 18 February 2024 04:15 UTC

Return-Path: <hutong@cmhi.chinamobile.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 BAEFCC14F5E8; Sat, 17 Feb 2024 20:15:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.808
X-Spam-Level:
X-Spam-Status: No, score=-6.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, 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
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 CoeCP3YA_5rb; Sat, 17 Feb 2024 20:15:29 -0800 (PST)
Received: from cmccmta1.chinamobile.com (cmccmta4.chinamobile.com [111.22.67.137]) by ietfa.amsl.com (Postfix) with ESMTP id 90A74C14F5E2; Sat, 17 Feb 2024 20:15:24 -0800 (PST)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[10.188.0.87]) by rmmx-syy-dmz-app04-12004 (RichMail) with SMTP id 2ee465d18457d76-6d647; Sun, 18 Feb 2024 12:15:21 +0800 (CST)
X-RM-TRANSID: 2ee465d18457d76-6d647
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from MacBook-Pro-4 (unknown[60.186.183.102]) by rmsmtp-syy-appsvr07-12007 (RichMail) with SMTP id 2ee765d184584d7-ef8c7; Sun, 18 Feb 2024 12:15:21 +0800 (CST)
X-RM-TRANSID: 2ee765d184584d7-ef8c7
Date: Sun, 18 Feb 2024 12:15:20 +0800
From: hutong <hutong@cmhi.chinamobile.com>
To: "henk.birkholz@ietf.contact" <henk.birkholz@ietf.contact>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-feng-opsawg-incident-management@ietf.org" <draft-feng-opsawg-incident-management@ietf.org>
Message-ID: <F3AB4A15-A8F2-4E6A-B255-F366FA64BD35@cmhi.chinamobile.com>
X-Mailer: MailMasterMac/4.17.11.1315 (13.2.0)
X-CUSTOM-MAIL-MASTER-SENT-ID: F80D311B-E54F-48C5-BF08-733F9E736A3F
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/V2IhjwsdjeTMdCeEljfwq5JSGWU>
Subject: Re: [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: Sun, 18 Feb 2024 08:45:11 -0000

Hi all，
I am not aware of any IPR related to this work.


----------------------------
Best Regards！
胡  通
18867101081


-----Original Message-----
From: Henk Birkholz <henk.birkholz@ietf.contact> Sent: Thursday, February 8, 2024 5:00 PM
To: OPSAWG <opsawg@ietf.org>; draft-feng-opsawg-incident-management@ietf.orgSubject: 🔔 IPR Call for draft-feng-opsawg-incident-management-04


Be aware: This is an external email.



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

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