RE: IPR call for draft-rtgwg-segment-routing-ti-lfa
"Voyer, Daniel" <daniel.voyer@bell.ca> Tue, 14 November 2023 19:56 UTC
Return-Path: <prvs=675a5b47e=daniel.voyer@bell.ca>
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 420C4C151087; Tue, 14 Nov 2023 11:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.803
X-Spam-Level:
X-Spam-Status: No, score=-2.803 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_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 (2048-bit key) header.d=bell.ca
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 B87dUhp_q6Dx; Tue, 14 Nov 2023 11:56:42 -0800 (PST)
Received: from ESA2-Wyn.bell.ca (esa2-wyn.bell.ca [67.69.243.180]) (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 D8364C15C299; Tue, 14 Nov 2023 11:56:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bell.ca; i=@bell.ca; q=dns/txt; s=ESAcorp; t=1699991799; x=1731527799; h=from:to:date:message-id:references:in-reply-to: mime-version:subject; bh=+W8Ng/B9Np6g4YQ9zYZ19wxudT01Em/BSjfg97XFb6o=; b=b/Y5RSp06wjjHyfUnzwy4UlKcniO4LxkxIf5kKtQtW7R/FbiNAEB4wU5 TH4uxnHs1/kN7sVw3LGRc996uT8x+fjRQpjvsT5QwSecCdof1tZs4wqJT Q2Su0sw/guOInPLLwYvJr+rXCnpvN0s4G9DiW6/r0lGxTeCoOeE+407/D JGyqtoVZ63Q9dO5Es7wq9BBLq/oB9PGRFGM4a+DEb+2BT/TxTEPQFz8tr +5Xwc3+U/C017uG10pg+J98FdMloayB0lNeAll/CHnzG7rylDsW/BAesg 09OLTOYmfGdWum3UqvnLpbHnNpyfllp5lCr4LjSG/Xw3irpEfsM2dRvha g==;
Subject: RE: IPR call for draft-rtgwg-segment-routing-ti-lfa
Received: from dm5czo-d00.bellca.int.bell.ca (HELO DG4MBX03-WYN.bell.corp.bce.ca) ([198.235.102.32]) by esa02corp-wyn.bell.corp.bce.ca with ESMTP; 14 Nov 2023 14:56:37 -0500
Received: from DG4MBX01-WYN.bell.corp.bce.ca (142.182.18.27) by DG4MBX03-WYN.bell.corp.bce.ca (142.182.18.29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Tue, 14 Nov 2023 14:56:37 -0500
Received: from DG4MBX01-WYN.bell.corp.bce.ca ([fe80::cc16:e2a3:3b5b:a2cf]) by DG4MBX01-WYN.bell.corp.bce.ca ([fe80::cc16:e2a3:3b5b:a2cf%4]) with mapi id 15.01.2507.027; Tue, 14 Nov 2023 14:56:37 -0500
From: "Voyer, Daniel" <daniel.voyer@bell.ca>
To: Yingzhen Qu <yingzhen.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>
Thread-Topic: [EXT]IPR call for draft-rtgwg-segment-routing-ti-lfa
Thread-Index: AQHaFyeo2bx1e+LQW0qr93djZkC6Q7B6OwqA
Date: Tue, 14 Nov 2023 19:56:37 +0000
Message-ID: <7F234AE6-88A1-4CFF-BAA0-224497021C15@bell.ca>
References: <CABY-gONzwDdrpmqCTD0_3qC6jSinqY+BiuJ+LP_m5jgtC+hrpw@mail.gmail.com>
In-Reply-To: <CABY-gONzwDdrpmqCTD0_3qC6jSinqY+BiuJ+LP_m5jgtC+hrpw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.78.23102801
x-originating-ip: [172.28.239.73]
Content-Type: multipart/alternative; boundary="_000_7F234AE688A14CFFBAA0224497021C15bellca_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/Ceg0qlAsYluhlR7Ou21vGoTpH2k>
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: Tue, 14 Nov 2023 19:56:46 -0000
No, I'm not aware of any IPR that applies to this draft. Cheers, Dan From: rtgwg <rtgwg-bounces@ietf.org> on behalf of Yingzhen Qu <yingzhen.ietf@gmail.com> Date: Tuesday, November 14, 2023 at 1:23 PM To: RTGWG <rtgwg@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org> Subject: [EXT]IPR call for draft-rtgwg-segment-routing-ti-lfa 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
- IPR call for draft-rtgwg-segment-routing-ti-lfa Yingzhen Qu
- Re: IPR call for draft-rtgwg-segment-routing-ti-l… Ahmed Bashandy
- RE: IPR call for draft-rtgwg-segment-routing-ti-l… Voyer, Daniel
- RE: IPR call for draft-rtgwg-segment-routing-ti-l… bruno.decraene
- RE: IPR call for draft-rtgwg-segment-routing-ti-l… slitkows.ietf
- RE: IPR call for draft-rtgwg-segment-routing-ti-l… Clarence Filsfils (cfilsfil)
- RE: IPR call for draft-rtgwg-segment-routing-ti-l… Pablo Camarillo (pcamaril)
- Re: IPR call for draft-rtgwg-segment-routing-ti-l… Francois Clad
- Re: IPR call for draft-rtgwg-segment-routing-ti-l… Pierre Francois