IETF Logo Mail Archive

Re: IPR call for draft-rtgwg-segment-routing-ti-lfa

Francois Clad <fclad.ietf@gmail.com> Thu, 16 November 2023 08:14 UTC

Return-Path: <fclad.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01A69C14CF01; Thu, 16 Nov 2023 00:14:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (2048-bit key) header.d=gmail.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 N2Xq_B0CKnnk; Thu, 16 Nov 2023 00:14:14 -0800 (PST)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23159C14E513; Thu, 16 Nov 2023 00:14:14 -0800 (PST)
Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-9c603e235d1so70930266b.3; Thu, 16 Nov 2023 00:14:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700122452; x=1700727252; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lhldAmfF1uRxUSVsmoqeb9wPRErMBNO814sjdwU/B00=; b=kYd5vlGrniTFVFjB2i/dtKiISDEoRMJPGR+qNbWtMnURMzL4wsczikJsbpo+6FhnKk h+/K/Rgcht3DWl2IUR65GbAKi70bZi3ObHoZPsDILpCALmlgNVtQGOLHghotxoVUVZBf RSpcLPKHeNvYTgNOiR8QycyFOh6s04N/c08NeqmqqFbTzIr+iyZvAjjxKNLkw9BNuDGF qY8O4h9Mm9pOHf7RJb7X9EqGnyvHkds+u1s1Aed96wXnCFngOz26bRHDvp5I/vlmko4x g/SIa5GdXGBZG+qoBnDjeenT9TJ7uR1V9Nvh9bRsyslERPWYy3RwBf9pFXa3lqy+VFu5 OWTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700122452; x=1700727252; 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=lhldAmfF1uRxUSVsmoqeb9wPRErMBNO814sjdwU/B00=; b=Qg+VN2L5EHvP41asCljVTBlS5mpDK+SJRp4Iad1BHv6kFmi7PD0JyahwMxXWvLzA9r Bm+bC8YlroPmiwVs1i1hdk1edKYxdzhkQpfrtezcesuLCNO5CCT8R8/SeWOY2JfSwClV s/RKsZ1wdfQNzlQT0eLrUL1FNLmF8x9h8nRa/UlpXwWt1RwsUpLQQYDtaa4G/toLpbTe +gGPKoGcMf1Z4lln3vZ/uYRGgFZvRV2dge/ukGHD2fild4C9l0r6dpXkXpxCy8lyc8FC 69q0LAwro56lk5+24oH2c/l5tQInActr/chbdFlVARtC9BzVN5J0ZDnQmM+jiRgj9Fo2 33ww==
X-Gm-Message-State: AOJu0YweyUF7bs8NC97AS6ffxMYlUSdwq+LJM1tmiMOxho3r6C3pbgFW lcdqlxhakZGf8XBQu5kb9VvC7VpER81wakgHq0CIYxMj9e7ZH0g=
X-Google-Smtp-Source: AGHT+IFxSPm9jI3Xs+2m/tZ7nwszwapca6SzKRaRca+pA94bZatdVqzYFDCpGcOxP/7I1qXjDr3uf+B416YcB0Rq2YY=
X-Received: by 2002:a17:906:1342:b0:9c4:54c6:8030 with SMTP id x2-20020a170906134200b009c454c68030mr11431540ejb.6.1700122451545; Thu, 16 Nov 2023 00:14:11 -0800 (PST)
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Thu, 16 Nov 2023 02:14:10 -0600
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Thu, 16 Nov 2023 02:14:07 -0600
Mime-Version: 1.0 (Mimestream 1.1.5)
References: <CABY-gONzwDdrpmqCTD0_3qC6jSinqY+BiuJ+LP_m5jgtC+hrpw@mail.gmail.com>
In-Reply-To: <CABY-gONzwDdrpmqCTD0_3qC6jSinqY+BiuJ+LP_m5jgtC+hrpw@mail.gmail.com>
From: Francois Clad <fclad.ietf@gmail.com>
Date: Thu, 16 Nov 2023 02:14:10 -0600
Message-ID: <CAHT6gR_f71zhc9PZ5RENrWE06LHeYe8A925B4y6=3EdJ6yjdiw@mail.gmail.com>
Subject: Re: IPR call for draft-rtgwg-segment-routing-ti-lfa
To: Yingzhen Qu <yingzhen.ietf@gmail.com>
Cc: RTGWG <rtgwg@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cc91c7060a409ab8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/eUs6_TeFRHlLdTDXW6IZ98vzy_c>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 16 Nov 2023 08:14:18 -0000

 Hi Yingzhen,

I am not aware of any undisclosed IPR applicable to this document.

Cheers,
Francois

On Nov 14, 2023 at 19:23:06, Yingzhen Qu <yingzhen.ietf@gmail.com> wrote:

> Hi,
>
> This is an IPR call for draft-ietf-rtgwg-segment-routing-ti-lfa
> (draft-ietf-rtgwg-segment-routing-ti-lfa-11 - Topology Independent Fast Reroute using Segment Routing <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-segment-routing-ti-lfa/>)
>
> There is an existing IPR disclosure:
> <IPR Details - Cisco's Statement about IPR related to draft-bashandy-rtgwg-segment-routing-ti-lfa (ietf.org) <https://datatracker.ietf.org/ipr/3068/>>
>
> The authors and contributors please respond to this IPR call.
>
> 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 3669, 5378 and 8179 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.
>
> The WG Last Call will only start after all authors have sent in their
> IPR statements to the list.
>
> Thanks,
> Yingzhen
>
>
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>

v2.23.0 | Report a Bug | By Email