Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 IPR Poll

"Toy, Mehmet" <mehmet.toy@verizon.com> Tue, 02 June 2020 02:22 UTC

Return-Path: <mehmet.toy@verizon.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 2F3E13A0846 for <lsr@ietfa.amsl.com>; Mon, 1 Jun 2020 19:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.089
X-Spam-Level:
X-Spam-Status: No, score=-2.089 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizon.com header.b=KyWaEHFj; dkim=pass (2048-bit key) header.d=verizon-com.20150623.gappssmtp.com header.b=GUT15wmW
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 9wFA7pYTcTuC for <lsr@ietfa.amsl.com>; Mon, 1 Jun 2020 19:22:03 -0700 (PDT)
Received: from mx0a-0024a201.pphosted.com (mx0a-0024a201.pphosted.com [148.163.149.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E821E3A0845 for <lsr@ietfa.amsl.com>; Mon, 1 Jun 2020 19:22:03 -0700 (PDT)
Received: from pps.filterd (m0114267.ppops.net [127.0.0.1]) by mx0a-0024a201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 0522JEVM085640 for <lsr@ietfa.amsl.com>; Mon, 1 Jun 2020 22:22:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon.com; h=mime-version : from : date : message-id : subject : to : cc : content-type; s=corp; bh=lWd7caWlZkVspSKRImkfTa59EQKAqZIZXMeJ7g8Tu6c=; b=KyWaEHFjKyuQ6caKFNBPWpZ4NeQrLKGwq0RrxGSjp9/T55Dd0woGA8nfB++zysdZdXTk e0oJRoVQkXkkRLFlCCracpSJt0WWcmj5/CRLGsi5NccNfXaKrCt7mLMbNX0vSfakb5Ld siKGu4JEQP49M+9J7NQBC9+MtluZIKfWCB4=
Received: from mail-qv1-f70.google.com (mail-qv1-f70.google.com [209.85.219.70]) by mx0a-0024a201.pphosted.com with ESMTP id 31bhyyx2a9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <lsr@ietfa.amsl.com>; Mon, 01 Jun 2020 22:22:01 -0400
Received: by mail-qv1-f70.google.com with SMTP id w6so2080550qvj.4 for <lsr@ietfa.amsl.com>; Mon, 01 Jun 2020 19:22:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=lWd7caWlZkVspSKRImkfTa59EQKAqZIZXMeJ7g8Tu6c=; b=GUT15wmWiismgQ9ZCruQVZqgI3fUnhdStj1NUpBQ54A7UEx+r12aRmK0JsilI6fhaz OUOMYVVba3QJAzFMuh69Ba9SiMjv2mK3+D9MliaGZfXZWMOoiiFoiIp1wwYadl/YZ5Kz 6UePLG2WqF7tHwqi8cktDNJklDU1phWOcJuXmpVMbUWMdiKqytgngtISd9Y4uPAR1ADh leEwrIUUtq6XmR4/1++k+XF7vHtNmBpwoeFntEFefUld+6Tx6ghHqWhiHwW7Vf6RbQ0/ x65/FIkvKQrB6m2JptLdSR4zEuC8iyD3lCHk3HDHfu6h/8EstsoWZvd+/ez6XGPDagU6 R9vQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=lWd7caWlZkVspSKRImkfTa59EQKAqZIZXMeJ7g8Tu6c=; b=Y0TL/UK+sR7kXd5/eq9HO69FjZW0JRqOBw+hn9fUpS0sG7K28fGmjvlRkY/HH15Ph4 a92/96z1yqXk2Udm9TqlnbirMXFqcXUy3OCapgNtIPXgElxZwlsTMDRnfGR+yR0F3kE8 hYiENCwJeWckr3XuGwp9t8wwdL3lXGj4VPaIaX6XgiBSfBITMLcNJVGoUQXvai31Yv/b 9E4Is7J8JvEgemFMKLGiMyN8MBHN8e951nXcdOzchldVF41xiSvaIT1LfmOjrJhvTl2E RescwR0kc4Qarr5ouatjqwDHpaw8doKBZiZGj2yMCOJlrQVDpYzNsoD062nex8lo7jCd CISg==
X-Gm-Message-State: AOAM5339iv0GgP0nz+2PUGn/2xUiwY9Sap9sA4iyhPZxRMRBl4t4SUlQ 7AFtEAYhibNjzNZl/NrWknD+QlsQ+UhJy/HTlXWIp69Se6965Is3AJS+39WmpRXuJkUUaPylzK8 /qu5BWY/6pwNswZkwdWAvxYv0/9Y=
X-Received: by 2002:a0c:9e53:: with SMTP id z19mr23581253qve.47.1591064519245; Mon, 01 Jun 2020 19:21:59 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJzDqEitQJjHq4+915k+GGtyXto6DOXLLS3pj+KmDMj6fbHrxaK+xhKtoe9qKuYvfj4oV9wr0fKlcXBXsXRMjXs=
X-Received: by 2002:a0c:9e53:: with SMTP id z19mr23581220qve.47.1591064518123; Mon, 01 Jun 2020 19:21:58 -0700 (PDT)
MIME-Version: 1.0
From: "Toy, Mehmet" <mehmet.toy@verizon.com>
Date: Mon, 1 Jun 2020 22:21:47 -0400
Message-ID: <CAKr6JWt+Zz=o_tAqNm2Y+tS9wMh+zggR_+oN_zUQpYaJ926rww@mail.gmail.com>
To: acee@cisco.com
Cc: lsr@ietfa.amsl.com
Content-Type: multipart/alternative; boundary="0000000000006af2ba05a71093c2"
X-mailroute: internal
X-Proofpoint-Spam-Details: rule=out_spam_notspam policy=out_spam score=0 mlxscore=0 bulkscore=0 malwarescore=0 cotscore=-2147483648 suspectscore=3 impostorscore=0 clxscore=1011 mlxlogscore=396 spamscore=0 priorityscore=1501 phishscore=0 adultscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2006020009
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/HKXal6mM1cuS3KKNikD8f-2rs3s>
Subject: Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 IPR Poll
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Jun 2020 02:22:05 -0000

Acee,

I am not aware of any IPR that applies to
draft-cc-lsr-flooding-reduction-08.
Thanks

Mehmet


On Fri, May 15, 2020 at 12:47 PM Acee Lindem (acee) <acee@cisco.com>
<&lt;acee@cisco.com&gt;> wrote:

> Authors,
>
>
>
> Are you aware of any IPR that applies
> to draft-cc-lsr-flooding-reduction-08.txt.
>
>
>
> 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