IETF Logo Mail Archive

RE: IPR call for draft-ietf-l2vpn-evpn-07

"Bitar, Nabil N" <nabil.n.bitar@verizon.com> Fri, 30 May 2014 09:58 UTC

Return-Path: <nabil.n.bitar@verizon.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E7691A084B for <l2vpn@ietfa.amsl.com>; Fri, 30 May 2014 02:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 K_u7MoCy0THf for <l2vpn@ietfa.amsl.com>; Fri, 30 May 2014 02:58:15 -0700 (PDT)
Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com [199.249.25.209]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF8E61A07A5 for <l2vpn@ietf.org>; Fri, 30 May 2014 02:58:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verizon.com; i=nabil.n.bitar@verizon.com; q=dns/txt; s=corp; t=1401443891; x=1432979891; h=from:to:date:subject:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=Xo9MCDCwxJIs5l7DJbxChwhv8+sYXLiQ1262V0V0vXE=; b=HbgDmvASje8wHNzu+B88HFOiMYdcCJtJt8hFGPf7HEJFS+BcPyTGkAML 2n/vFELmOUbw4bD7PnmU8A9Ea3PpAeNZkUM8uQphGEBE1Km7k12YfWYdv +LD/ttf1udfOVX6BxPONURVQuJDQYdE2EU/KEKOl7pZDJZAAOfK/xqe8+ w=;
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by omzsmtpe02.verizonbusiness.com with ESMTP; 30 May 2014 09:58:10 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
X-IronPort-AV: E=Sophos;i="4.98,940,1392163200"; d="scan'208";a="758183649"
Received: from fldp1lumxc7hb03.verizon.com (HELO FLDP1LUMXC7HB03.us.one.verizon.com) ([166.68.75.86]) by fldsmtpi01.verizon.com with ESMTP; 30 May 2014 09:58:09 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([166.68.45.45]) by FLDP1LUMXC7HB03.us.one.verizon.com ([166.68.75.86]) with mapi; Fri, 30 May 2014 05:58:09 -0400
To: Giles Heron <giles.heron@gmail.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Fri, 30 May 2014 05:56:47 -0400
Subject: RE: IPR call for draft-ietf-l2vpn-evpn-07
Thread-Topic: IPR call for draft-ietf-l2vpn-evpn-07
Thread-Index: Ac97PMSRyUpRJdxpSx2JO/aCEvKyXQAsLPEC
Message-ID: <EE3DB9B68D417942A9B1863918E159FA11E19BFB16@FLDP1LUMXC7V63.us.one.verizon.com>
References: <AEFFC653-DECB-41B5-980C-35DF2958E935@gmail.com>
In-Reply-To: <AEFFC653-DECB-41B5-980C-35DF2958E935@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/Jch5CQNW9WJqbZYMc0MdAjp3ysU
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <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, 30 May 2014 09:58:16 -0000

Hi,
I am not aware of any IPR related to this draft that has not been properly disclosed.

Thanks,
Nabil
____________________________
From: Giles Heron [giles.heron@gmail.com]
Sent: Thursday, May 29, 2014 8:51 AM
To: l2vpn@ietf.org
Cc: Bitar, Nabil N
Subject: IPR call for draft-ietf-l2vpn-evpn-07

Hi,

this email initiates an IPR call for:

http://tools.ietf.org/html/draft-ietf-l2vpn-evpn-07

would all authors please respond to this email indicating whether there is any IPR they are aware of which has not already been disclosed to the IETF.

Likewise if anyone else is aware of any IPR that has not already been disclosed to the IETF would you please respond to this email.

And would everyone please take a look at the IPR that has already been disclosed - especially in view of the fact that one of those disclosures only happened this month:

https://datatracker.ietf.org/ipr/search/?option=document_search&id=draft-ietf-l2vpn-evpn

Please respond to the list if you have any concerns about the impact of any of this IPR on the suitability of this draft for adoption as a standards-track RFC.

this IPR call closes on Thursday 10th June 2014.

Giles

v2.8.7 | Report a Bug | By Email