Re: [Lsr] [E] Work Group Last Call IPR Call for 'Dynamic-Flooding on Dense Graphs" - draft-ietf-lsr-dynamic-flooding

"Jalil, Luay" <luay.jalil@verizon.com> Wed, 22 February 2023 21:52 UTC

Return-Path: <luay.jalil@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 C5A57C14F726 for <lsr@ietfa.amsl.com>; Wed, 22 Feb 2023 13:52:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizon.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZrThAzytcSII for <lsr@ietfa.amsl.com>; Wed, 22 Feb 2023 13:52:07 -0800 (PST)
Received: from mx0b-0024a201.pphosted.com (mx0b-0024a201.pphosted.com [148.163.153.92]) (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 B9B86C15154C for <lsr@ietf.org>; Wed, 22 Feb 2023 13:52:07 -0800 (PST)
Received: from pps.filterd (m0115888.ppops.net [127.0.0.1]) by mx0b-0024a201.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 31MImkLD033992 for <lsr@ietf.org>; Wed, 22 Feb 2023 16:52:07 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon.com; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : cc : content-type; s=corp; bh=XV7fYqZ38aw6Csn76z+6J+SuAEjjeBulLwOh9PoVjqE=; b=nw7kw5e3CKMAzufu2V+rtrULzmvGcnfO50usq/tPbaUB2WuP2iCIjWF7klVZ9L3czkoI V2RAo70JpBTsMUUo5/4hhZRGL+ViOntRLdH8cRvK1eR2Zp4HbhyGLbBR5o4cfcRVwAzL ibKqyEWuCghytwIuIdqMBUSX4/2bXqgeCw0=
Received: from mail-oi1-f197.google.com (mail-oi1-f197.google.com [209.85.167.197]) by mx0b-0024a201.pphosted.com (PPS) with ESMTPS id 3ntushf9vm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <lsr@ietf.org>; Wed, 22 Feb 2023 16:52:06 -0500
Received: by mail-oi1-f197.google.com with SMTP id v133-20020acaac8b000000b0037fa06d71cfso3009188oie.5 for <lsr@ietf.org>; Wed, 22 Feb 2023 13:52:06 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=XV7fYqZ38aw6Csn76z+6J+SuAEjjeBulLwOh9PoVjqE=; b=r+YpzTGpgeG4Li4FzmoGMwaQJ7rxBWBVuJwsZwcNkixI77ILAEjjhfnYU5vN8bRNEX +oHZ7J0Iu9Hir1PemYy85jpzrjfgFhyzdQz+MwV5bPaWvMy3/f5+HagiFYHdXKpAD7kT ryV10vqwEWxO4O5Hyr4j2XWHMCaL+/+zWmN2jbI3wvZxuqBUjQu8STR7RTmRztO68YOk MjC6volKY558oR7LKTBTuIPwHb/u9GdVo/TPVECw8n8YDFgSCix09jJNynrEURnseTkW z76zgZ/CPopqoKH04zcfZMAUh843a5RWnuEItNrNlpb3fCWVIrbLwD+R8bCgZ2iatmUs 4H7Q==
X-Gm-Message-State: AO0yUKXVBuVNcNjlLTMYIBerxF5iEnPNXNrpEpVBnxjFJb9KHRCw9dOr Rnzm6VpGfOmkcZDOhpIxwMLZQfqEpf72coefIyBdUOSv9Ak1Q4o3i6vJHEbmDhNtS5i5l70tfkf DgsToitgm2tHzI38QRrpr7acEabc=
X-Received: by 2002:a05:6870:e250:b0:16e:4544:bedd with SMTP id d16-20020a056870e25000b0016e4544beddmr2167856oac.3.1677102725888; Wed, 22 Feb 2023 13:52:05 -0800 (PST)
X-Google-Smtp-Source: AK7set/53ILNH+RlRuBOdeq4HVuIZ+LzPK4AVWMqOsTsfvjmSQx9YgSfpKTKulYqvVMpNsxpe4FNbm6pAzw5HDJo7bY=
X-Received: by 2002:a05:6870:e250:b0:16e:4544:bedd with SMTP id d16-20020a056870e25000b0016e4544beddmr2167851oac.3.1677102725315; Wed, 22 Feb 2023 13:52:05 -0800 (PST)
MIME-Version: 1.0
References: <029E35E1-F30F-4612-8F40-0A33E0B86ED3@gmail.com>
In-Reply-To: <029E35E1-F30F-4612-8F40-0A33E0B86ED3@gmail.com>
From: "Jalil, Luay" <luay.jalil@verizon.com>
Date: Wed, 22 Feb 2023 15:51:29 -0600
Message-ID: <CAO8-O7oFguLdXim7BNf9Ooietu00rS=a+dMhGZo4MPqVnvLTWQ@mail.gmail.com>
To: Acee Lindem <acee.ietf@gmail.com>
Cc: draft-ietf-lsr-dynamic-flooding@ietf.org, lsr <lsr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000031d90205f550e809"
X-mailroute: internal
X-Proofpoint-GUID: 5i0Ma_rAt3LjhIOSr8xt5ZAvVfSwl0-c
X-Proofpoint-ORIG-GUID: 5i0Ma_rAt3LjhIOSr8xt5ZAvVfSwl0-c
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/7HMd1dlDHLhY3HIjx0fLZQyV4tM>
Subject: Re: [Lsr] [E] Work Group Last Call IPR Call for 'Dynamic-Flooding on Dense Graphs" - draft-ietf-lsr-dynamic-flooding
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 22 Feb 2023 21:52:11 -0000

Acee,
I'm not aware of any IPR that applies to
draft-ietf-lsr-dynamic-flooding-11.txt

Regards,
*Luay*


On Wed, Feb 22, 2023 at 3:46 PM Acee Lindem <acee.ietf@gmail.com> wrote:

> Co-Authors,
>
> Are you aware of any IPR that applies to
> draft-ietf-lsr-dynamic-flooding-11.txt?
> If so, has this IPR been disclosed in compliance with IETF IPR rules  (see
> RFCs 3979, 4879, 3669 and 5378 for more details).
>
> There are a few IPR statements already -
> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_ipr_search_-3Fsubmit-3Ddraft-26id-3Ddraft-2Dietf-2Dlsr-2Ddynamic-2Dflooding&d=DwIFAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&m=u3jJ5z4k0393ILN6Hmba_ayg81dbNxGxXJXejqJQtjSA8KC8ciFUJJWAAEh_yWpa&s=X_ug6CDVIUCCmtc_uT6sRtTErK73KomNR1jYxkuo3_I&e=
>
> 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.
>
> Also, since there are nine authors, it would be great if you could reduce
> the author list and make
> the others contributors (which still requires an IPR response).
>
> Thanks,
> Acee