IETF Logo Mail Archive

[Detnet] Re: WG Last Call: draft-ietf-spring-sr-redundancy-protection-07 (Ends 2026-07-06)

Mach Chen <mach.chen@huawei.com> Wed, 01 July 2026 02:54 UTC

Return-Path: <mach.chen@huawei.com>
X-Original-To: detnet@mail2.ietf.org
Delivered-To: detnet@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E28D310B502AD; Tue, 30 Jun 2026 19:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782874495; bh=wJLQfekYdQmtPn5IeCQYQzvdHNWf65j4pyHh+nNSMcE=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=xJfSs8gWELbpqy0jIsmctCljA8CE/Vc5TYU1oSt8LpqbBYkB62KYtJavG44f6+bZO /ysNv6IDhF7EnC9VUvF8L79YX0xarbPfTGGyiyQCLFf+x4cwtbACT/2kfD9D4bSL3k jFdh7l8NSsNxZ7bJ8e0XW++egLubA87r8xSSB1tA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.595
X-Spam-Level:
X-Spam-Status: No, score=-2.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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
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 cV7RRGbuizkY; Tue, 30 Jun 2026 19:54:50 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3105D10B5027B; Tue, 30 Jun 2026 19:54:50 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.224.83]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4gql2y4FjGzHnGdR; Wed, 1 Jul 2026 10:54:02 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id C5FD040569; Wed, 1 Jul 2026 10:54:47 +0800 (CST)
Received: from kwepemf500006.china.huawei.com (7.202.181.244) by kwepemh500011.china.huawei.com (7.202.181.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Wed, 1 Jul 2026 10:54:46 +0800
Received: from kwepemf100006.china.huawei.com (7.202.181.220) by kwepemf500006.china.huawei.com (7.202.181.244) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Wed, 1 Jul 2026 10:54:45 +0800
Received: from kwepemf100006.china.huawei.com ([7.202.181.220]) by kwepemf100006.china.huawei.com ([7.202.181.220]) with mapi id 15.02.1544.036; Wed, 1 Jul 2026 10:54:45 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, "draft-ietf-spring-sr-redundancy-protection@ietf.org" <draft-ietf-spring-sr-redundancy-protection@ietf.org>, "luismiguel.contrerasmurillo@telefonica.com" <luismiguel.contrerasmurillo@telefonica.com>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: WG Last Call: draft-ietf-spring-sr-redundancy-protection-07 (Ends 2026-07-06)
Thread-Index: AQHdAAlUZMCE3Z7TfE6XSP5RdhvQm7ZXQaQAgADHYIA=
Date: Wed, 01 Jul 2026 02:54:45 +0000
Message-ID: <84755272791646339ef311aa3da44120@huawei.com>
References: <178188659896.804518.1724349790116643869@dt-datatracker-f9b87776f-xzl65> <BN0PR11MB57261996184CABA8E0C29EDCC9F72@BN0PR11MB5726.namprd11.prod.outlook.com>
In-Reply-To: <BN0PR11MB57261996184CABA8E0C29EDCC9F72@BN0PR11MB5726.namprd11.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.110.47.46]
Content-Type: multipart/alternative; boundary="_000_84755272791646339ef311aa3da44120huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: D67XSA36MPZGFWZDTKDQZ6FCW6BFQWEX
X-Message-ID-Hash: D67XSA36MPZGFWZDTKDQZ6FCW6BFQWEX
X-MailFrom: mach.chen@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-detnet.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "detnet@ietf.org" <detnet@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Detnet] Re: WG Last Call: draft-ietf-spring-sr-redundancy-protection-07 (Ends 2026-07-06)
List-Id: Discussions on Deterministic Networking WG <detnet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/xZ3Zyo8sQsh6ckbH8ds20eU2Bi4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Owner: <mailto:detnet-owner@ietf.org>
List-Post: <mailto:detnet@ietf.org>
List-Subscribe: <mailto:detnet-join@ietf.org>
List-Unsubscribe: <mailto:detnet-leave@ietf.org>

Hi,

As co-author of the draft, I believe the latest version is ready for publication and support to move it forward.

Best regards,
Mach

From: Alvaro Retana via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>>
Sent: Friday, 19 June 2026 18:29:58
To: draft-ietf-spring-sr-redundancy-protection@ietf.org<mailto:draft-ietf-spring-sr-redundancy-protection@ietf.org> <draft-ietf-spring-sr-redundancy-protection@ietf.org<mailto:draft-ietf-spring-sr-redundancy-protection@ietf.org>>; luismiguel.contrerasmurillo@telefonica.com<mailto:luismiguel.contrerasmurillo@telefonica.com> <luismiguel.contrerasmurillo@telefonica.com<mailto:luismiguel.contrerasmurillo@telefonica.com>>; spring-chairs@ietf.org<mailto:spring-chairs@ietf.org> <spring-chairs@ietf.org<mailto:spring-chairs@ietf.org>>; spring@ietf.org<mailto:spring@ietf.org> <spring@ietf.org<mailto:spring@ietf.org>>
Cc: detnet@ietf.org<mailto:detnet@ietf.org> <detnet@ietf.org<mailto:detnet@ietf.org>>
Subject: WG Last Call: draft-ietf-spring-sr-redundancy-protection-07 (Ends 2026-07-06)

This message starts a WG Last Call for:
draft-ietf-spring-sr-redundancy-protection-07

This Working Group Last Call ends on 2026-07-06

Abstract:
   Redundancy Protection is a generalized protection mechanism to
   achieve high reliability for service provided in Segment Routing
   networks.  The mechanism uses the "Live-Live" methodology, i.e.,
   multiple copies of the data packets are sent on different paths to
   provide protection.  This document introduces one new SRv6 Segment
   Endpoint Behavior to provide replication and elimination functions on
   specific network nodes by leveraging SRv6 Network Programming
   capabilities.

File can be retrieved from:

Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping
spring@ietf.org<mailto:spring@ietf.org> in copy. Objections should be explained and suggestions to
resolve them are highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [1].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.

[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-sr-redundancy-protection/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-spring-sr-redundancy-protection-07

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-spring-sr-redundancy-protection-07

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