Re: [Teas] Regarding IPR on draft-zhao-teas-pcecc-use-cases

"Chao Zhou (czhou)" <czhou@cisco.com> Sun, 22 January 2017 03:14 UTC

Return-Path: <czhou@cisco.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 87CF6129586; Sat, 21 Jan 2017 19:14:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level:
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 bOdBo_dO_KVK; Sat, 21 Jan 2017 19:14:25 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE6EE129570; Sat, 21 Jan 2017 19:14:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12224; q=dns/txt; s=iport; t=1485054864; x=1486264464; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=T9pxIZd+NOg/mMoxlqGDPF9BeMmhIy+yYV9DNFCJ94E=; b=MzTtVWyNGdQYNUP/wnTyE8Zh5JJDgZZt4GXi+BJy52cs093yCuit/u+z w+ieib7CzEXJggIHc20EnSvErWYenKRnEtgVtUTEhv6psRhByT7G4Rb3r zLLGHj9PALndW9w4KDAAgrG0JX49fr9x8MilquvEgWRsaPXtFe5dGKluC o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AkAQAkI4RY/49dJa1eGQEBAQEBAQEBAQEBBwEBAQEBgm8+EAEBAQEBH2CBCQeDTIoIkgGIBod9hSuCDSqFeAIagXs/GAECAQEBAQEBAWMohGkBAQEEI1EFEAIBCBEDAQIrAgICHxEdCAIEAQ0FiHEDGA6peYNRgiUrhnYNgwgBAQEBAQEBAQEBAQEBAQEBAQEBAQEdhkuCBYJrglGBShEBMwmCZi2CMQWVOoVZOAGGYYcAhAiBd1KEPYloih+IVgEPEDhzVBU6EAGGJXMBhXKBIYENAQEB
X-IronPort-AV: E=Sophos;i="5.33,267,1477958400"; d="scan'208,217";a="196081351"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jan 2017 03:14:23 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v0M3EMfn030972 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 22 Jan 2017 03:14:23 GMT
Received: from xch-rtp-006.cisco.com (64.101.220.146) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 21 Jan 2017 22:14:22 -0500
Received: from xch-rtp-006.cisco.com ([64.101.220.146]) by XCH-RTP-006.cisco.com ([64.101.220.146]) with mapi id 15.00.1210.000; Sat, 21 Jan 2017 22:14:21 -0500
From: "Chao Zhou (czhou)" <czhou@cisco.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>, "quintin.zhao@huawei.com" <quintin.zhao@huawei.com>, "lizhenbin@huawei.com" <lizhenbin@huawei.com>, "khasanov.boris@huawei.com" <khasanov.boris@huawei.com>, "kinghe@tencent.com" <kinghe@tencent.com>, "chao.zhou@cisco.com" <chao.zhou@cisco.com>, "boris.zhang@telus.com" <boris.zhang@telus.com>, "arachitskiy@mts.by" <arachitskiy@mts.by>, "agulida@mts.by" <agulida@mts.by>, "lufang@ebay.com" <lufang@ebay.com>
Thread-Topic: Regarding IPR on draft-zhao-teas-pcecc-use-cases
Thread-Index: AQHSc/UxJTVq66fclEWm05hvKC91Z6FErUOA
Date: Sun, 22 Jan 2017 03:14:21 +0000
Message-ID: <11EE4FDB-A485-42F5-BFF8-29A283F6960F@cisco.com>
References: <CA+YzgTvmsC9sVXw1F05buCUKYGm6hfOZ59OGK9orEdEoEbbq1g@mail.gmail.com>
In-Reply-To: <CA+YzgTvmsC9sVXw1F05buCUKYGm6hfOZ59OGK9orEdEoEbbq1g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1a.0.160910
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.79.127.136]
Content-Type: multipart/alternative; boundary="_000_11EE4FDBA48542F5BFF829A283F6960Fciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/fAub4lWFkzyCkBroRLovQ_p3nB0>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Subject: Re: [Teas] Regarding IPR on draft-zhao-teas-pcecc-use-cases
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 22 Jan 2017 03:14:26 -0000

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

Thanks.
-Chao

From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Saturday, January 21, 2017 at 10:46 PM
To: Quintin Zhao <quintin.zhao@huawei.com>, 'Lizhenbin' <lizhenbin@huawei.com>, "khasanov.boris@huawei.com" <khasanov.boris@huawei.com>, "kinghe@tencent.com" <kinghe@tencent.com>, "chao.zhou@cisco.com" <chao.zhou@cisco.com>, "boris.zhang@telus.com" <boris.zhang@telus.com>, "arachitskiy@mts.by" <arachitskiy@mts.by>, "agulida@mts.by" <agulida@mts.by>, "lufang@ebay.com" <lufang@ebay.com>
Cc: "teas@ietf.org" <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
Subject: Regarding IPR on draft-zhao-teas-pcecc-use-cases

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