Re: [Teas] Regarding IPR on draft-ietf-teas-rfc3272bis-16

Xufeng Liu <xufeng.liu.ietf@gmail.com> Fri, 13 May 2022 00:56 UTC

Return-Path: <xufeng.liu.ietf@gmail.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 D6A01C15E405; Thu, 12 May 2022 17:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, HTML_OBFUSCATE_10_20=0.093, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 LLcOGwgQFf9a; Thu, 12 May 2022 17:56:46 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 3BD6EC15E400; Thu, 12 May 2022 17:56:46 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id bx33so8482581ljb.12; Thu, 12 May 2022 17:56:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LqDPoiqk1jz30VwtuFH6LAw8VItDp/OLYP50epB0eBI=; b=XN5P8S+zIjWXpjIwjva/EZm4W0rf0mQbuHSQNX2+yEdRCuTK6A3bm9s0ynk+vhfVAS iO+dndqlgzZFcNBMBNOoBr495aJ+FvwPT08CXy8iuK1rqtj5Vf7FiHeSQ31ZeuvRapqb JnsNLzX2ovXbNm6djJLNyoG1c/PXlLMZaEW4iXj9g39AxIx5ndDOyoIHUrXDWuz/Q7NF S1lJdq2Tv/vFKrXaopFmM3s9mEMGTzL7rzUB4S2tfRui4pxFu00Y8fBQFo6emcPTijyy 0mIhf9r5ZT9EJilfAyA06o8q1Ye7bPUy4ynqgVf09GaIfVzT6LMKJRdhSeVuV77Awn46 KZ8A==
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=LqDPoiqk1jz30VwtuFH6LAw8VItDp/OLYP50epB0eBI=; b=M2S11tQfzjkq7WpO9IbPOpjfC2xa5uf/As18+Z9XQUh3OdtODU0qbWa18e78HUPU++ ypimlndDzXoV8bubndsZ7gjddA/d9raQVRgaFjgZmqUcEmC5DmDBF9LXAWJi+HJPLZqk qV6G+RdgoL2ZiYOq+F8G/zlRIXBdeMKndWe6OijB7otPJhYnUfDtlCvDrYxFZvoD1OnV 1aOfId2a3H+qs7KWZtl/APl0UJVdpxNnSVDjunh4B0E5o/htkB6wsngMSVuev07bcLh6 9CjE4G0xxabTGhmJsygbd0vfFA+ffajU6jVgT3e5fB2VCcTfhW3eJHeZByn0anARToQO KJtA==
X-Gm-Message-State: AOAM530lMD7lE2JiQxjTInRFM+0SW/z7Pz/ssnPRph+6SyBYe/l9WXSZ YeT/wJZdkTWMktHua9VAS0askK+HqUBgZ9jbdDc=
X-Google-Smtp-Source: ABdhPJxe32UDwh3lJVXA4eyK4gYO7W29c+LYM4eB+PUAylWiRHr+mnXAwIuT3Y4wNDAoS5dhcImdn0AdFNd2I/fDi+A=
X-Received: by 2002:a2e:5149:0:b0:24f:1a3b:b774 with SMTP id b9-20020a2e5149000000b0024f1a3bb774mr1591361lje.279.1652403404106; Thu, 12 May 2022 17:56:44 -0700 (PDT)
MIME-Version: 1.0
References: <CA+YzgTtw62uVTzPpV-HbfzPWMPHHj76zsD5s6XwtF615tLkeKw@mail.gmail.com>
In-Reply-To: <CA+YzgTtw62uVTzPpV-HbfzPWMPHHj76zsD5s6XwtF615tLkeKw@mail.gmail.com>
From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
Date: Thu, 12 May 2022 20:56:32 -0400
Message-ID: <CAEz6PPR3D4PA0VjoCxz8rOgK71X5GzuaxuhhTCUKEUBg8TjMxA@mail.gmail.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>, Gert Grammel <ggrammel@juniper.net>, Loa Andersson <loa@pi.nu>, Lou Berger <lberger@labn.net>, Jeff Tantsura <jefftant.ietf@gmail.com>, Daniel King <daniel@olddog.co.uk>, bhassanov@yandex-team.ru, Kiran Makhijani <kiranm@futurewei.com>, Dhruv Dhody <dhruv.ietf@gmail.com>, Med Boucadair <mohamed.boucadair@orange.com>, TEAS WG <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ed6d7105deda258a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/5ZpVHMvgFEWiy5oLeM_vknpjfNE>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-rfc3272bis-16
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: Fri, 13 May 2022 00:56:46 -0000

No, I'm not aware of any IPR that applies to this draft.


Thanks,

- Xufeng


On Fri, May 6, 2022 at 1:02 PM 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 (Co-Chair & doc Shepherd)
>
> PS: Please include all listed in the headers of this message in your
> response.
>
>