IETF Logo Mail Archive

[Teas] 答复: Regarding IPR on draft-ietf-teas-actn-requirements-06

Zhenghaomian <zhenghaomian@huawei.com> Sat, 28 October 2017 06:11 UTC

Return-Path: <zhenghaomian@huawei.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 F379913F83C; Fri, 27 Oct 2017 23:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, 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 9uOeJgvnYZZ4; Fri, 27 Oct 2017 23:11:57 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D17013F82B; Fri, 27 Oct 2017 23:11:51 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML714-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DRL20944; Sat, 28 Oct 2017 06:11:50 +0000 (GMT)
Received: from DGGEML402-HUB.china.huawei.com (10.3.17.38) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.361.1; Sat, 28 Oct 2017 07:11:49 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.222]) by DGGEML402-HUB.china.huawei.com ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0301.000; Sat, 28 Oct 2017 14:11:37 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>, Leeyoung <leeyoung@huawei.com>, Dhruv Dhody <dhruv.ietf@gmail.com>, "Belotti, Sergio (Nokia - IT)" <sergio.belotti@nokia.com>, Khuzema Pithewan <kpithewan@infinera.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, "ta-miyasaka@kddi.com" <ta-miyasaka@kddi.com>, "jongyoon.shin@sk.com" <jongyoon.shin@sk.com>, "kwangkoog.lee@kt.com" <kwangkoog.lee@kt.com>, "xuyunbin@mail.ritt.com.cn" <xuyunbin@mail.ritt.com.cn>, "toshiaki.suzuki.cs@hitachi.com" <toshiaki.suzuki.cs@hitachi.com>
CC: "teas@ietf.org" <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
Thread-Topic: Regarding IPR on draft-ietf-teas-actn-requirements-06
Thread-Index: AQHTT2s3efnX+VDYek29xwAcNp7Vu6L4yFaw
Date: Sat, 28 Oct 2017 06:11:37 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43B60EA86@dggeml511-mbx.china.huawei.com>
References: <CA+YzgTtBNK8xFzXpH+bx+UesCXxf3=X0QDphPno+ZEce95PHfA@mail.gmail.com>
In-Reply-To: <CA+YzgTtBNK8xFzXpH+bx+UesCXxf3=X0QDphPno+ZEce95PHfA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.57.78.212]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.59F41FA6.007B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.222, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 660492e814a100b073c4b8b7a4ed057f
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/MTgiG2RlvAhb2n8DYM-1OmY4iuo>
Subject: [Teas] 答复: Regarding IPR on draft-ietf-teas-actn-requirements-06
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: Sat, 28 Oct 2017 06:11:59 -0000

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

Best wishes,
Haomian

-----邮件原件-----
发件人: Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com] 
发送时间: 2017年10月28日 5:33
收件人: Leeyoung; Dhruv Dhody; Belotti, Sergio (Nokia - IT); Khuzema Pithewan; Daniele Ceccarelli; ta-miyasaka@kddi.com; jongyoon.shin@sk.com; kwangkoog.lee@kt.com; xuyunbin@mail.ritt.com.cn; toshiaki.suzuki.cs@hitachi.com; Zhenghaomian
抄送: teas@ietf.org; TEAS WG Chairs
主题: Regarding IPR on draft-ietf-teas-actn-requirements-06

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.

v2.23.0 | Report a Bug | By Email