RE: IPR call for draft-rtgwg-segment-routing-ti-lfa
slitkows.ietf@gmail.com Wed, 15 November 2023 13:23 UTC
Return-Path: <slitkows.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 EEA91C14CEFF; Wed, 15 Nov 2023 05:23:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 3fA44kwvMIcx; Wed, 15 Nov 2023 05:23:36 -0800 (PST)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 0FA4FC14CE55; Wed, 15 Nov 2023 05:23:36 -0800 (PST)
Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-53e2308198eso10394823a12.1; Wed, 15 Nov 2023 05:23:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700054614; x=1700659414; darn=ietf.org; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=Ip1iFbYu3kVhreKTasoNTaMLENuWLunheIQ1wLWIMgQ=; b=O2treRVm77K71siPxyO9h/lIpcUGmuZ7/QerJO+poZOVUZHA0tYU2G/rSrKc48gCSW c0yJEnJdLzA+UuDlJgRfJMVT/SuWarHiKefAtTfupNGNoTDroA8seFvv0cDneIK3LhVC KEYwrxdQ06gW4+0hVvUdFNdn+zx5dvlq6vtksN95lRfQpVZTirSTEpfKdnj0TTo3cG0c y0iTbEXGQ1H1jfc2vbpk+waw/lv8v9cElTG450uYp0hLzBWgN7gHK1nc8njMFWmjEFwP 6aWEXbaKuq+Bj8RrUKS0bajz0W0sK2EUqzBUGddFqCUtMnZvk1HUcESDxsLIT+3+5baw KsmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700054614; x=1700659414; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Ip1iFbYu3kVhreKTasoNTaMLENuWLunheIQ1wLWIMgQ=; b=ZHiUP/TVejWUe8OQxuIGCw1o42rI+/+U05+kDlXlSMmy1Zj4Q2CgfBhg8h8nyn5B1U 9pxlJA1Ltmav7bAAuYqsWC7adRUI+s+gFufyyjg6CJxFFK5XFK/AMwI0dRj5SYX1QaKO /sz3RNJMVsjgiKaxIP/rrawODaSEeTM4WG76tkMOJgOdLIa9dtdX97TOIvS5U1AOsQ2q BNbbF3J7TbKU67SV27A3L6XJ5/HfZGiKyEe4oThDYVomQzZ5faeNDUcB20XjV/AJ4zAU 96gqEIqbHA/Gi3sFaEFilq+1+MQrMGxj9iIVtTAhYJXSd8OLS5nAXTeo+bFVPe/838L0 xCxg==
X-Gm-Message-State: AOJu0Yz45fTmuFvGggrknzn8PRaclHc552YpR/IU+PpGpDOPhq7m17IT 0lRJNimJQ1o+yd6kkUTLiw==
X-Google-Smtp-Source: AGHT+IGmyqK/i46HpCwLEeYOoV+yovLEtTbwxLZd++8uISTmaVS8cwOWG5ul5O/tahlGC+pTazMP2Q==
X-Received: by 2002:a05:6402:38e:b0:53d:ab75:6074 with SMTP id o14-20020a056402038e00b0053dab756074mr9257045edv.16.1700054613656; Wed, 15 Nov 2023 05:23:33 -0800 (PST)
Received: from CSCOWPF2QW8Y3 ([173.38.220.46]) by smtp.gmail.com with ESMTPSA id u27-20020a50c05b000000b0053de19620b9sm6684713edd.2.2023.11.15.05.23.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Nov 2023 05:23:33 -0800 (PST)
From: slitkows.ietf@gmail.com
To: bruno.decraene@orange.com, 'Yingzhen Qu' <yingzhen.ietf@gmail.com>
Cc: 'RTGWG' <rtgwg@ietf.org>, 'rtgwg-chairs' <rtgwg-chairs@ietf.org>
References: <CABY-gONzwDdrpmqCTD0_3qC6jSinqY+BiuJ+LP_m5jgtC+hrpw@mail.gmail.com> <AS2PR02MB88395E687C8D4CDD5CEAE895F0B1A@AS2PR02MB8839.eurprd02.prod.outlook.com>
In-Reply-To: <AS2PR02MB88395E687C8D4CDD5CEAE895F0B1A@AS2PR02MB8839.eurprd02.prod.outlook.com>
Subject: RE: IPR call for draft-rtgwg-segment-routing-ti-lfa
Date: Wed, 15 Nov 2023 14:23:31 +0100
Message-ID: <032d01da17c6$edbcd570$c9368050$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_032E_01DA17CF.4F844AB0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIAokIumgeMz9HRyhSfDhuZ79RqAwLqf9gGsBb1RLA=
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/t70BfxVFGr6GngQfZVikZ1nd7FA>
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: Wed, 15 Nov 2023 13:23:40 -0000
Hi, I'm not aware of non-disclosed IPR. Stephane From: rtgwg <rtgwg-bounces@ietf.org> On Behalf Of bruno.decraene@orange.com Sent: Wednesday, November 15, 2023 9:16 AM To: Yingzhen Qu <yingzhen.ietf@gmail.com> Cc: RTGWG <rtgwg@ietf.org>; rtgwg-chairs <rtgwg-chairs@ietf.org> Subject: RE: IPR call for draft-rtgwg-segment-routing-ti-lfa Hi Yingzhen, I'm not aware of non-disclosed IPR. Thanks, Regards, --Bruno From: rtgwg <rtgwg-bounces@ietf.org <mailto:rtgwg-bounces@ietf.org> > On Behalf Of Yingzhen Qu Sent: Tuesday, November 14, 2023 7:23 PM To: RTGWG <rtgwg@ietf.org <mailto:rtgwg@ietf.org> >; rtgwg-chairs <rtgwg-chairs@ietf.org <mailto:rtgwg-chairs@ietf.org> > Subject: IPR call for draft-rtgwg-segment-routing-ti-lfa Hi, This is an IPR call for draft-ietf-rtgwg-segment-routing-ti-lfa ( <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-segment-routing-ti-lfa/> draft-ietf-rtgwg-segment-routing-ti-lfa-11 - Topology Independent Fast Reroute using Segment Routing) 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 Orange Restricted ____________________________________________________________________________ ________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
- 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