Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm-encapsulation
xiao.min2@zte.com.cn Thu, 11 April 2024 00:50 UTC
Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE5BC14F61A; Wed, 10 Apr 2024 17:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.193
X-Spam-Level:
X-Spam-Status: No, score=-4.193 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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, UNPARSEABLE_RELAY=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 7uKdZgkimHv7; Wed, 10 Apr 2024 17:50:27 -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 5A0C5C14F60C; Wed, 10 Apr 2024 17:50:20 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (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 4VFLhS6Tpkz8XrRD; Thu, 11 Apr 2024 08:50:16 +0800 (CST)
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 mxct.zte.com.cn (FangMail) with ESMTPS id 4VFLgt5tHwz501gF; Thu, 11 Apr 2024 08:49:46 +0800 (CST)
Received: from njy2app04.zte.com.cn ([10.40.12.64]) by mse-fl1.zte.com.cn with SMTP id 43B0neTj048814; Thu, 11 Apr 2024 08:49:40 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njb2app07[null]) by mapi (Zmail) with MAPI id mid201; Thu, 11 Apr 2024 08:49:40 +0800 (CST)
Date: Thu, 11 Apr 2024 08:49:40 +0800
X-Zmail-TransId: 2aff661733a4026-66d2b
X-Mailer: Zmail v1.0
Message-ID: <20240411084940819H6T7i4_tAnLl8BaU0kJHW@zte.com.cn>
In-Reply-To: <771469D9-B9AD-4FE2-B209-82DB787430A6@tony.li>
References: 771469D9-B9AD-4FE2-B209-82DB787430A6@tony.li
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: tony.li@tony.li
Cc: mpls@ietf.org, mpls-chairs@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 43B0neTj048814
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 661733C8.000/4VFLhS6Tpkz8XrRD
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/UyltYmupgWVI7X0EvfpqrybJiI8>
Subject: Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm-encapsulation
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2024 00:50:29 -0000
No, I'm not aware of any IPR that applies to this draft. Best Regards, Xiao Min Original From: TonyLi <tony.li@tony.li> To: mpls <mpls@ietf.org>; Cc: mpls-chairs <mpls-chairs@ietf.org>; Date: 2024年04月11日 00:34 Subject: [mpls] IPR poll for draft-ietf-mpls-inband-pm-encapsulation _______________________________________________ mpls mailing list mpls@ietf.org https://www.ietf.org/mailman/listinfo/mpls [WG chair hat: on] Hi all, This starts an IPR poll for draft-ietf-mpls-inband-pm-encapsulation. All authors and contributors MUST reply to this email. Datatracker shows one current IPR disclosure (https://datatracker.ietf.org/ipr/4745/) for this draft. 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 and contributor.Thanks, Tony
- [mpls] IPR poll for draft-ietf-mpls-inband-pm-enc… Tony Li
- Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm… xiao.min2
- Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm… chengweiqiang
- Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm… wangminxue@chinamobile.com
- Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm… Tianran Zhou
- Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm… Tony Li
- Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm… Yoav Peleg
- Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm… 戴锦友
- Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm… Tianran Zhou
- Re: [mpls] IPR poll for draft-ietf-mpls-inband-pm… Weiqiang Cheng