IETF Logo Mail Archive

RE: Polling for IPR on the E-Tree Requirements draft draft-ietf-l2vpn-etree-reqt-04

Raymond Key <raymond.key@ieee.org> Fri, 05 April 2013 12:03 UTC

Return-Path: <raymond.key@hotmail.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 647E621F89DB for <l2vpn@ietfa.amsl.com>; Fri, 5 Apr 2013 05:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.698
X-Spam-Level:
X-Spam-Status: No, score=-101.698 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_65=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NESBW0GKtXXy for <l2vpn@ietfa.amsl.com>; Fri, 5 Apr 2013 05:03:20 -0700 (PDT)
Received: from blu0-omc2-s35.blu0.hotmail.com (blu0-omc2-s35.blu0.hotmail.com [65.55.111.110]) by ietfa.amsl.com (Postfix) with ESMTP id A638E21F89D3 for <l2vpn@ietf.org>; Fri, 5 Apr 2013 05:03:20 -0700 (PDT)
Received: from BLU175-W8 ([65.55.111.71]) by blu0-omc2-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 5 Apr 2013 05:03:19 -0700
X-EIP: [le4XBn0NlGq6wnbtEyfTMPdhPVgOJS/DL8TaIeQOyT4=]
X-Originating-Email: [raymond.key@hotmail.com]
Message-ID: <BLU175-W82A0EB11B8C3D56CF7AA3F4DA0@phx.gbl>
Content-Type: multipart/alternative; boundary="_470a87ee-3862-4dd5-888f-af2053aa46f5_"
From: Raymond Key <raymond.key@ieee.org>
Sender: raymond.key@hotmail.com
To: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>, "giheron@cisco.com" <giheron@cisco.com>
Subject: RE: Polling for IPR on the E-Tree Requirements draft draft-ietf-l2vpn-etree-reqt-04
Date: Fri, 05 Apr 2013 23:03:19 +1100
Importance: Normal
In-Reply-To: <CD7FCADC.7CCF2%nabil.n.bitar@verizon.com>
References: <CD7FC98C.7CCE9%nabil.n.bitar@verizon.com>, <CD7FCADC.7CCF2%nabil.n.bitar@verizon.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 05 Apr 2013 12:03:19.0993 (UTC) FILETIME=[9069E290:01CE31F5]
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2013 12:03:21 -0000

Hi WG Chairs,
I am not aware of any relevant IPR that has not been properly disclosed. Raymond Key  From: nabil.n.bitar@verizon.com
CC: giheron@cisco.com; raymond.key@ieee.org; simon.delord@gmail.com; frederic.jounay@orange.ch; huanglu@chinamobile.com; zhliu@gsta.com; manuel.paul@telekom.de; ruediger.kunze@telekom.de; nick.delregno@verizon.com; josh.rogers@twcable.com
To: l2vpn@ietf.org
Date: Thu, 4 Apr 2013 14:11:55 -0400
Subject: Polling for IPR on the E-Tree Requirements draft draft-ietf-l2vpn-etree-reqt-04

Hi,
We are polling for knowledge of any IPR that applies
 to draft-ietf-l2vpn-etree-reqt-04, Requirements for MEF E-Tree Support in L2VPN, in order to ensure that IPR has been disclosed in compliance
 with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). 
If you are listed as a document author or
 contributor,  please respond to this email whether or not you are aware of any relevant IPR that has not been properly
 disclosed. The draft will not be adopted until a response has been received from each author
 and contributor.
If you are on the l2vpn WG email list but are not listed as an author or contributor, then please explicitly respond only if you are
 aware of any IPR that has not yet been disclosed in conformance with IETF rules. The
 draft can be found at https://tools.ietf.org/html/draft-ietf-l2vpn-etree-reqt-04
This poll closes on Thursday April 11, 2013.
Thanks,Nabil & Giles

v2.23.0 | Report a Bug | By Email