Re: [Teas] Regarding IPR on draft-lee-teas-actn-vn-yang

"Takuya Miyasaka" <ta-miyasaka@kddi.com> Mon, 07 May 2018 02:58 UTC

Return-Path: <ta-miyasaka@kddi.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 E8DEB1270AB; Sun, 6 May 2018 19:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 X4gq-hr2ilbP; Sun, 6 May 2018 19:58:23 -0700 (PDT)
Received: from post-send.kddi.com (athena2.kddi.com [27.90.165.195]) by ietfa.amsl.com (Postfix) with ESMTP id B4DC012D88B; Sun, 6 May 2018 19:58:20 -0700 (PDT)
Received: from LTMC2123.kddi.com (post-send [10.206.2.120]) by post-send.kddi.com (KDDI Mail) with ESMTP id B2201E0036; Mon, 7 May 2018 11:58:19 +0900 (JST)
Received: from LTMC2146.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2123.kddi.com with ESMTP; Mon, 7 May 2018 11:58:19 +0900
Received: from LTMC2146.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 8280530005D; Mon, 7 May 2018 11:58:19 +0900 (JST)
Received: from LTMC2151.kddi.com (post-incheck [10.206.0.239]) by LTMC2146.kddi.com (Postfix) with ESMTP id 7725C300051; Mon, 7 May 2018 11:58:19 +0900 (JST)
Received: from LTMC2151.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2151.kddi.com with ESMTP id w472wJb6024184; Mon, 7 May 2018 11:58:19 +0900
Received: from LTMC2151.kddi.com.mid_43195647 (localhost.localdomain [127.0.0.1]) by LTMC2151.kddi.com with ESMTP id w472usRO022139; Mon, 7 May 2018 11:56:54 +0900
X-SA-MID: 43195647
Received: from KDDI1004PC0155 ([10.211.123.216] [10.211.123.216]) by post-smtp2.kddi.com with ESMTPA; Mon, 7 May 2018 11:56:53 +0900
From: "Takuya Miyasaka" <ta-miyasaka@kddi.com>
To: "'Vishnu Pavan Beeram'" <vishnupavan@gmail.com>
Cc: "'TEAS WG Chairs'" <teas-chairs@ietf.org>, "'TEAS WG'" <teas@ietf.org>
References: <CA+YzgTuiBPQmifhiME=+gVAVeVfNyvJPKeMjfzeOGD2H1-svnQ@mail.gmail.com> <fd7aabd2-8c93-1cc5-0f7a-79d4e18846a0@kddi-research.jp>
In-Reply-To: <fd7aabd2-8c93-1cc5-0f7a-79d4e18846a0@kddi-research.jp>
Date: Mon, 7 May 2018 11:56:53 +0900
Message-ID: <000701d3e5af$0ddd22b0$29976810$@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQMPpxuP9FcOQPnMjRDbUBi3qMIm1wIHn5looZvREdA=
Content-Language: ja
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Sxwh_V-lwLiV0zQGXf9C0BZTsqI>
Subject: Re: [Teas] Regarding IPR on draft-lee-teas-actn-vn-yang
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, 07 May 2018 02:58:26 -0000

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

Thanks,
Takuya

-----Original Message----- 
Subject: 	[Teas] Regarding IPR on draft-lee-teas-actn-vn-yang	 
Resent-Date: 	Wed, 2 May 2018 10:33:44 +0900	 
Resent-From: 	Postmaster@kddi.com	 
Date: 	Tue, 1 May 2018 21:33:34 -0400	 
From: 	Vishnu Pavan Beeram <vishnupavan@gmail.com> <mailto:vishnupavan@gmail.com> 	 
To: 	Leeyoung <leeyoung@huawei.com> <mailto:leeyoung@huawei.com> , Dhruv Dhody <dhruv.ietf@gmail.com> <mailto:dhruv.ietf@gmail.com> , Daniele Ceccarelli <daniele.ceccarelli@ericsson.com> <mailto:daniele.ceccarelli@ericsson.com> , Igor Bryskin <Igor.Bryskin@huawei.com> <mailto:Igor.Bryskin@huawei.com> , byyun@etri.re.kr, zhenghaomian@huawei.com, Zhangxian (Xian) <zhang.xian@huawei.com> <mailto:zhang.xian@huawei.com> , Belotti, Sergio (Nokia - IT) <sergio.belotti@nokia.com> <mailto:sergio.belotti@nokia.com> , bill.wu@huawei.com, ta-miyasaka@kddi.com, peter.park@kt.com	 
CC: 	TEAS WG Chairs <teas-chairs@ietf.org> <mailto:teas-chairs@ietf.org> , TEAS WG <teas@ietf.org> <mailto:teas@ietf.org> 	 


Authors, Contributors, WG,

As part of preparation for 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 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 <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.