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 9BC3E3A0E0D for ; Wed, 1 Jul 2020 14:51:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.648 X-Spam-Level: X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OqIEd-EqCs3q for ; Wed, 1 Jul 2020 14:51:38 -0700 (PDT) Received: from mail-il1-f194.google.com (mail-il1-f194.google.com [209.85.166.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5EA73A0E0F for ; Wed, 1 Jul 2020 14:51:38 -0700 (PDT) Received: by mail-il1-f194.google.com with SMTP id x9so22463409ila.3 for ; Wed, 01 Jul 2020 14:51:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Cz3GNExLbuikpsOGHfqWtCKRBsiEb7e/LjMImEvsQWE=; b=LWQLsLmseoujwMTj17wrkTw2wjEuNjuhAnDHvvHh/IwvV9NfcC/dJ/PPhi4YxBf6ZQ VZXwd5t8ld6t66yth7Vs40Dnet/cMjNZKuZMNMReXOuXbMiKOHM8D6TXJ4YH9HPS7Ds3 5QkI/nzeSLyDujdGkd72dq4KovqvJMqX5yrL6Qwf6m6+GV9onRcBxsMyw7N9d26PnVN/ jD3jBfZ38NTk6A/szLjK2rPi6v6XxZqlV3hTp9k41mFvxtEFR6NcZPzufvhhA1wum2Ce I00ZAtrpciBjx/aiyyik5z0pkOBYS+civmJIsO2wO5GsOSULlcpipbNRsrPUWAjHPTyr DoRA== X-Gm-Message-State: AOAM530NN9PhBn3jvf3HuGGWtZTBC/zc4+jcBEaSXyl9PTuWkmFdVtK4 qe1DnNyv9RgT3IhudWvHj9/2ZmNrGVSN7FRJAc1ohKgx X-Google-Smtp-Source: ABdhPJzTBIaB38qvmA88d6Vd5n4fI+/5tPGRUCm2Yw3hs6EUc7KF3GPlPxlEX0NcQCGBaXcnqolIRMKM6faolCgUK+M= X-Received: by 2002:a05:6e02:592:: with SMTP id c18mr9799260ils.80.1593640297453; Wed, 01 Jul 2020 14:51:37 -0700 (PDT) MIME-Version: 1.0 References: <95d3dcb4-a39b-468b-921f-b4a16bd09060@Spark> In-Reply-To: <95d3dcb4-a39b-468b-921f-b4a16bd09060@Spark> From: Daniel King Date: Wed, 1 Jul 2020 22:52:50 +0100 Message-ID: To: teas@ietf.org, TEAS WG Chairs Cc: Peruzzini Fabio , "BOUQUIER, JEAN-FRANCOIS, Vodafone Spain" , Italo Busi , Daniele Ceccarelli , "Belotti, Sergio (Nokia - IT)" , "Gabriele Maria Galimberti (ggalimbe)" , Zheng Yanlei , Anton Snitser , Costa Pereira Correia Washington , "Scharf, Michael" , Young Lee , Vishnu Pavan Beeram , jefftant.ietf@gmail.com Content-Type: multipart/alternative; boundary="000000000000d476ca05a9684b79" Archived-At: Subject: Re: [Teas] Regarding IPR on draft-peru-teas-actn-poi-applicability-05 X-BeenThere: teas@ietf.org X-Mailman-Version: 2.1.29 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: Wed, 01 Jul 2020 21:51:41 -0000 --000000000000d476ca05a9684b79 Content-Type: text/plain; charset="UTF-8" Dear Chairs, all. No, I'm not aware of any IPR that applies to this draft. BR, Dan. On Wed, 1 Jul 2020, 22:26 Jeff Tantsura, wrote: > No, I'm not aware of any IPR that applies to this draft. > > Cheers, > Jeff > On Jul 1, 2020, 11:42 AM -0700, Vishnu Pavan Beeram , > wrote: > > Authors, Contributors, WG, > > As part of the preparation for polling for WG document adoption: > > Are you aware of any IPR that applies to draft 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 3979, 4879, 3669 and 5378 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 and listed > contributor. 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 > > --000000000000d476ca05a9684b79 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear Chairs, all.

<= div dir=3D"auto">No, I'm not aware of any IPR that applies to this draf= t.

BR, Dan.

On= Wed, 1 Jul 2020, 22:26 Jeff Tantsura, <jefftant.ietf@gmail.com> wrote:
No, I'm not aware of any=C2=A0IPR=C2=A0that applies t= o this draft.

Cheers,
Jeff
On Jul 1, 2020, 11:42 AM -0700, Vishnu Pa= van Beeram <vishnupavan@gmail.com>, wrote:
Authors, Contributors, WG,

As part of the preparation for=C2=A0polling=C2=A0for WG document=C2=A0adopt= ion:

Are you aware of any=C2=A0IPR=C2=A0that applies to draft identified above?<= br>
=C2=A0 Please state either:

=C2=A0 "No, I'm not aware of any=C2=A0IPR=C2=A0that applies to thi= s draft"
=C2=A0 or
=C2=A0 "Yes, I'm aware of=C2=A0IPR=C2=A0that applies to this draft= "

If so, has this=C2=A0IPR=C2=A0been disclosed in compliance with IETF=C2=A0I= PR=C2=A0rules
(see RFCs 3979, 4879, 3669 and 5378 for more details)?

If yes to the above, please state either:

=C2=A0 "Yes, the=C2=A0IPR=C2=A0has been disclosed in compliance with I= ETF=C2=A0IPR=C2=A0rules"
=C2=A0 or
=C2=A0 "No, the=C2=A0IPR=C2=A0has not been disclosed"

If you answer no, please provide any additional details you think
=C2=A0 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=C2=A0IPR.=C2=A0 This document will not advance to the= next
stage until a response has been received from each author and listed
contributor.=C2=A0 NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS=C2=A0
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=C2=A0IPR=C2=A0rules which encourages you to notify the IETF if you= are
aware of=C2=A0IPR=C2=A0of others on an IETF contribution, or to refrain fro= m
participating in any contribution or discussion related to your
undisclosed=C2=A0IPR. For more information, please see the RFCs listed abov= e
and
http://trac.tools.iet= f.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
Pavan and Lou
--000000000000d476ca05a9684b79--