IETF Logo Mail Archive

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

Raveendra Torvi <rtorvi@juniper.net> Tue, 07 March 2017 15:18 UTC

Return-Path: <rtorvi@juniper.net>
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 A9C3F12943E; Tue, 7 Mar 2017 07:18:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 Vw_cO8_0_Usf; Tue, 7 Mar 2017 07:18:21 -0800 (PST)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0126.outbound.protection.outlook.com [104.47.36.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCB8D126DFB; Tue, 7 Mar 2017 07:18:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Xyq4uwuAQQezHPr5MuIMF16KVy3BF9O3sGlxUUhKZL0=; b=CakA+b8LrrrC2U/suZG47dMOcntAM4N2UOMSpRgBQ7MkceLnfOdI8jBcUy0ZRfCa9UEuLUkrAXrmuhbN0Bd55sjLc/CBDGuDpfN7wruVX/FprYBtsuKvo/kyLobGvxfMVnm3hvQqTQNKT6+kMOu3OKL2Lq9HZuOnkJnLWbDH7iI=
Received: from MWHPR05MB3086.namprd05.prod.outlook.com (10.173.228.144) by CY1PR0501MB1564.namprd05.prod.outlook.com (10.161.161.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.2; Tue, 7 Mar 2017 15:18:19 +0000
Received: from MWHPR05MB3086.namprd05.prod.outlook.com ([10.173.228.144]) by MWHPR05MB3086.namprd05.prod.outlook.com ([10.173.228.144]) with mapi id 15.01.0961.014; Tue, 7 Mar 2017 15:18:17 +0000
From: Raveendra Torvi <rtorvi@juniper.net>
To: "EXT-vishnupavan@gmail.com" <vishnupavan@gmail.com>, Huaimo Chen <huaimo.chen@huawei.com>, "ningso01@gmail.com" <ningso01@gmail.com>, "hliu@ciena.com" <hliu@ciena.com>, "zhenbin.li@huawei.com" <zhenbin.li@huawei.com>, Yimin Shen <yshen@juniper.net>, "Tarek Saad (tsaad)" <tsaad@cisco.com>, "fengman.xu@verizon.com" <fengman.xu@verizon.com>, "mehmet.toy@verizon.com" <mehmet.toy@verizon.com>, "liulei.kddi@gmail.com" <liulei.kddi@gmail.com>, "renwei.li@huawei.com" <renwei.li@huawei.com>, "quintin.zhao@huawei.com" <quintin.zhao@huawei.com>, "Boris.Zhang@telus.com" <Boris.Zhang@telus.com>, Markus Jork <mjork@juniper.net>
Thread-Topic: Regarding IPR on draft-ietf-teas-rsvp-ingress-protection
Thread-Index: AQHSlsFgoJag7c4qW0mDoWj8qsLR6qGJKsOA
Date: Tue, 07 Mar 2017 15:18:17 +0000
Message-ID: <ADFADF23-924A-4079-9A2C-48D03118BDD4@juniper.net>
References: <CA+YzgTthjgtzu3WKc7=2jeVYg=4bXTuctoS6jpLY6PYUqGV-XQ@mail.gmail.com>
In-Reply-To: <CA+YzgTthjgtzu3WKc7=2jeVYg=4bXTuctoS6jpLY6PYUqGV-XQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1b.0.161010
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.14]
x-microsoft-exchange-diagnostics: 1; CY1PR0501MB1564; 7:g1oeUt6FBCkNSS1qGLbXTb+XtNRijyD6iItH4XCKtonkTZOllXz9Rp4Tc+MfsZoJyLJ2bLvCqO5M/+FdrDWwxJnU1CUWceWQoRCjJe0q9wO8yYM+uwIw1nb5VkbjXwVba6MGkr1QrylhgtMZCJY0ex0wKqGAcv9cxZh0W+ZasbvUvEZWTR1Fpk4HoRue1qDV52uB8RdRujJRORTgDcBZpyC6e6odPeIS+1K4a66yunHyX+LE5Oi1EQhEPMcaQ4TGu0XeFrgN0H0zhDSAegd7VmWeI5FEmhbvX0woS1syrnrn0vu5dCdwGMLDGwDFgT+MXAwaeOssO/IClxhDx7l+EQ==
x-ld-processed: bea78b3c-4cdb-4130-854a-1d193232e5f4,ExtAddr
x-forefront-antispam-report: SFV:SKI; SCL:-1SFV:NSPM; SFS:(10019020)(7916002)(39860400002)(39840400002)(39850400002)(39410400002)(39450400003)(377454003)(24454002)(6636002)(966004)(189998001)(6512007)(3660700001)(38730400002)(106116001)(82746002)(33656002)(81166006)(83506001)(36756003)(99286003)(2900100001)(2501003)(2201001)(14971765001)(54906002)(6306002)(7416002)(8676002)(83716003)(54896002)(8936002)(25786008)(236005)(4001350100001)(122556002)(7906003)(53546006)(77096006)(102836003)(3846002)(6436002)(86362001)(2950100002)(229853002)(606005)(230783001)(6116002)(2906002)(66066001)(6246003)(3280700002)(7736002)(4326008)(76176999)(50986999)(54356999)(53936002)(5660300001)(6506006)(39060400002)(1941001)(6486002)(921003)(1121003)(104396002)(491001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0501MB1564; H:MWHPR05MB3086.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
x-ms-office365-filtering-correlation-id: a0437476-0d9e-4af1-7f34-08d4656d2ecd
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:CY1PR0501MB1564;
x-microsoft-antispam-prvs: <CY1PR0501MB156446E738FFA2A82CEA5F22D02F0@CY1PR0501MB1564.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123564025)(20161123560025)(20161123562025)(20161123558025)(20161123555025)(6072148); SRVR:CY1PR0501MB1564; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0501MB1564;
x-forefront-prvs: 0239D46DB6
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_ADFADF23924A40799A2C48D03118BDD4junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2017 15:18:17.6205 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB1564
Cc: TEAS WG Chairs <teas-chairs@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-rsvp-ingress-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: Tue, 07 Mar 2017 15:18:22 -0000

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

-Ravi

On 3/6/17, 4:34 PM, "Vishnu Pavan Beeram" <vishnupavan@gmail.com<mailto:vishnupavan@gmail.com>> wrote:

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