IETF Logo Mail Archive

[Idr] Re: Fw:draft-ietf-idr-flowspec-redirect-ip-04 - 2 week WG LC(2/7/2026 to 2/21/2026)

Wenying Jiang <jiangwenying@chinamobile.com> Thu, 26 February 2026 09:06 UTC

Return-Path: <jiangwenying@chinamobile.com>
X-Original-To: idr@mail2.ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 97A73BE91A99 for <idr@mail2.ietf.org>; Thu, 26 Feb 2026 01:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.397
X-Spam-Level:
X-Spam-Status: No, score=-2.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=chinamobile.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U_YCLC4eXt9M for <idr@mail2.ietf.org>; Thu, 26 Feb 2026 01:06:29 -0800 (PST)
Received: from cmccmta2.chinamobile.com (cmccmta1.chinamobile.com [111.22.67.137]) by mail2.ietf.org (Postfix) with ESMTP id C813DBE91A92 for <idr@ietf.org>; Thu, 26 Feb 2026 01:06:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chinamobile.com; s=default; l=0; h=from:subject:message-id:to:mime-version; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=XoSMRnTGTR7ckBZlW/F6KzB26KAYU1RhIuK/xhO1lrWHZUOzyabY0XYi7kCTkIf7Q54CLKLOcvmEA bAydMs/PpjTVVenovM97hqoutsq2KG6L+5HCZYrbr/dsyR+U/Wxr7o4dtSWN9c+NpMZ8WyyfsdtgEj IGuCS+9Wpuw73f6E=
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[10.188.0.87]) by rmmx-syy-dmz-app08-12008 (RichMail) with SMTP id 2ee869a00d0617d-f7237; Thu, 26 Feb 2026 17:06:14 +0800 (CST)
X-RM-TRANSID: 2ee869a00d0617d-f7237
X-RM-SPAM-FLAG: 00000000
Received: from jiangwenying@chinamobile.com ( [10.2.146.27] ) by ajax-webmail-syy-spmd02-11012 (Richmail) with HTTP; Thu, 26 Feb 2026 17:06:14 +0800 (CST)
Date: Thu, 26 Feb 2026 17:06:14 +0800
From: Wenying Jiang <jiangwenying@chinamobile.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Message-ID: <2b0469a00a3689e-0001b.Richmail.00007022362020611786@chinamobile.com>
References: <DM8PR08MB741323EC57FD093429A36598B367A@DM8PR08MB7413.namprd08.prod.outlook.com>, <2b07699feeafafe-0003d.Richmail.00006072653910097546@chinamobile.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_11657_790560174.1772096774318"
X-Priority: 3
X-RM-TRANSID: 2b0469a00a3689e-0001b
Encrypt-Channel: web
X-RM-OA-ENC-TYPE: 0
X-RM-FontColor: 0
X-CLIENT-INFO: X-TIMING=0&X-MASSSENT=0&X-SENSITIVE=0
X-Mailer: Richmail_Webapp(V2.5.01)
Message-ID-Hash: OZBOGDTAPFZUWPN4PFRYNCBKRPCWPLNE
X-Message-ID-Hash: OZBOGDTAPFZUWPN4PFRYNCBKRPCWPLNE
X-MailFrom: jiangwenying@chinamobile.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Re: Fw:draft-ietf-idr-flowspec-redirect-ip-04 - 2 week WG LC(2/7/2026 to 2/21/2026)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/SemjuaGRqAU0gdli9KTIOOkYjuE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Hi, Sue and all



I support the publication of this draft. The method proposed in this document is feasible.



BR.

Wenying





----邮件原文----发件人：Susan Hares  <shares@ndzh.com>收件人：idr  <idr@ietf.org>,"adam.1.simpson@nokia.com" <adam.1.simpson@nokia.com>,Wim Henderickx  <wim.henderickx@gmail.com>抄　送: (无)发送时间：2026-02-07 23:55:47主题：[Idr] draft-ietf-idr-flowspec-redirect-ip-04 - 2 week WG LC (2/7/2026 to 2/21/2026)     

This begins a 2-week WG LC for draft-ietf-idr-flowspec-redirect-ip-04.txt.


 


There are 4 implementations (Cisco, HPE/Juniper, Huawei, Arrcus)


See the implementation report on the IDR Wiki at: 


https://wiki.ietf.org/group/idr/implementations/draft-ietf-idr-flowspec-redirect-ip


 


The Authors (Jeff, Wim, and Adam) should respond to this email 


with an IPR statement indicating that


a) Yes – I  know of IPR related to this draft, or 


b) No – I do not know of IPR related to this drasft.  


 


If they state they know of IPR, please indicate if it has been disclosed to the IETF. 


 


This draft has gone through several iterations.  


Please examine the implementation Report carefully, 


due to the fact:

some features (e.g. the C = Copy Bit) have not been implemented by any vendor, 

some features (e.g., Redirect-to-IP in Redirect-to-VRF feature) 


are only implemented by one vendor. 


 


The technology described in this draft extends Flow Specification v1 technology. 


It is referred to by draft-ietf-idr-ts-flowspec-srv6-policy-08


(https://datatracker.ietf.org/doc/draft-ietf-idr-ts-flowspec-srv6-policy/)


 


in which an additional 5 implementations have used it in deployed technology


(Huawei, New H3C, Ruijie, China Unitechs, and ZTE). 


 


 


Cheerily, Sue

v2.46.0 | Report a Bug | By Email | System Status