Re: [Lsr] IPR for IS-IS and OSPF Flex Algorithm Drafts

Peter Psenak <ppsenak@cisco.com> Tue, 17 April 2018 19:00 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5600E12E8D5; Tue, 17 Apr 2018 12:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 PgAt5byAEtIM; Tue, 17 Apr 2018 12:00:15 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5441612E88C; Tue, 17 Apr 2018 12:00:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1018; q=dns/txt; s=iport; t=1523991614; x=1525201214; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=E0FrlP7Jk9/JI7K5OLkfxFjsMJrH9xGY/GnRvZLj3/c=; b=VeA0JF9+eV34yifQsPt7agNaOOR5XeH+ulng2VrwxS38BOtdzIgdSbq4 kY8xsahP27oPAZU6foEIbYBX4WGgpH+R92wxxdvtyAAuha2AyfcsVXLNf YFrjvYpKTMXxqvhztnoXYMT5I7oeKkCDSNSvkqoQgro4WAK1UNLzZYta5 A=;
X-IronPort-AV: E=Sophos;i="5.48,464,1517875200"; d="scan'208";a="3198210"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Apr 2018 19:00:12 +0000
Received: from [10.60.140.54] (ams-ppsenak-nitro5.cisco.com [10.60.140.54]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w3HJ0BCB016649; Tue, 17 Apr 2018 19:00:11 GMT
Message-ID: <5AD6443B.7080607@cisco.com>
Date: Tue, 17 Apr 2018 21:00:11 +0200
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Acee Lindem (acee)" <acee@cisco.com>, "draft-hegdeppsenak-isis-sr-flex-algo@ietf.org" <draft-hegdeppsenak-isis-sr-flex-algo@ietf.org>, "draft-ppsenak-ospf-sr-flex-algo@ietf.org" <draft-ppsenak-ospf-sr-flex-algo@ietf.org>
CC: "lsr@ietf.org" <lsr@ietf.org>
References: <943C5E80-10F5-4EEE-A2F0-EB1C1658AEAB@cisco.com>
In-Reply-To: <943C5E80-10F5-4EEE-A2F0-EB1C1658AEAB@cisco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/8ZZ4oP-PL49zJUNMrNItgmJRlT8>
Subject: Re: [Lsr] IPR for IS-IS and OSPF Flex Algorithm Drafts
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2018 19:00:18 -0000

Hi Acee,

there is pending IPR and the formal IETF IPR Disclosure will be filed soon.

thanks,
Peter



On 17/04/18 17:16 , Acee Lindem (acee) wrote:
> Authors,
>
> Are you aware of any IPR that applies to draft-hegdeppsenak-isis-sr-algo
> and draft-ppsenak-ospf-sr-flex-algo?
>
> If so, has this IPR 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 regardless of whether or not you are aware of any relevant
> IPR. *The response needs to be sent to the LSR WG mailing list.* The
> document will not advance to the next stage until a response has been
> received from each author and contributor.
>
> If you are on the LSR 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.
>
> Thanks,
>
> Acee
>