Re: [Cats] Regarding IPR on draft-ldbc-cats-framework

Adrian Farrel <adrian@olddog.co.uk> Fri, 23 February 2024 16:36 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: cats@ietfa.amsl.com
Delivered-To: cats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F843C14F5EC; Fri, 23 Feb 2024 08:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.803
X-Spam-Level:
X-Spam-Status: No, score=-2.803 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=olddog.co.uk
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 xV6gG9XYUMqh; Fri, 23 Feb 2024 08:36:18 -0800 (PST)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9802C14F5F1; Fri, 23 Feb 2024 08:36:16 -0800 (PST)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta6.iomartmail.com (8.14.7/8.14.7) with ESMTP id 41NGaEBi013154; Fri, 23 Feb 2024 16:36:14 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 1022C46052; Fri, 23 Feb 2024 16:36:14 +0000 (GMT)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 03F4346051; Fri, 23 Feb 2024 16:36:14 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS; Fri, 23 Feb 2024 16:36:13 +0000 (GMT)
Received: from LAPTOPK7AS653V ([85.255.234.134]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.7/8.14.7) with ESMTP id 41NGaB4p027038 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 23 Feb 2024 16:36:12 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Xuewei Wang' <wangxuewei1@ruijie.com.cn>
Cc: 'cats' <cats@ietf.org>, cats-chairs@ietf.org
References: <0ed501da6342$75cb73b0$61625b10$@olddog.co.uk> <29e540a2652de0cf2773fffcb38edf59fc548f6e.a094df9c.0678.4d68.9ec0.2f3cf0a121ff@feishu.cn>
In-Reply-To: <29e540a2652de0cf2773fffcb38edf59fc548f6e.a094df9c.0678.4d68.9ec0.2f3cf0a121ff@feishu.cn>
Date: Fri, 23 Feb 2024 16:36:10 -0000
Organization: Old Dog Consulting
Message-ID: <01a101da6676$69f21da0$3dd658e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A2_01DA6676.69F30800"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJ0gjBN3nxeIys8btyH/3SZZ6e0jQIbDm1rr9MLUkA=
Content-Language: en-gb
X-Originating-IP: 85.255.234.134
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=r+DuFkK7eJm0Q7V8EUZzi ccgAcwFEw1a7BkXa+VR3os=; b=WMBHPoCSG+D4Bn9QwjVVysEE8tERWEQnEn0IJ Ac8JMg15tqgLULYbIwZi/J3GetKmvSJmx/L94ptlIq66QDFuwK2V8dyzKK8wOczI uXeK6tJUna5rOsxLtKP0NJ7WIA017YIduPPZ4gsE7nYz6DdQFurnTNZcbrtY5H3F qV7affL96RiEmlWb+yXngyfZm0p9sOEiZPj/A38ywplmR8VpmgTsP6C7NP6tBseW 9O/BmuomltyhaZ+Pt7pHXFsH9QdNyViNgmJMbWUlMqI7i7gPKtVO6iYxn0jTL9rZ d95b4GyVAGojs8qrzYk+iWXTEK3yDo0e6o9DWq4CAw3Zd93Bw==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-28208.007
X-TM-AS-Result: No--27.903-10.0-31-10
X-imss-scan-details: No--27.903-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-28208.007
X-TMASE-Result: 10--27.902900-10.000000
X-TMASE-MatchedRID: hFbMlnd2lLM0QDP3j4T8uWCuN6HSW3agjhXy0Khej9LB0/7xhd4ByT+B /tp8itBTWeCjURnD4jRWzc5oODw5Eedv4xjwreWfs1RWeqLGIw6If3m0sUfx5wKepbH0zN4ZUoK pGo+HpccXdudYOKS8Ojt4gerJs3fVefTHqxypj9OjpzeDGKpgq95x7RpGJf1aKOG9KSvT2EC5qR lKWyqkjxplbnRIZ6aEGqK1GiwImx7ugYf75qB+MgsbkbSHcUnIlVHM/F6YkvROGffsUU/kDbwxq SK0GSPRd1DzNSnJPK9zJBCq1HFAR/x15EY4PiFAGY382d/hoI04ZNXh8UPrINq1p6neH75UcFfb HRo0WfeGdV1o2FvDHAauzS8gDMTfbK+bZCQFLzbl5keOTGAi+RlxrtI3TxRk2B5g90ltSFYiw3w 8aLdNLJim4buSmgpHIHqwoDWL8rRkw/voluFJgLIoFV0gUSQDE7sLdRVaGmffVqwz+CynaalVRH RK9i1K9TvadhXG9g3gPqVbzYllURvzEjY4Pdnt7IPLxXyVNZRkGI+vgRTxMFGk5uRH0MzCR6RHd VK85hXaOBWaEqUPGKofXa4f40fCVCHlgT24MfuDPJ3sg13mJ5pg8IOIewHQKQNhMboqZlrNiXmD PBs02ffnaHkTI99QHpzILIkWa6f770KfKft/uK4QAeQvIGeq7kIYxuaO6ZTBIlxtEe6gxytwWBG VoxmpriuZAgOgHpJGdQAWn8CmCAin6k0GuLUFvogoaLbF9Igvj6wHfIGxyQv/9UzFeXITLhJJjz GgNQSFoZ+lOCN1FBmt4kFBM7XWJ6ljrnXGyZWhiBk878JnAJ4CIKY/Hg3AaZGo0EeYG97UHQeTV DUrIj166Jh7ejx4h9eWnlL1x8DiRhduhvElsvJT+hf62k2YIbZSWXZZ520=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/7kf1s-L2RFUCQvk8wBXOlr2Ne64>
Subject: Re: [Cats] Regarding IPR on draft-ldbc-cats-framework
X-BeenThere: cats@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Computing-Aware Traffic Steering \(CATS\)" <cats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cats>, <mailto:cats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cats/>
List-Post: <mailto:cats@ietf.org>
List-Help: <mailto:cats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cats>, <mailto:cats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Feb 2024 16:36:23 -0000

Thanks for the response, Xuewei, and for reporting the current situation.

 

I understand that it is not always simple to determine whether IPR applies to a draft and what license terms should be used.

 

That said, I need to remind you that when the draft was posted in March last year (https://datatracker.ietf.org/doc/draft-ldbc-cats-framework/00/) your name was on the front page, and the draft contained the text:

   This Internet-Draft is submitted in full conformance with the

   provisions of BCP 78 and BCP 79.

BCP 79 is currently RFC 8179 (https://www.rfc-editor.org/rfc/rfc8179.txt) and covers IPR. Section 3.3 (Obligations on Participants) says:

   each Participant
   that is a Contributor makes the following representations to the
   IETF:
 
   A. Such Contributor represents that he or she has made or will
      promptly make all disclosures required by Section 5.1.1 of this
      document.

 

So, there is a requirement on you, personally, to try to move this along as quickly as possible.

 

I appreciate that it is complex and you need to drive the company’s legal department, but I hope you can work this out quickly.

 

Best,

Adrian

 

From: Xuewei Wang <wangxuewei1@ruijie.com.cn> 
Sent: 23 February 2024 03:13
To: adrian@olddog.co.uk
Cc: 'Chengli (Cheng Li)' <chengli13@huawei.com>; 'Zongpeng Du' <duzongpeng@chinamobile.com>; mohamed.boucadair@orange.com; luismiguel.contrerasmurillo@telefonica.com; je_drake@yahoo.com; christian.jacquenet@orange.com; xswang@fiberhome.com; linchangwang.04414@h3c.com; 'Shihang(Vincent)' <shihang9@huawei.com>; luigi.iannone@huawei.com; dirk.trossen@huawei.com; liyizhou@huawei.com; yaohuijuan@chinamobile.com; hayabusagsm@gmail.com; huang.guangping@zte.com.cn; 'cats' <cats@ietf.org>; cats-chairs@ietf.org
Subject: Re: Regarding IPR on draft-ldbc-cats-framework

 

Hi Adrian, all,

Sorry for the late reply. There is IPR, because our company has less experience in IPR declarations, and the declarations would be completed as soon as possible after our detailed analysis and comparison.

From: "Adrian Farrel"< <mailto:adrian@olddog.co.uk> adrian@olddog.co.uk>

Date: Mon, Feb 19, 2024, 22:48

Subject: Regarding IPR on draft-ldbc-cats-framework

To: "'Chengli (Cheng Li)'"< <mailto:chengli13@huawei.com> chengli13@huawei.com>, "'Zongpeng Du'"< <mailto:duzongpeng@chinamobile.com> duzongpeng@chinamobile.com>, < <mailto:mohamed.boucadair@orange.com> mohamed.boucadair@orange.com>, < <mailto:luismiguel.contrerasmurillo@telefonica.com> luismiguel.contrerasmurillo@telefonica.com>, < <mailto:je_drake@yahoo.com> je_drake@yahoo.com>, < <mailto:christian.jacquenet@orange.com> christian.jacquenet@orange.com>, < <mailto:wangxuewei1@ruijie.com.cn> wangxuewei1@ruijie.com.cn>, < <mailto:xswang@fiberhome.com> xswang@fiberhome.com>, < <mailto:linchangwang.04414@h3c.com> linchangwang.04414@h3c.com>, "'Shihang(Vincent)'"< <mailto:shihang9@huawei.com> shihang9@huawei.com>, < <mailto:luigi.iannone@huawei.com> luigi.iannone@huawei.com>, < <mailto:dirk.trossen@huawei.com> dirk.trossen@huawei.com>, < <mailto:liyizhou@huawei.com> liyizhou@huawei.com>, < <mailto:yaohuijuan@chinamobile.com> yaohuijuan@chinamobile.com>, < <mailto:hayabusagsm@gmail.com> hayabusagsm@gmail.com>, < <mailto:huang.guangping@zte.com.cn> huang.guangping@zte.com.cn>

Cc: "'cats'"< <mailto:cats@ietf.org> cats@ietf.org>, < <mailto:cats-chairs@ietf.org> cats-chairs@ietf.org>

Authors and Contributors of draft-ldbc-cats-framework, CATS WG, If you are listed as a document author or contributor please answer the above by responding to this email copying the CATS mailing list regardless of whether or not you are aware of any IPR that needs to be disclosed. This document will not advance to the next stage until a response has been received from each author and contributor. NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES. In preparation for WG Adoption of draft-ldbc-cats-framework, please state whether you are aware of any IPR that applies to 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 your answer is "yes", has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3669, 5378 and 8179 for more details)? Please answer either: "Yes, the IPR has been disclosed in compliance with IETF IPR rules" or "No, the IPR has not been disclosed" If your answer here is "no", please provide any additional details you think appropriate including what action you have taken to ensure that the IPR is disclosed in a timely fashion. If you are on the WG email list or attend WG meetings but are not listed as an author or contributor, we remind you of your obligations under the IETF IPR rules which encourages you to notify the IETF if you are aware of IPR of others on an IETF contribution, or to refrain from participating in any contribution or discussion related to your undisclosed IPR. For more information, please see https://www.ietf.org/standards/ipr/ Thanks, Adrian (as co-chair)