Re: [Teas] Regarding IPR on draft-ietf-teas-lsp-diversity

"Zafar Ali (zali)" <zali@cisco.com> Thu, 23 June 2016 17:36 UTC

Return-Path: <zali@cisco.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 979B312D53A; Thu, 23 Jun 2016 10:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 FYU5B4hqB-Jl; Thu, 23 Jun 2016 10:36:26 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F02712D534; Thu, 23 Jun 2016 10:36:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3312; q=dns/txt; s=iport; t=1466703386; x=1467912986; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=72a8aBaVtEhb2DfT8j0lTna/7cFev8BegYlJIgJkjL0=; b=imN7BszK9djSn7iZjgJag+yNBDq0yakB38AkzL1kSFUFx2rSWFOsz9sa cjW2zeBHeI3iCendm+dJUBCd+MPLJNezTAa9b8dei+aoM3ncV8vkTEDJC 7WWA1lpHrM/mCWwkaLN7cL4FdgNVm3E8TWq1Z2+fTTsQ+XOfRdf6uDXEH 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D9AQAeHWxX/4wNJK1dgz5WfQa6NIF6FwuFdgKBLjgUAQEBAQEBAWUnhE0BAQQBAQFrBhUCAQgOCi4nCyUCBAESiDAOxxEBAQEBAQEBAQEBAQEBAQEBAQEBHoYnhE2EEhEBKIVPBZNLhTQBhgeIKYFpToQFiGiGU4kqAR42g3BuAYhuNn8BAQE
X-IronPort-AV: E=Sophos;i="5.26,517,1459814400"; d="scan'208";a="287736488"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Jun 2016 17:36:25 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u5NHaP4Q002846 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 23 Jun 2016 17:36:25 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 23 Jun 2016 13:36:24 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1104.009; Thu, 23 Jun 2016 13:36:24 -0400
From: "Zafar Ali (zali)" <zali@cisco.com>
To: Lou Berger <lberger@labn.net>, "fu.xihua@zte.com.cn" <fu.xihua@zte.com.cn>, "draft-ietf-teas-lsp-diversity@ietf.org" <draft-ietf-teas-lsp-diversity@ietf.org>, TEAS WG <teas@ietf.org>
Thread-Topic: [Teas] Regarding IPR on draft-ietf-teas-lsp-diversity
Thread-Index: AQHRv1MVaGVyS1NMpEWG3aoYiyr6+J/02ssAgALM5oD//8UoAA==
Date: Thu, 23 Jun 2016 17:36:24 +0000
Message-ID: <D391964A.17DC4C%zali@cisco.com>
References: <d0a381b8-45b4-8440-b18d-060d43fb3d44@labn.net> <e740574f-a42f-7322-8ee4-4bc97f18df3d@labn.net> <5bc08d5e-9165-012f-144f-e1ca9940ba82@labn.net>
In-Reply-To: <5bc08d5e-9165-012f-144f-e1ca9940ba82@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.8.151023
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.241.12]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <6E18DDA2A5AA08448832992A96531981@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/rYGkzpLSpU3PPPhAO0Bdi8Naew4>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-lsp-diversity
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2016 17:36:28 -0000

Lou- 

This sounds good to me.

Thanks

Regards Š Zafar





On 6/23/16, 1:06 PM, "Lou Berger" <lberger@labn.net> wrote:

>Okay, we're down to Xihua Fu.
>
>Via back channels,  I've been hearing that others have having trouble
>reaching him and he appears to no longer be active in the IETF.  Given
>this and that he's a contributor vs an author, how about we give him
>until Monday to respond and if he hasn't at that point, the Authors
>update the draft
>
>(a) To the Acknowledgements section add something like " Xihua Fu
><fu.xihua@zte.com.cn> contributed to the development of this document."
>
>(b) remove him from the Contributors section
>
>Once the update is published we can start the last call.
>
>Does anyone object to this approach?
>
>Thanks,
>Lou
>
>On 6/21/2016 6:21 PM, Lou Berger wrote:
>> getting close -- Still missing:
>>  
>>   fu.xihua at zte.com.cn
>>   Ruediger.Kunze at telekom.de
>>   Lieven.Levrau at nokia.com <http://nokia.com>
>>
>> If you have contacts with any of the three, please ask them to respond
>> to the original message!
>>
>> Thank you,
>> Lou
>>
>>
>> On 6/5/2016 1:52 PM, Lou Berger wrote:
>>> Authors, Contributors, WG,
>>>
>>> As part of the preparation for WG Last Call
>>>
>>> Are you aware of any IPR that applies to draft identified above?
>>>
>>> Please state either:
>>>
>>> "No, I'm not aware of any IPR that applies to this draft"
>>> or
>>> "Yes, I'm aware of IPR that applies to this draft"
>>>
>>> If so, has this IPR been disclosed in compliance with IETF IPR rules
>>> (see RFCs 3979, 4879, 3669 and 5378 for more details)?
>>>
>>> If yes to the above, please state either:
>>>
>>> "Yes, the IPR has been disclosed in compliance with IETF IPR rules"
>>> or
>>> "No, the IPR has not been disclosed"
>>>
>>> If you answer no, please provide any additional details you think
>>> appropriate.
>>>
>>> If you are listed as a document author or contributor please answer the
>>> above by responding to this email regardless of whether or not you are
>>> aware of any relevant IPR. This document will not advance to the next
>>> stage until a response has been received from each author and listed
>>> contributor. NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S
>>> TO LINES.
>>>
>>> If you are on the WG email list or attend WG meetings but are not
>>>listed
>>> as an author or contributor, we remind you of your obligations under
>>> the IETF IPR rules which encourages you to notify the IETF if you are
>>> aware of IPR of others on an IETF contribution, or to refrain from
>>> participating in any contribution or discussion related to your
>>> undisclosed IPR. For more information, please see the RFCs listed above
>>> and
>>> http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
>>>
>>> Thank you,
>>> TEAS WG Chairs
>>>
>>> PS Please include all listed in the headers of this message in your
>>> response.
>>>
>>>
>>>
>>> _______________________________________________
>>> Teas mailing list
>>> Teas@ietf.org
>>> https://www.ietf.org/mailman/listinfo/teas
>>>
>>
>> _______________________________________________
>> Teas mailing list
>> Teas@ietf.org
>> https://www.ietf.org/mailman/listinfo/teas
>>
>
>