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

Quintin Zhao <qzhao@ethericnetworks.com> Mon, 09 May 2022 17:22 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 EB298C157B3A for <teas@ietfa.amsl.com>; Mon, 9 May 2022 10:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 eKotOUOn-hbi for <teas@ietfa.amsl.com>; Mon, 9 May 2022 10:22:03 -0700 (PDT)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (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 C363CC147921 for <teas@ietf.org>; Mon, 9 May 2022 10:22:03 -0700 (PDT)
Received: by mail-yb1-xb33.google.com with SMTP id x17so5677076ybj.3 for <teas@ietf.org>; Mon, 09 May 2022 10:22:03 -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=KAhZHz+PZnUywaHYZBq0wqlXwOMoYzrokDtfKuL2gNA=; b=jZeJzGfK9FVFrwKhnGYGc6CZVxC1qsSCAscD7OxtMqDikAqYkudLUcWsS4vomGAo1D MCoSL/Q3Xd9EwGgEgCBUKsMqEIs0Pdx12PW5C5oLSbXNcDAIUsMVJiJnRIVdTso6z7OQ N3YwbpA0QFUUv6nSrkt88s9G8ynO+Wgh3Cn1M=
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=KAhZHz+PZnUywaHYZBq0wqlXwOMoYzrokDtfKuL2gNA=; b=2WDy4alun6tUSp6e+rJkA3WvZDAOu00p/9ePsfF7ThS2hKFKjZAVD352KAcB18gYRN ZjtHRnpCBlEObIXFmFgyQqN0OJR9pGMwjVT2JnIbVhxDPA3g7XCEeC/nsl5zOKqE8I0Q Ha2pvtPAkBDDtrh0U0FIJ0skuxWVY48uwD52HG6WPI5OwfZnmpwCoPaDpHI9FfTogr5H fxD0pSYLA24x8h2ZBmxDb06no7k9LXetqbSEfwShOqANYDoYWsSSTlAiIo8zuv5UkG9w rhLDirGgsL35kis//Y6Q4jbcSOzoY5nBBTdM1R1p7yGycG/Xuf2vZSKW0HLEKcY3hpbz Zb0A==
X-Gm-Message-State: AOAM532F/+jGvExvfCgsOqG1/+58NeVWzqOBTGyZbgj41N2A8QS0mw01 Lmj0W7LInMrZsb/zFhGAmf2TZ6LfM9kmU4NeRXDOhTW/pqkL7sxJY/slfr+Kcp6eM/jvyg4atbR 7ifW370ZZvN8=
X-Google-Smtp-Source: ABdhPJx6e4Hy/YcxrThIidxVquV55gNdIxGduAoLLSV3JgksKl/T6zxH6AGPH4jw9qkoTRoGegW3UYoqEj0NkJNQ+BQ=
X-Received: by 2002:a5b:606:0:b0:648:6a16:6423 with SMTP id d6-20020a5b0606000000b006486a166423mr14167107ybq.147.1652116921482; Mon, 09 May 2022 10:22:01 -0700 (PDT)
MIME-Version: 1.0
References: <CA+YzgTvDZeAxJT+kASDBBZDuPGjft4=LGrv9hxx7hu2GSsc8uw@mail.gmail.com> <79668e2aeaa5477e966a36bc01cb98e3@huawei.com>
In-Reply-To: <79668e2aeaa5477e966a36bc01cb98e3@huawei.com>
From: Quintin Zhao <qzhao@ethericnetworks.com>
Date: Mon, 09 May 2022 10:20:57 -0700
Message-ID: <CAED7FT=Pk+-yO3HY9WEn8f+Pet5yBBOWFP6Cxevz_Xrh48zK+Q@mail.gmail.com>
To: teas-chairs@ietf.org
Cc: Vishnu Pavan Beeram <vishnupavan@gmail.com>, Dhruv Dhody <dhruv.ietf@gmail.com>, "kinghe@tencent.com" <kinghe@tencent.com>, "bhassanov@yahoo.com" <bhassanov@yahoo.com>, Luyuan Fang <luyuanf@gmail.com>, "chaozhou_us@yahoo.com" <chaozhou_us@yahoo.com>, "Boris.zhang@telus.com" <Boris.zhang@telus.com>, "arachitskiy@mts.by" <arachitskiy@mts.by>, "anton.gulida@life.com.by" <anton.gulida@life.com.by>, TEAS WG <teas@ietf.org>, Lizhenbin <lizhenbin@huawei.com>
Content-Type: multipart/alternative; boundary="0000000000003b9b1905de977203"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/HCxll9py_n1d4Xae7QAnEYsaLVE>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-pcecc-use-cases-09
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.34
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, 09 May 2022 17:22:08 -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 Mon, May 9, 2022 at 8:59 AM Lizhenbin <lizhenbin@huawei.com> wrote:

> 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,
>
> Zhenbin (Robin)
>
>
>
>
>
>
>
> *From:* Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com]
> *Sent:* Saturday, May 7, 2022 1:12 AM
> *To:* Lizhenbin <lizhenbin@huawei.com>; Dhruv Dhody <dhruv.ietf@gmail.com>;
> qzhao@ethericnetworks.com; kinghe@tencent.com; bhassanov@yahoo.com;
> Luyuan Fang <luyuanf@gmail.com>; chaozhou_us@yahoo.com;
> Boris.zhang@telus.com; arachitskiy@mts.by; anton.gulida@life.com.by
> *Cc:* TEAS WG <teas@ietf.org>; TEAS WG Chairs <teas-chairs@ietf.org>
> *Subject:* Regarding IPR on draft-ietf-teas-pcecc-use-cases-09
>
>
>
> 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.
>

--