From nobody Sun Jun 25 21:48:29 2023 Return-Path: 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 5082DC15107B; Sun, 25 Jun 2023 21:48:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.002 X-Spam-Level: X-Spam-Status: No, score=-7.002 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ED40YS6UyYSk; Sun, 25 Jun 2023 21:48:27 -0700 (PDT) Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 9D3DBC151072; Sun, 25 Jun 2023 21:48:27 -0700 (PDT) Received: by mail-ej1-x629.google.com with SMTP id a640c23a62f3a-991e69499d1so3468366b.2; Sun, 25 Jun 2023 21:48:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687754905; x=1690346905; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=VgP2LvNb2gnBUKV4tbHb0XK7RpwT8dd+x2FjbtFN6f8=; b=Nef620I6tx8Uq9j7HGsUsbCJXF4Rn3Pbinq1w7y0XT6Z2gj2HvapswJ7KM35UUTOP5 e6Zoqr8a2GTeNiLnbMyjh9r5Nj35GUNLabGUIC0OOsEy/4IP+e2F/wiK070gVVcVq2lo PKnP+aQk6tSsIc8TOTuLi0ORd06llCRM+ytt1tVv7SBKItx01AlDM4NA/E02eJKcSIGI fd+HmIXvx0+J6YvVPHI2Xt941o7Z3nyty9GH5LHZDcf+FkrWYcnLZ0IbZHxZ3H8F7kgY RvP3grKAYTTmUB+UgMJlWCdyiw2VO9tHWKD1bpzeRZ/a229KtLQaP/nLbGqAZNK+Ybtl Taxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687754905; x=1690346905; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=VgP2LvNb2gnBUKV4tbHb0XK7RpwT8dd+x2FjbtFN6f8=; b=GgbignEW0PTFfOeG0DYSnjx1RLe2hIBwSp/d3rZL0mdtnea3WcFsJbufTWlMR85wcL l2BcbhDM4HMPrCY5asgUWVtUrs4brnEs6nPmqfYsDAZCUSjParbGf7JtoZBMPFRGn/xu GAeFK6PIU5rzcVxJX/H0R0Q5k00CUpBRc++Z/T4Eggfxoa5BgFjjLK8xz0puRaruCVFo A1UmsSno3oDvWTwxQdcPV8LGgMV08H3OSgIQdgVU2B9P+A4TGTfpX6sm5DUCU+JQ9DDA ASZpvZYEhN5QN6c/n55MroQS/e7/XoZTMsUA9Nx6VKrVIzOhpZiHRm4pVZNxqRWgcZE+ 0PtA== X-Gm-Message-State: AC+VfDyw0zIyyLQSzgckMyC9G3ZjyqJ29CttM4LZxFgdsAEXqyGIT//o pfqwpSq678VV/LL9S6WS7ReZbMZtmDAtlvpxPIc= X-Google-Smtp-Source: ACHHUZ4gwk+753eXE9fQ798rvwKCCi5CQ+irM5OJspiwkLfdgZfzp893hpTkql47WZQGfa5DhvTKYdHI75wVa8c8JxQ= X-Received: by 2002:a17:906:7945:b0:982:781e:ba13 with SMTP id l5-20020a170906794500b00982781eba13mr26604454ejo.39.1687754905457; Sun, 25 Jun 2023 21:48:25 -0700 (PDT) MIME-Version: 1.0 From: Vishnu Pavan Beeram Date: Mon, 26 Jun 2023 10:18:14 +0530 Message-ID: To: LUIS MIGUEL CONTRERAS MURILLO , "Rokui, Reza" , Jeff Tantsura , "Wubo (lana)" , Xufeng Liu , Dhruv Dhody , "Belotti, Sergio (Nokia - IT)" Cc: TEAS WG , TEAS WG Chairs Content-Type: multipart/alternative; boundary="0000000000009b9a7a05ff010f7b" Archived-At: Subject: [Teas] Regarding IPR on draft-contreras-teas-slice-controller-models-05 X-BeenThere: teas@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Traffic Engineering Architecture and Signaling working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2023 04:48:28 -0000 --0000000000009b9a7a05ff010f7b Content-Type: text/plain; charset="UTF-8" Authors, Contributors, WG, As part of WG Adoption: 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, Lou and Oscar PS Please include all listed in the headers of this message in your response. --0000000000009b9a7a05ff010f7b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Authors, Contributors, WG,

As part of WG Adoption:<= br>
Are you aware of any=C2=A0IPR=C2=A0t= hat applies to drafts identified above?

Please state either:

= "No, I'm not aware of any=C2=A0IPR= =C2=A0that applies to this draft"
or
"Yes, I'm aware of= =C2=A0IPR=C2=A0that applies to this draft&q= uot;

If so, has this=C2=A0IPR=C2=A0b= een disclosed in compliance with IETF=C2=A0IPR=C2=A0rules
(see RFCs 3669, 5378 and 8179 for more details)?

I= f yes to the above, please state either:

"Yes, the=C2=A0IPR=C2=A0has been disclosed in compliance with IET= F=C2=A0IPR=C2=A0rules"
or
"= No, the=C2=A0IPR=C2=A0has not been disclose= d"

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 wh= ether or not you are
aware of any relevant=C2=A0IPR. This document will not advance to the next
stage until a re= sponse has been received from each author.

NOTE: THIS APPLIES TO ALL= OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are=C2=A0on=C2=A0the WG email list or attend WG meetings = but are not listed
as an author or contributor, we remind you of your ob= ligations under
the IETF=C2=A0IPR=C2=A0r= ules which encourages you to notify the IETF if you are
aware of=C2=A0IPR=C2=A0of others=C2=A0on=C2=A0an IETF contribution, or to refrain from
participatin= g in any contribution or discussion related to your
undisclosed=C2=A0IPR. For more information, please see the RFCs= listed above
and
http://t= rac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Th= ank you,
Pavan, Lou and Oscar

PS Please include all listed in the= headers of this message in your
response.

--0000000000009b9a7a05ff010f7b--