Re: [OSPF] [E] IPR Call for "Advertising Tunneling Capability in OSPF"
luay.jalil@verizon.com Thu, 27 April 2017 15:06 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 A885612956C; Thu, 27 Apr 2017 08:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.71
X-Spam-Level:
X-Spam-Status: No, score=-0.71 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, 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=verizon.com header.b=CugAg4gd; dkim=pass (1024-bit key) header.d=verizon.com header.b=UPzp6I4d; dkim=pass (1024-bit key) header.d=verizon.com header.b=aj4ohah1
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 nku382aBzQ1w; Thu, 27 Apr 2017 08:06:14 -0700 (PDT)
Received: from omzsmtpe03.verizonbusiness.com (omzsmtpe03.verizonbusiness.com [199.249.25.208]) (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 F0B55129AFE; Thu, 27 Apr 2017 08:04:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1493305496; x=1524841496; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=n+Bk9KIWApziOwc4dlrHH4Kjzj4y9jMaSMc+ATAUWVM=; b=CugAg4gdg52r+Tg88j4LqhtWMrvmlKAERXvL5RUraWAd/xXQxInYhOwo wDPGUZB5TWIU/+n3InbD4Rrr/fHEI5L4hhhbmBwjLoDS5rwThH7C2YCM7 uuH5z07g0Y0KSEhBLXxMfS1F32txIEOZy/botbdzpmjUHRkvrIryW9RNv o=;
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by omzsmtpe03.verizonbusiness.com with ESMTP; 27 Apr 2017 15:04:53 +0000
X-IronPort-AV: E=Sophos;i="5.37,384,1488844800"; d="scan'208,217";a="195222465"
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; 27 Apr 2017 15:03:53 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1493305433; x=1524841433; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=n+Bk9KIWApziOwc4dlrHH4Kjzj4y9jMaSMc+ATAUWVM=; b=UPzp6I4doICltHsJ3BzOq1XLjAmFJ3tQyZWOVOTBQiCJzWlbc81F+cg4 euRvyAX5i/cBDetjME066ukU4LExazaxsou1HPdZ4d37vmuO8qWhP4BGy i8b6CEhFHRCGiJ1LvpaXhfJwboVXCr4HAQI++mwPYmSSgwHA0z6lA3Hfp Y=;
Received: from challenger.odc.vzwcorp.com (HELO mercury.verizonwireless.com) ([10.255.240.24]) by apollo.verizonwireless.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 27 Apr 2017 11:03:52 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1493305433; x=1524841433; h=to:cc:subject:date:message-id:references:in-reply-to: mime-version:from; bh=n+Bk9KIWApziOwc4dlrHH4Kjzj4y9jMaSMc+ATAUWVM=; b=aj4ohah1qdaAmoDbaZgB/6/E0+V0zx4bH8I6q7G2JXc3ENZKlAC48K/t 8oDDzDT3DnqxZmvLmM0gg7lYjX+7kW2nXtUtwLMHtp972yWEqhYJxWXEi ptp3N4xoVAuHaoZ/U3L8P7ootyEcmSorp45ammhe/mtu/dBxJ5fPuPyYK U=;
From: luay.jalil@verizon.com
X-Host: challenger.odc.vzwcorp.com
Received: from gaalpexhub2.uswin.ad.vzwcorp.com ([10.191.138.196]) by mercury.verizonwireless.com with ESMTP/TLS/AES256-SHA; 27 Apr 2017 15:03:50 +0000
Received: from OMZP1LUMXCA05.uswin.ad.vzwcorp.com (144.8.22.175) by GAALPEXHUB2.uswin.ad.vzwcorp.com (10.191.138.196) with Microsoft SMTP Server (TLS) id 8.3.406.0; Thu, 27 Apr 2017 11:03:11 -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; Thu, 27 Apr 2017 10:03:10 -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; Thu, 27 Apr 2017 10:03:10 -0500
To: "Acee Lindem (acee)" <acee@cisco.com>, "draft-ietf-ospf-encapsulation-cap@ietf.org" <draft-ietf-ospf-encapsulation-cap@ietf.org>
CC: OSPF WG List <ospf@ietf.org>
Thread-Topic: [E] IPR Call for "Advertising Tunneling Capability in OSPF"
Thread-Index: AQHSv2diyrlzAQ8mSkWoEaz6wp952g==
Date: Thu, 27 Apr 2017 15:03:10 +0000
Message-ID: <3idm7cn1pgbso9g7prxf6ix2.1493305387624@email.android.com>
References: <D5277D85.ABED6%acee@cisco.com>
In-Reply-To: <D5277D85.ABED6%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_3idm7cn1pgbso9g7prxf6ix21493305387624emailandroidcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/IqoiVguudZPy7lghfEDO2OkUPko>
Subject: Re: [OSPF] [E] IPR Call for "Advertising Tunneling Capability in OSPF"
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: Thu, 27 Apr 2017 15:06:16 -0000
Not aware of any IPR Thanks, Luay -------- Original Message -------- From: "Acee Lindem (acee)" <acee@cisco.com<mailto:acee@cisco.com>> Date: Thu, Apr 27, 2017, 10:51 AM To: "draft-ietf-ospf-encapsulation-cap@ietf.org<mailto:draft-ietf-ospf-encapsulation-cap@ietf.org>" <draft-ietf-ospf-encapsulation-cap@ietf.org<mailto:draft-ietf-ospf-encapsulation-cap@ietf.org>> CC: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>> Subject: [E] IPR Call for "Advertising Tunneling Capability in OSPF" Authors, Concurrent with the OSPF WG last call, we are polling again as to whether you have knowledge of any undeclared IPR. So far, there are no IPR declarations related to the document. https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-ospf-encapsulation-cap<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_ipr_search_-3Fsubmit-3Ddraft-26id-3Ddraft-2Dietf-2Dospf-2Dencapsulation-2Dcap&d=DwQGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=7yfE7g9ZjpRzGkNuVTidj5c7H2bMIhCLfUwl8WcELSY&m=4aoiCSmUZ8LyI_QXKBZyyt3jBbJ_SZg-jWOlQ-Ol-tg&s=X04kG-BQm1mLEu_LTu0RaefcF45fp7E3Zb7yHe0d1lw&e=> Please confirm to the best of your knowledge that there is no IPR. Thanks, Acee
- Re: [OSPF] [E] IPR Call for "Advertising Tunnelin… luay.jalil
- [OSPF] IPR Call for "Advertising Tunneling Capabi… Acee Lindem (acee)
- [OSPF] 答复: IPR Call for "Advertising Tunneling Ca… Xuxiaohu
- Re: [OSPF] IPR Call for "Advertising Tunneling Ca… bruno.decraene
- Re: [OSPF] IPR Call for "Advertising Tunneling Ca… Uma Chunduri
- Re: [OSPF] IPR Call for "Advertising Tunneling Ca… Acee Lindem (acee)
- Re: [OSPF] IPR Call for "Advertising Tunneling Ca… Acee Lindem (acee)
- Re: [OSPF] IPR Call for "Advertising Tunneling Ca… Robert Raszuk