Re: [OPSAWG] IPR POLL: Attachment circuits work
Qin Wu <bill.wu@huawei.com> Sun, 21 April 2024 10:14 UTC
Return-Path: <bill.wu@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 09878C14F603 for <opsawg@ietfa.amsl.com>; Sun, 21 Apr 2024 03:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.194
X-Spam-Level:
X-Spam-Status: No, score=-4.194 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 Ztm8Is8Rxvg1 for <opsawg@ietfa.amsl.com>; Sun, 21 Apr 2024 03:13:55 -0700 (PDT)
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 6B4FFC14F70C for <opsawg@ietf.org>; Sun, 21 Apr 2024 03:13:55 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VMkgc0Fdkz67ZyX for <opsawg@ietf.org>; Sun, 21 Apr 2024 18:11:40 +0800 (CST)
Received: from lhrpeml500001.china.huawei.com (unknown [7.191.163.213]) by mail.maildlp.com (Postfix) with ESMTPS id 63D79140AE5 for <opsawg@ietf.org>; Sun, 21 Apr 2024 18:13:52 +0800 (CST)
Received: from canpemm500006.china.huawei.com (7.192.105.130) by lhrpeml500001.china.huawei.com (7.191.163.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Sun, 21 Apr 2024 11:13:51 +0100
Received: from canpemm500005.china.huawei.com (7.192.104.229) by canpemm500006.china.huawei.com (7.192.105.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Sun, 21 Apr 2024 18:13:49 +0800
Received: from canpemm500005.china.huawei.com ([7.192.104.229]) by canpemm500005.china.huawei.com ([7.192.104.229]) with mapi id 15.01.2507.035; Sun, 21 Apr 2024 18:13:49 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Joe Clarke (jclarke)" <jclarke=40cisco.com@dmarc.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: IPR POLL: Attachment circuits work
Thread-Index: AdqT1JjXd8CTDe49H0GHlT5SsNGC7Q==
Date: Sun, 21 Apr 2024 10:13:49 +0000
Message-ID: <b27e7240704f4f21a3a6976c6aa4a7b5@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.84.55.113]
Content-Type: multipart/alternative; boundary="_000_b27e7240704f4f21a3a6976c6aa4a7b5huaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/vMcEWS0XMoAUv7cIllj5GnJqPUY>
Subject: Re: [OPSAWG] IPR POLL: Attachment circuits work
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, 21 Apr 2024 10:14:01 -0000
Hi, Joe: No, I'm not aware of any IPR that applies to these drafts -Qin De: OPSAWG <opsawg-bounces@ietf.org<mailto:opsawg-bounces@ietf.org>> En nombre de Joe Clarke (jclarke) Enviado el: viernes, 19 de abril de 2024 16:32 Para: opsawg@ietf.org<mailto:opsawg@ietf.org> Asunto: [OPSAWG] IPR POLL: Attachment circuits work We're up to WG LC on these four drafts. And while we did an IPR poll before, we want to be thorough since this work has evolved. https://datatracker.ietf.org/doc/draft-ietf-opsawg-ntw-attachment-circuit/ https://datatracker.ietf.org/doc/draft-ietf-opsawg-teas-attachment-circuit/ https://datatracker.ietf.org/doc/draft-ietf-opsawg-teas-common-ac/ https://datatracker.ietf.org/doc/draft-ietf-opsawg-ac-lxsm-lxnm-glue/ Are you aware of any IPR that applies to drafts identified above? Please state either: "No, I'm not aware of any IPR that applies to these drafts" or "Yes, I'm aware of IPR that applies to these drafts" 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. Also please send the response to the list above, and not unicast it. As of this time, no IPR has been disclosed on any of the four drafts. Joe
- [OPSAWG] IPR POLL: Attachment circuits work Joe Clarke (jclarke)
- Re: [OPSAWG] IPR POLL: Attachment circuits work mohamed.boucadair
- Re: [OPSAWG] ACTION NEEDED RE: IPR POLL: Attachme… samier Barguil
- Re: [OPSAWG] IPR POLL: Attachment circuits work LUIS ANGEL MUÑOZ, Vodafone
- Re: [OPSAWG] IPR POLL: Attachment circuits work Qin Wu
- Re: [OPSAWG] IPR POLL: Attachment circuits work Ogaki, Kenichi
- Re: [OPSAWG] IPR POLL: Attachment circuits work Wubo (lana)
- Re: [OPSAWG] IPR POLL: Attachment circuits work Oscar González de Dios
- Re: [OPSAWG] IPR POLL: Attachment circuits work Victor Lopez
- Re: [OPSAWG] IPR POLL: Attachment circuits work Richard Roberts
- Re: [OPSAWG] IPR POLL: Attachment circuits work Ivan Bykov
- Re: [OPSAWG] IPR POLL: Attachment circuits work Joe Clarke (jclarke)