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

Henk Birkholz <henk.birkholz@ietf.contact> Thu, 08 February 2024 16:01 UTC

Return-Path: <henk.birkholz@ietf.contact>
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 19E6BC14F5F6; Thu, 8 Feb 2024 08:01:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.806
X-Spam-Level:
X-Spam-Status: No, score=-2.806 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf.contact
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 zHlwKC53GVuS; Thu, 8 Feb 2024 08:01:02 -0800 (PST)
Received: from smtp04-ext3.udag.de (smtp04-ext3.udag.de [62.146.106.41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9990CC1DF553; Thu, 8 Feb 2024 08:00:09 -0800 (PST)
Received: from [IPV6:2a01:599:715:7438:54f1:41ab:5c36:89ba] (tmo-124-233.customers.d1-online.com [80.187.124.233]) by smtp04-ext3.udag.de (Postfix) with ESMTPA id EBDB6E0174; Thu, 8 Feb 2024 17:00:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.contact; s=uddkim-202310; t=1707408008; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=nrN8KAl7HFmgon/B8cCi42VppIAx9CvMTTrMfySBNm8=; b=FoqSzPWmDRS7RAbMN1k9yhvCkBKOcBQigCOooGcKzzZ5XzOd2HURo6TaUCIZKStQ4IzanC vBL6XIiWzbJZsMuUvnGI8ZWkqxRl+iado6QiKTHXuP3N8NXXj0Q7r5WTjyVJz3mOzMauuc POnR2asay/Dp5I8A61jpOHpvjUFjkZPU6Uly61dePNO4f/4FKqCIyHn632MkNR8JhhAah3 aDMqwq4twWF4pTLjm6S/wySZrrRBuqmLC517XfJE06DCWjnO1CBRORiwFFX0hO50I/bAEL C7LrwqBHgs4q0rFxeVgX//Jupz9ztC6mhhCdLB+nYtJ3vcFI+7ijhVQbYHF1bQ==
Message-ID: <42322df6-0ef5-a0ab-51b9-0a8d1c5ec755@ietf.contact>
Date: Thu, 08 Feb 2024 17:00:06 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
From: Henk Birkholz <henk.birkholz@ietf.contact>
To: OPSAWG <opsawg@ietf.org>, draft-feng-opsawg-incident-management@ietf.org
Content-Language: en-US
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Authentication-Results: smtp04-ext3.udag.de; auth=pass smtp.auth=henk.birkholz@ietf.contact smtp.mailfrom=henk.birkholz@ietf.contact
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/H_F-hqUd3VzXkER5_cG7dKIOYMM>
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: Thu, 08 Feb 2024 16:01:07 -0000

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