Re: IPR Claims related to draft-ietf-rtgwg-mofrr

"Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com> Fri, 14 March 2014 18:28 UTC

Return-Path: <wim.henderickx@alcatel-lucent.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFD11A017C for <rtgwg@ietfa.amsl.com>; Fri, 14 Mar 2014 11:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] 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 45RGKb5jVlJa for <rtgwg@ietfa.amsl.com>; Fri, 14 Mar 2014 11:27:58 -0700 (PDT)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 36B931A016F for <rtgwg@ietf.org>; Fri, 14 Mar 2014 11:27:57 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s2EIRmqQ015595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 14 Mar 2014 13:27:49 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s2EIRl6q010532 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 14 Mar 2014 19:27:47 +0100
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.10]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Fri, 14 Mar 2014 19:27:47 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "draft-ietf-rtgwg-mofrr@tools.ietf.org" <draft-ietf-rtgwg-mofrr@tools.ietf.org>
Subject: Re: IPR Claims related to draft-ietf-rtgwg-mofrr
Thread-Topic: IPR Claims related to draft-ietf-rtgwg-mofrr
Thread-Index: AQHPPz9L2w2bbTUN3EO+tBGO/aSUWprgUjfQgAAvgAA=
Date: Fri, 14 Mar 2014 18:27:46 +0000
Message-ID: <CF48B31D.B75EC%wim.henderickx@alcatel-lucent.com>
References: <CF480018.50946%aretana@cisco.com> <10099_1394789773_5322CD8D_10099_9050_1_53C29892C857584299CBF5D05346208A07118F6A@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <10099_1394789773_5322CD8D_10099_9050_1_53C29892C857584299CBF5D05346208A07118F6A@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [135.239.27.39]
Content-Type: multipart/alternative; boundary="_000_CF48B31DB75ECwimhenderickxalcatellucentcom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/6RcGVbP4oH7m8IL3C9golxC50cc
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Mar 2014 18:28:00 -0000

I am not aware of IPR

From: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Date: Friday 14 March 2014 10:36
To: "Alvaro Retana (aretana)" <aretana@cisco.com<mailto:aretana@cisco.com>>, "draft-ietf-rtgwg-mofrr@tools.ietf.org<mailto:draft-ietf-rtgwg-mofrr@tools.ietf.org>" <draft-ietf-rtgwg-mofrr@tools.ietf.org<mailto:draft-ietf-rtgwg-mofrr@tools.ietf.org>>
Cc: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: IPR Claims related to draft-ietf-rtgwg-mofrr

Hi,

I’m not aware of any non disclosed relevant IPR.

Speaking of disclosed IPR, http://tools.ietf.org/html/draft-ietf-rtgwg-mofrr does not indicate the below IPR. I assume that this is because the IETF datatracker does not know that draft-ietf-rtgwg-mofrr-00 replaces draft-karan-mofrr-02  (which has the IPR disclosed).

Thanks
Bruno


From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Alvaro Retana (aretana)
Sent: Friday, March 14, 2014 5:39 AM
To: draft-ietf-rtgwg-mofrr@tools.ietf.org<mailto:draft-ietf-rtgwg-mofrr@tools.ietf.org>
Cc: rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: IPR Claims related to draft-ietf-rtgwg-mofrr

Hi!

In parallel to the WGLC for this draft, I want to formally ask the authors (and contributors) to please respond to this message indicating whether or not you are aware of any relevant IPR beyond what has already been disclosed.  The draft will not progress (pending the results of the WGLC) until we have received a response from each author/contributor.

http://datatracker.ietf.org/ipr/search/?option=document_search&id=draft-ietf-rtgwg-mofrr

Thanks!

Alvaro.


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.