IETF Logo Mail Archive

[OPSAWG] 答复: IPR Poll for draft-ietf-opsawg-ntf [CORRECT]

qinfengwei <qinfengwei@chinamobile.com> Fri, 25 September 2020 01:22 UTC

Return-Path: <qinfengwei@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 0F5993A08E5; Thu, 24 Sep 2020 18:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qyaOhLbWxIts; Thu, 24 Sep 2020 18:22:03 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id 73BBF3A0901; Thu, 24 Sep 2020 18:22:01 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.1]) by rmmx-syy-dmz-app04-12004 (RichMail) with SMTP id 2ee45f6d462e12d-a81fe; Fri, 25 Sep 2020 09:21:50 +0800 (CST)
X-RM-TRANSID: 2ee45f6d462e12d-a81fe
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmccPC (unknown[223.69.29.169]) by rmsmtp-syy-appsvr01-12001 (RichMail) with SMTP id 2ee15f6d462bfc0-e7ff9; Fri, 25 Sep 2020 09:21:50 +0800 (CST)
X-RM-TRANSID: 2ee15f6d462bfc0-e7ff9
From: qinfengwei <qinfengwei@chinamobile.com>
To: 'Tianran Zhou' <zhoutianran@huawei.com>, 'opsawg' <opsawg@ietf.org>
Cc: draft-ietf-opsawg-ntf@ietf.org
References: <f5f87ae6f92d423ebd8430a40fa7dd0f@huawei.com>
In-Reply-To: <f5f87ae6f92d423ebd8430a40fa7dd0f@huawei.com>
Date: Fri, 25 Sep 2020 09:21:50 +0800
Message-ID: <005d01d692da$4018eef0$c04accd0$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005E_01D6931D.4E3C2EF0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdaSPYvICTiAtXU/STiu/7vSqFRHIgAnKWqw
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/TaqotTj7Lz9eHnkauW4sO410TSY>
Subject: [OPSAWG] 答复: IPR Poll for draft-ietf-opsawg-ntf [CORRECT]
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Sep 2020 01:22:05 -0000

Hi Tianran,

         

I am not aware of any IPR as a co-author.

 

 

 

Thanks,

Fengwei Qin

 

发件人: OPSAWG [mailto:opsawg-bounces@ietf.org] 代表 Tianran Zhou
发送时间: 2020年9月24日 14:43
收件人: opsawg
抄送: draft-ietf-opsawg-ntf@ietf.org
主题: [OPSAWG] IPR Poll for draft-ietf-opsawg-ntf [CORRECT]

 

Sorry for attaching a wrong link to the draft. Please see as follows.

 
Hi Authors,
 
Accompany with the WG LC, this mail starts the IPR poll.
 
Are you aware of any IPR that applies to draft-ietf-opsawg-ntf-04?
 
If you own or are aware of any IPR that applies to draft-ietf-opsawg-ntf-04,
please clarify whether this IPR been disclosed in compliance with IETF IPR
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
 
If you are listed as a document author or contributor please respond to this
email in OPSAWG mailing list regardless of whether or not you are aware of
any relevant IPR. The document will not advance to the next stage until a
response has been received from each author and contributor.
 
If you are not listed as an author or contributor but are on OPSAWG mailing
list, then please explicitly respond if you are aware of any IPR that has
not yet been disclosed in conformance with IETF rules.
 
Thanks,
Tianran

v2.23.0 | Report a Bug | By Email