IETF Logo Mail Archive

Re: [Teas] Regarding IPR on draft-ietf-teas-pce-central-control

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 22 May 2017 21:20 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 7A553127B60; Mon, 22 May 2017 14:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.102
X-Spam-Level:
X-Spam-Status: No, score=0.102 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] 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 Dzz2QfN6qBX9; Mon, 22 May 2017 14:20:21 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E889A128DF3; Mon, 22 May 2017 14:20:19 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v4MLKGRu011940; Mon, 22 May 2017 22:20:16 +0100
Received: from 950129200 (73.204.115.87.dyn.plus.net [87.115.204.73]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v4MLKFNi011927 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 May 2017 22:20:16 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Vishnu Pavan Beeram' <vishnupavan@gmail.com>
Cc: 'TEAS WG Chairs' <teas-chairs@ietf.org>, teas@ietf.org
References: <CA+YzgTvckqLVww7wQTVu6a==B_iG6=Fs5EX=3NbVNJyQOQp6Aw@mail.gmail.com>
In-Reply-To: <CA+YzgTvckqLVww7wQTVu6a==B_iG6=Fs5EX=3NbVNJyQOQp6Aw@mail.gmail.com>
Date: Mon, 22 May 2017 22:20:13 +0100
Message-ID: <026101d2d341$33e90590$9bbb10b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0262_01D2D349.95B07AD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHBh+VI+h1KKFKdAzsKMoiYeRanK6Ijcemg
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23084.007
X-TM-AS-Result: No--19.947-10.0-31-10
X-imss-scan-details: No--19.947-10.0-31-10
X-TMASE-MatchedRID: Ync95tbzDRkwJ6xbTjBa5uYAh37ZsBDCX5TqQagR07cHp3cP4ojBkJjn 0VVd2q+BxsV4zK22Mc9opg3VnkcLopSL8e/MGApZFVfH7j3N9bf27Syjew41+PWETc72r+tYfQ2 8T7selJzz6xFyOdgkscOFOHoa0LX+y7e/WVbpHztmVHNo7XGknW79evoIpeI3mmzaGKIwUHaAvG IDnCswPdQaD1hgLSvdc4+2jJpVwaEp23mj39P7ak+4wmL9kCTxS0pipcWJ0S7agsZM0qVv1xQX0 Ci7mTQksHABAwbw/Vpskvh6ucexrJZK7fsqplGh71Wx2uUbPLdDr8MVm6DK3TA4N9SXuYkp/hkB Sy3LYQ17CjyP3UZ5MbpGAQ2wD/3Qyx6w4CJ+2uX2Ii0VSfdeQzuvYa1v2IFhTx0U/40+rr7a6BB kIrnTcudLZPVW5sDNedxyf/baQ0eb2ohNz0F+pNT+TcIhUUCBZJAk04EAz2Un+p552csI1Y/sYB BJ7n+d9sFE6GfY4gY8LuP+bOkMWp8voPxO05mszzuzg6dga4Iytf6nW43O0D3dpxIEGwCa8FhGj Tp5WPfe2M7eE7V+nawvTQpsPBALizFhECDuofD4pTO56aJ0/JAX3UzEQF1GpRezBf/GshJ4ouZE jkeLRrCZGEu3G/I6hgKF4YW7GyAvebl6MJ1oUZ0K2Qyuw606mRKFhwukYf1kzblkBbANhmAQRn3 L+ljhjSJ3SkiGrFPXkuVVlJMsPZx6Ilif8OzGL4+sB3yBsckz2D5h92okoUIjuk0uJKN95GpADF tYP37i8zVgXoAlttVnSDvjSUv5IhDmZnlKoc9Ud5j2GccyZNUXi4EljO2QE8pEXAj85Sv+HSKwt hKse1uR5G3q+LkP
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/LY4xGP81xtrfr61GkQrcSctxYQ8>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-pce-central-control
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: Mon, 22 May 2017 21:20:24 -0000

No, I'm not aware of any IPR that applies to this draft.
 
Thanks,
Adrian
 
From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Vishnu Pavan Beeram
Sent: 22 May 2017 21:56
To: afarrel@juniper.net; quintin.zhao@huawei.com; lizhenbin@huawei.com; chao.zhou@cisco.com; cmargaria@juniper.net; scheruathur@juniper.net; Dhruv Dhody; Daniel King; ihussain@infinera.com; Anurag Sharma; eric.wu@huawei.com
Cc: TEAS WG Chairs; teas@ietf.org
Subject: [Teas] Regarding IPR on draft-ietf-teas-pce-central-control
 
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 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,
TEAS WG Chairs

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

v2.23.0 | Report a Bug | By Email