IETF Logo Mail Archive

Re: [Teas] Regarding IPR on draft-ietf-teas-rsvp-egress-protection

Mengnan <mengnan@huawei.com> Wed, 08 March 2017 00:58 UTC

Return-Path: <mengnan@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 4F1B9129470; Tue, 7 Mar 2017 16:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 hOGj2vsnNNvP; Tue, 7 Mar 2017 16:58:17 -0800 (PST)
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 254D6126579; Tue, 7 Mar 2017 16:58:16 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DCJ33981; Wed, 08 Mar 2017 00:58:13 +0000 (GMT)
Received: from SZXEMA413-HUB.china.huawei.com (10.82.72.72) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 8 Mar 2017 00:58:12 +0000
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.67]) by SZXEMA413-HUB.china.huawei.com ([10.82.72.72]) with mapi id 14.03.0235.001; Wed, 8 Mar 2017 08:58:03 +0800
From: Mengnan <mengnan@huawei.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>, Huaimo Chen <huaimo.chen@huawei.com>, "hliu@ciena.com" <hliu@ciena.com>, "Tarek Saad (tsaad)" <tsaad@cisco.com>, "fengman.xu@verizon.com" <fengman.xu@verizon.com>, "huanglu@chinamobile.com" <huanglu@chinamobile.com>, "ningso01@gmail.com" <ningso01@gmail.com>, "mehmet.toy@verizon.com" <mehmet.toy@verizon.com>, "lliu@us.fujitsu.com" <lliu@us.fujitsu.com>, Lizhenbin <lizhenbin@huawei.com>, "boris.zhang@telus.com" <boris.zhang@telus.com>, "prejeeth@gmail.com" <prejeeth@gmail.com>, "liu.cmri@gmail.com" <liu.cmri@gmail.com>
Thread-Topic: Regarding IPR on draft-ietf-teas-rsvp-egress-protection
Thread-Index: AdKXpp9eJsJwR/2lS/uYas3K1iZsLg==
Date: Wed, 08 Mar 2017 00:58:03 +0000
Message-ID: <6A70085375009045B8212879C8E5A23ACC4DFEC3@szxema506-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.73.56]
Content-Type: multipart/alternative; boundary="_000_6A70085375009045B8212879C8E5A23ACC4DFEC3szxema506mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.58BF5726.0028, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.67, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: e4c7badd1cfa663fe70741f96d92998b
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/GJJ7OcMPETnGqpPsT5ceW_6ewv0>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-rsvp-egress-protection
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: Wed, 08 Mar 2017 00:58:20 -0000

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

Best Regards,
Nan Meng



发件人: Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com]
发送时间: 2017年3月7日 5:41
收件人: Huaimo Chen <huaimo.chen@huawei.com>; hliu@ciena.com; Tarek Saad (tsaad) <tsaad@cisco.com>; fengman.xu@verizon.com; huanglu@chinamobile.com; ningso01@gmail.com; mehmet.toy@verizon.com; lliu@us.fujitsu.com; Lizhenbin <lizhenbin@huawei.com>; boris.zhang@telus.com; Mengnan <mengnan@huawei.com>; prejeeth@gmail.com; liu.cmri@gmail.com
抄送: teas@ietf.org; TEAS WG Chairs <teas-chairs@ietf.org>
主题: Regarding IPR on draft-ietf-teas-rsvp-egress-protection

Authors, Contributors, WG,

As part of the preparation for WG Last Call

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

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

v2.23.0 | Report a Bug | By Email