Re: [Teas] Regarding IPR on draft-ietf-teas-actn-framework-10

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 27 October 2017 22:18 UTC

Return-Path: <adrian@olddog.co.uk>
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 BBC8213F5F7; Fri, 27 Oct 2017 15:18:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham 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 udHGbNe90t_d; Fri, 27 Oct 2017 15:17:58 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7759013F5F5; Fri, 27 Oct 2017 15:17:58 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id v9RMHnvl023795; Fri, 27 Oct 2017 23:17:49 +0100
Received: from 950129200 (105.76.115.87.dyn.plus.net [87.115.76.105]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id v9RMHlYQ023782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Oct 2017 23:17:48 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Vishnu Pavan Beeram'" <vishnupavan@gmail.com>, "'Daniele Ceccarelli'" <daniele.ceccarelli@ericsson.com>, "'Leeyoung'" <leeyoung@huawei.com>, "'Italo Busi'" <Italo.Busi@huawei.com>, "'Khuzema Pithewan'" <kpithewan@infinera.com>, "'Scharf, Michael \(Nokia - DE\)'" <michael.scharf@nokia.com>, "'Luyuan Fang'" <luyuanf@gmail.com>, <diego@tid.es>, "'Belotti, Sergio \(Nokia - IT\)'" <sergio.belotti@nokia.com>, <d.king@lancaster.ac.uk>, "'Dhruv Dhody'" <dhruv.ietf@gmail.com>, "'Gert Grammel'" <ggrammel@juniper.net>
Cc: <teas@ietf.org>, "'TEAS WG Chairs'" <teas-chairs@ietf.org>
References: <CA+YzgTunGbZzMOvS9a5fMST2LLk-GzU4mm35aU2Kkr992DLUWQ@mail.gmail.com>
In-Reply-To: <CA+YzgTunGbZzMOvS9a5fMST2LLk-GzU4mm35aU2Kkr992DLUWQ@mail.gmail.com>
Date: Fri, 27 Oct 2017 23:17:41 +0100
Message-ID: <008801d34f71$6917c2e0$3b4748a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ4VgEqdgIbOrnRaJamm0uleZBx9KGuNW0A
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23422.003
X-TM-AS-Result: No--9.872-10.0-31-10
X-imss-scan-details: No--9.872-10.0-31-10
X-TMASE-MatchedRID: u7Yf2n7Ca/0v2k3M27J31p21GZGE81yGt+hhn8Iy6GXadW4iYSMjUae7 nmhJA6kzZ81JypZjTb8E5rtJqNQ7b5R0O6A0usb1lVHM/F6YkvT2acON9Q+rnsUmcSma304TSsX dBTjJu8OSJDsK0LUOWcs84zBIgEgt4QsjLzswuv5omJbPMdjPdDTbofuc5kuvut/GVGOoEnf36x IGbTm5O04kHnA/WiqE3Qq0ey35KMz3fZ+bzIHVnpMSBMTQNiSAgHzgwy8qV5qn29pdUyz/h6iZa OZUGVmq/6RJK3ec/64XmgKQJcfTfxfz4r7vtfFdEwyZyuMQ4119LQinZ4QefNQdB5NUNSsi1GcR AJRT6POOhzOa6g8Krd19Xc5DsagHF579ZkVnbrEvOrf2mPPrO5u42yXdmt9go8DNoH0+vRVDDKa 3G4nrLQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/dbvU5Cj4ncJ7w4quBMzZGnmOaWc>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-actn-framework-10
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
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, 27 Oct 2017 22:18:01 -0000

Hi,

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

Cheers,
Adrian

> -----Original Message-----
> From: Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com]
> Sent: 27 October 2017 22:28
> To: Daniele Ceccarelli; Leeyoung; Adrian Farrel; Italo Busi; Khuzema Pithewan;
> Scharf, Michael (Nokia - DE); Luyuan Fang; diego@tid.es; Belotti, Sergio (Nokia -
> IT); d.king@lancaster.ac.uk; Dhruv Dhody; Gert Grammel
> Cc: teas@ietf.org; TEAS WG Chairs
> Subject: Regarding IPR on draft-ietf-teas-actn-framework-10
> 
> Authors, Contributors, WG,
> 
> As part of the preparation for 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 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,
> TEAS WG Chairs
> 
> PS Please include all listed in the headers of this message in your
> response.