Re: [Teas] Regarding IPR on draft-ietf-teas-pcecc-use-cases-09

Quintin Zhao <qzhao@ethericnetworks.com> Mon, 06 June 2022 16:57 UTC

Return-Path: <qzhao@ethericnetworks.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC1B2C157B54 for <teas@ietfa.amsl.com>; Mon, 6 Jun 2022 09:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level:
X-Spam-Status: No, score=-1.844 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, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_BLOCKED=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ethericnetworks.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 AOw_hUcNBCXx for <teas@ietfa.amsl.com>; Mon, 6 Jun 2022 09:57:46 -0700 (PDT)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 1B684C157B4B for <teas@ietf.org>; Mon, 6 Jun 2022 09:57:46 -0700 (PDT)
Received: by mail-yb1-xb31.google.com with SMTP id f34so26743227ybj.6 for <teas@ietf.org>; Mon, 06 Jun 2022 09:57:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ethericnetworks.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=m4SMqpK1ddHOANyoaZYTCSzXtKIflV8gFZYyOXyep3I=; b=VmmyiGpgvmH8mPBeqNKIAZzQz/rKzf9x0qix/ZtDV/xR++uvKQ2l6tGkRVCBHsRujn v6sfB641jU0jLWXPis64kNbmeMDhzrZhpOkoh+XS+WD98QSpvuO4MxBZInsG621p9CTN pvS/huL/PdFPOnFZPjC2ZirboEspmMkn+Fqq8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=m4SMqpK1ddHOANyoaZYTCSzXtKIflV8gFZYyOXyep3I=; b=hJTPkhIk2+hJvsWp0+sY828yrL1opu3Zf+uHA5qzHkfwXQ0ueGKaz9g9uJYgZoJux+ zOy2oeFdTIyeHeIqsJcaikLRiojm2pz6L9V7McsGTuO/SC0x7MXHlWsLQD0ukQSbsdnN FUyVcqfMoo4lkhOljAWM3G9qwu2zUACYMtfodL01fR6DFqNrfvteEmHIFUQ2eCADRE7T eaW7mQNwS5ki5aCuBKVNfNmojBk7LVEUcqDDWDYAs+6jFcUueO7uzX0LQ5HIhzP/sT55 twQsm8pyxGxQa4J08KIFRps0W+g7jxj2EFt7uxWpsIzcLuFfcSoUbfX2jW4LHoAW5Avq BXMw==
X-Gm-Message-State: AOAM5330ZZojzqb2Xre26wZbT40XUoszxDsTsW7JL/bPONzoBg1Vnioc Ob3kDreQj9CCJDoO7OVwdPpntIOWnM83LCAd/hP26yIYUceQN5cyGTRmIEkljxayKyMg2oDIhjm 8W0WxU/ibFdA=
X-Google-Smtp-Source: ABdhPJxcFCR5iXC6UBqHYKsfhOBJ7sPIrZPyLsYHrAcBr4NBJKPSFGvxNkhcDHJz1y9Y4moFxDhd+gfhKXIV1psSqhQ=
X-Received: by 2002:a25:8a81:0:b0:65b:9268:2760 with SMTP id h1-20020a258a81000000b0065b92682760mr26347465ybl.119.1654534664611; Mon, 06 Jun 2022 09:57:44 -0700 (PDT)
MIME-Version: 1.0
References: <CA+YzgTvDZeAxJT+kASDBBZDuPGjft4=LGrv9hxx7hu2GSsc8uw@mail.gmail.com>
In-Reply-To: <CA+YzgTvDZeAxJT+kASDBBZDuPGjft4=LGrv9hxx7hu2GSsc8uw@mail.gmail.com>
From: Quintin Zhao <qzhao@ethericnetworks.com>
Date: Mon, 06 Jun 2022 09:57:33 -0700
Message-ID: <CAED7FTkyyBCppc246RTtei7AVP5U7NvStA_JLTjPPTF6rZo_bg@mail.gmail.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Cc: Lizhenbin <lizhenbin@huawei.com>, Dhruv Dhody <dhruv.ietf@gmail.com>, kinghe@tencent.com, bhassanov@yahoo.com, Luyuan Fang <luyuanf@gmail.com>, chaozhou_us <chaozhou_us@yahoo.com>, Boris.zhang@telus.com, arachitskiy@mts.by, anton.gulida@life.com.by, TEAS WG <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f404cb05e0ca5e30"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Uk3hMVxSBVzz77AW3Mkh0AH85no>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-pcecc-use-cases-09
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2022 16:57:49 -0000

Hi All,



Yes, I'm aware of IPR that applies to this draft.

Yes, the IPR has been disclosed in compliance with IETF IPR rules.



Best Regards,

Quintin

On Fri, May 6, 2022 at 10:11 AM Vishnu Pavan Beeram <vishnupavan@gmail.com>
wrote:

> Authors, Contributors, WG,
>
> As part of WG Last Call:
>
> 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 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.
>
> NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.
>
> 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 the RFCs listed above
> and
> http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
>
> Thank you,
> Pavan and Lou
>
> PS Please include all listed in the headers of this message in your
> response.
>

--