IETF Logo Mail Archive

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

Gyan Mishra <hayabusagsm@gmail.com> Fri, 23 February 2024 03:54 UTC

Return-Path: <hayabusagsm@gmail.com>
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 07ABCC17C8B3; Thu, 22 Feb 2024 19:54:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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=gmail.com
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 F6u0yVC8K6ad; Thu, 22 Feb 2024 19:54:21 -0800 (PST)
Received: from mail-oo1-xc2e.google.com (mail-oo1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 150FDC17C8A2; Thu, 22 Feb 2024 19:54:21 -0800 (PST)
Received: by mail-oo1-xc2e.google.com with SMTP id 006d021491bc7-5a00b5e78adso276759eaf.0; Thu, 22 Feb 2024 19:54:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708660460; x=1709265260; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xS1Tu4Sh55P//0hK7gU7G+A2l7WNQpMPxCM6sLD6Dc0=; b=UXGpOyh/kT5YTi82kXUfaJ+rxCml+1CT9iZD9Natjtg15ljprbTRVX86OazgZ1DCoY Uhfjelk/rGJtisew7PHGGbFSKBQp1zW6b57oBWDJizchczNhRvsO/MY357O2PfUJdJCV JjZmYUWQwn8vlXPi+aclMHo41VM5Z+3ESq2L9TC4j8xX8G7Ohi/0zcBMMghiqhSkLNQW HehtmE0blJkHZ6ULiQBj8kXVUJiPFE2Et+B/OuVqM2aNreXc8mj4uqmPNQsJ+swqg3gj L7pt9DPl6Ias20SxpI2jK9z47LabGl7o4ByWATqPcHftey/r6cn8J0nLLRh8mDTouxKt +xYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708660460; x=1709265260; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xS1Tu4Sh55P//0hK7gU7G+A2l7WNQpMPxCM6sLD6Dc0=; b=hyLErjShff3o/ilR7Q4Y9zctzCO6qi9pDbqQwKCCrb/sFODZjXsvx3SZatNlxEqm/3 pUDBikzdWzq1V6YvWisOJ2KQ71nS1NnsBQ1aTFqLuy4hyTu+YitXk9v9T62INaxPjgpJ ZVWGPvNJedUjYiPkQ6gp90rrurfNvWBQILyZ+ctVVt5gdBlsOSZ6qvngG4NXZsbMunKY U3xG9iT218il/tI6b5fxmlxwhw796wwqv4Cz0fwEs6ykBaEXpWMMckBVjijaTlqhziRs OUDNqS/IDz01X45St/oECZnqOkqHwGTS+gcOET4Uvr3HG+r9qTjQyeshN1lXCN33pW07 ZveA==
X-Forwarded-Encrypted: i=1; AJvYcCU5L3Q2Q8vP2RaJmeCxte+BzIV+YuZc0rr8st2dv5ghNOcERqntB4KoAIEIpPQW1U5m5ObwT1/Cx9iXR6MfgnW0WEwa3BIFukG7zHaiR0g0XOndbQ==
X-Gm-Message-State: AOJu0YyUyTc9oa+gDVSnxuRFHt1jJJidyojjk8IfWroZfsk6+nqbtNEL DHDzfXNprjbovFjCFXIJO+5TFnuC3P5oYcPH6+KCLs9QCprTbx463F8SHSktN7q6zzR4zBtO7PQ /N8KjmennzHubEZlbi833u1829h0=
X-Google-Smtp-Source: AGHT+IEwFyc2bz853I0WQC14wkzza4DDHpCTgPENsOookIxuWsTQV0LqtnBx5KXxIjckxttQg95dxh8TfSh3wEDadsw=
X-Received: by 2002:a05:6358:4a7:b0:17b:62a1:c35b with SMTP id x39-20020a05635804a700b0017b62a1c35bmr887232rwi.6.1708660459819; Thu, 22 Feb 2024 19:54:19 -0800 (PST)
MIME-Version: 1.0
References: <0ed501da6342$75cb73b0$61625b10$@olddog.co.uk>
In-Reply-To: <0ed501da6342$75cb73b0$61625b10$@olddog.co.uk>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Thu, 22 Feb 2024 22:54:08 -0500
Message-ID: <CABNhwV09k8Qrm+GZpsk1yZ6-+Zu5qFx+wRDKwvLrnScaPgN0Mg@mail.gmail.com>
To: adrian@olddog.co.uk
Cc: "Chengli (Cheng Li)" <chengli13@huawei.com>, "Shihang(Vincent)" <shihang9@huawei.com>, Zongpeng Du <duzongpeng@chinamobile.com>, cats <cats@ietf.org>, cats-chairs@ietf.org, christian.jacquenet@orange.com, dirk.trossen@huawei.com, huang.guangping@zte.com.cn, je_drake@yahoo.com, linchangwang.04414@h3c.com, liyizhou@huawei.com, luigi.iannone@huawei.com, luismiguel.contrerasmurillo@telefonica.com, mohamed.boucadair@orange.com, wangxuewei1@ruijie.com.cn, xswang@fiberhome.com, yaohuijuan@chinamobile.com
Content-Type: multipart/alternative; boundary="000000000000bfd79406120483cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/QLYlnsR3vD6n2lHZ_FzwFfLEt4M>
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 03:54:25 -0000

I am not aware of any undisclosed IPRs.

Thanks

Gyan

On Mon, Feb 19, 2024 at 9:47 AM Adrian Farrel <adrian@olddog.co.uk> wrote:

> 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)
>
> --

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*

v2.23.0 | Report a Bug | By Email