Re: [OSPF] [E] IPR Poll "OSPF Link Overload"
"Jalil, Luay" <luay.jalil@verizon.com> Mon, 23 October 2017 04:54 UTC
Return-Path: <luay.jalil@verizon.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 86C4313D62B;
Sun, 22 Oct 2017 21:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.731
X-Spam-Level:
X-Spam-Status: No, score=-0.731 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, HTTPS_HTTP_MISMATCH=1.989,
RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01,
RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=verizon.com header.b=su+I5FtL;
dkim=fail (1024-bit key)
reason="fail (message has been altered)" header.d=verizon.com
header.b=kjYFo3Bg; dkim=fail (1024-bit key)
reason="fail (message has been altered)" header.d=verizon.com
header.b=kjYFo3Bg
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 QTaRrZrzlbX3; Sun, 22 Oct 2017 21:54:26 -0700 (PDT)
Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com
[199.249.25.209])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id BCE5713D62A;
Sun, 22 Oct 2017 21:54:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=verizon.com; i=@verizon.com; q=dns/txt; s=corp;
t=1508734465; x=1540270465;
h=from:to:cc:subject:date:message-id:references:
in-reply-to:mime-version;
bh=a7oZ4OOA4GcIHkMLwjVo4/C188kuuNvTxxxLw0UODSs=;
b=su+I5FtL0t/rjGrIUUtkHRvxr/9a7yhZlMrgQLiTA3lLIgin30WGx4ZA
tJTMaJ8AHvLdmmwVDi0ebbrE2Ab3eemQ+Pv0JuZhbWH6p5Hndu3Xp3vdG
9CEekU1ex0vBTEkdiDzGrvllpuFQTGqU9bet8XS6kvgJqCBnJKnGqbZnT I=;
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143])
by omzsmtpe02.verizonbusiness.com with ESMTP; 23 Oct 2017 04:54:23 +0000
From: "Jalil, Luay" <luay.jalil@verizon.com>
Received: from rogue-10-255-192-101.rogue.vzwcorp.com (HELO
apollo.verizonwireless.com) ([10.255.192.101])
by fldsmtpi01.verizon.com with ESMTP/TLS/DHE-RSA-AES256-SHA;
23 Oct 2017 04:53:50 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=verizon.com; i=@verizon.com; q=dns/txt; s=corp;
t=1508734430; x=1540270430;
h=from:to:cc:subject:date:message-id:references:
in-reply-to:mime-version;
bh=a7oZ4OOA4GcIHkMLwjVo4/C188kuuNvTxxxLw0UODSs=;
b=kjYFo3BgfxGeifFJ1BEYot2VkTNk36vfz5SGz/ngZLSEm8z8aQubRm69
kE2HnNT5gRc6j0mGn8c6Ow+ydNqj8uDHIxxe/DkqE3gK+u/G+rac3Onva
J6lNRK8qezl6j8Hlc7iaD5Iq3zEAKU/4dDL3Yu7pT8ZeUD0iPBK6Rm/bw w=;
Received: from endeavour.tdc.vzwcorp.com (HELO eris.verizonwireless.com)
([10.254.88.163])
by apollo.verizonwireless.com with ESMTP/TLS/DHE-RSA-AES256-SHA;
23 Oct 2017 00:53:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=verizon.com; i=@verizon.com; q=dns/txt; s=corp;
t=1508734430; x=1540270430;
h=from:to:cc:subject:date:message-id:references:
in-reply-to:mime-version;
bh=a7oZ4OOA4GcIHkMLwjVo4/C188kuuNvTxxxLw0UODSs=;
b=kjYFo3BgfxGeifFJ1BEYot2VkTNk36vfz5SGz/ngZLSEm8z8aQubRm69
kE2HnNT5gRc6j0mGn8c6Ow+ydNqj8uDHIxxe/DkqE3gK+u/G+rac3Onva
J6lNRK8qezl6j8Hlc7iaD5Iq3zEAKU/4dDL3Yu7pT8ZeUD0iPBK6Rm/bw w=;
X-Host: endeavour.tdc.vzwcorp.com
Received: from ohtwi1exh003.uswin.ad.vzwcorp.com ([10.144.218.45])
by eris.verizonwireless.com with ESMTP/TLS/AES128-SHA256;
23 Oct 2017 04:53:37 +0000
Received: from tbwexch19apd.uswin.ad.vzwcorp.com (153.114.162.43) by
OHTWI1EXH003.uswin.ad.vzwcorp.com (10.144.218.45) with Microsoft SMTP Server
(TLS) id 14.3.248.2; Mon, 23 Oct 2017 00:53:37 -0400
Received: from OMZP1LUMXCA05.uswin.ad.vzwcorp.com (144.8.22.175) by
tbwexch19apd.uswin.ad.vzwcorp.com (153.114.162.43) with Microsoft SMTP Server
(TLS) id 15.0.1263.5; Mon, 23 Oct 2017 00:53:37 -0400
Received: from OMZP1LUMXCA07.uswin.ad.vzwcorp.com (144.8.22.180) by
OMZP1LUMXCA05.uswin.ad.vzwcorp.com (144.8.22.175) with Microsoft SMTP Server
(TLS) id 15.0.1263.5; Sun, 22 Oct 2017 23:53:36 -0500
Received: from OMZP1LUMXCA07.uswin.ad.vzwcorp.com ([144.8.22.180]) by
OMZP1LUMXCA07.uswin.ad.vzwcorp.com ([144.8.22.180]) with mapi id
15.00.1263.000; Sun, 22 Oct 2017 23:53:36 -0500
To: "Acee Lindem (acee)" <acee@cisco.com>,
"draft-ietf-ospf-link-overload@ietf.org"
<draft-ietf-ospf-link-overload@ietf.org>
CC: OSPF WG List <ospf@ietf.org>
Thread-Topic: [E] IPR Poll "OSPF Link Overload"
Thread-Index: AQHTS7ri+TwUOjZ5BkmOb++SXxOC5Q==
Date: Mon, 23 Oct 2017 04:53:36 +0000
Message-ID: <9qly8hhtf5nbefir6eae9j8w.1508734413997@email.android.com>
References: <D6110F24.D0DEE%acee@cisco.com>
In-Reply-To: <D6110F24.D0DEE%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative;
boundary="_000_9qly8hhtf5nbefir6eae9j8w1508734413997emailandroidcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/XnGfIHDEj14Tt0zxV1M8CM4Z-Qg>
Subject: Re: [OSPF] [E] IPR Poll "OSPF Link Overload"
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>,
<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
<mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Oct 2017 04:54:27 -0000
I'm not aware of any IPR other than the Juniper one Regards, Luay -------- Original Message -------- From: "Acee Lindem (acee)" <acee@cisco.com<mailto:acee@cisco.com>> Date: Sat, Oct 21, 2017, 1:50 PM To: "draft-ietf-ospf-link-overload@ietf.org<mailto:draft-ietf-ospf-link-overload@ietf.org>" <draft-ietf-ospf-link-overload@ietf.org<mailto:draft-ietf-ospf-link-overload@ietf.org>> CC: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>> Subject: [E] IPR Poll "OSPF Link Overload" Authors, Please indicate whether you are aware of any relevant IPR and if so, whether it has been disclosed. The following IPR has been disclosed: https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-ospf-link-overload<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_ipr_search_-3Fsubmit-3Ddraft-26id-3Ddraft-2Dietf-2Dospf-2Dlink-2Doverload&d=DwQGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&m=8fqnQmnaAZiC42ufr7KPf6KEspOzP7K_muAz82Vk39I&s=v5ijRhFmMrlfX2SWNe-cuMqQN6lwSg-74-Jl1JIMmN0&e=> Thanks, Acee
- [OSPF] IPR Poll "OSPF Link Overload" Acee Lindem (acee)
- Re: [OSPF] IPR Poll "OSPF Link Overload" Hannes Gredler
- Re: [OSPF] IPR Poll "OSPF Link Overload" Shraddha Hegde
- Re: [OSPF] [E] IPR Poll "OSPF Link Overload" Jalil, Luay
- Re: [OSPF] IPR Poll "OSPF Link Overload" Mohan Nanduri
- Re: [OSPF] IPR Poll "OSPF Link Overload" Acee Lindem (acee)
- Re: [OSPF] IPR Poll "OSPF Link Overload" Pushpasis Sarkar