[spring] FW: New Version Notification for draft-chen-rtgwg-srv6-midpoint-protection-05.txt

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Mon, 12 July 2021 10:23 UTC

Return-Path: <gengxuesong@huawei.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA83A3A118B; Mon, 12 Jul 2021 03:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxfSiVppVE8H; Mon, 12 Jul 2021 03:22:56 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F0233A117A; Mon, 12 Jul 2021 03:22:56 -0700 (PDT)
Received: from fraeml735-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GNfbz30pBz6BBG5; Mon, 12 Jul 2021 18:08:31 +0800 (CST)
Received: from dggema774-chm.china.huawei.com (10.1.198.216) by fraeml735-chm.china.huawei.com (10.206.15.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Mon, 12 Jul 2021 12:22:51 +0200
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by dggema774-chm.china.huawei.com (10.1.198.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 12 Jul 2021 18:22:49 +0800
Received: from dggeme752-chm.china.huawei.com ([10.6.80.76]) by dggeme752-chm.china.huawei.com ([10.6.80.76]) with mapi id 15.01.2176.012; Mon, 12 Jul 2021 18:22:49 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: "spring@ietf.org" <spring@ietf.org>
CC: draft-chen-rtgwg-srv6-midpoint-protection <draft-chen-rtgwg-srv6-midpoint-protection@ietf.org>
Thread-Topic: New Version Notification for draft-chen-rtgwg-srv6-midpoint-protection-05.txt
Thread-Index: AQHXdwcYx7YWxb80bkWDXbqlmr7q7Ks/IIGA
Date: Mon, 12 Jul 2021 10:22:49 +0000
Message-ID: <8fcec13780f54af79262d1eeca86c3dd@huawei.com>
References: <162608503380.18627.11512023531096497290@ietfa.amsl.com>
In-Reply-To: <162608503380.18627.11512023531096497290@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.242.209]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/WoDvjqFBFEVJllKJ1IUp1uBhELc>
Subject: [spring] FW: New Version Notification for draft-chen-rtgwg-srv6-midpoint-protection-05.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2021 10:23:07 -0000

Hi SPRING,

We have just updated the document of draft-chen-rtgwg-srv6-midpoint-protection for SRv6 midpoint protection. Considering that there are relevant work and discussions in SPRING as well, it is appreciated if you could review our draft and give comments. We will also try to request a time slot in IETF 111 to collect feedback.

Thanks!
Xuesong

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, July 12, 2021 6:17 PM
To: Huaimo Chen <Huaimo.chen@futurewei.com>; Huaimo Chen <huaimo.chen@futurewei.com>; Huanan Chen <chenhuan6@chinatelecom.cn>; Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com>; Yisong Liu <liuyisong@chinamobile.com>; Huzhibo <huzhibo@huawei.com>
Subject: New Version Notification for draft-chen-rtgwg-srv6-midpoint-protection-05.txt


A new version of I-D, draft-chen-rtgwg-srv6-midpoint-protection-05.txt
has been successfully submitted by Xuesong Geng and posted to the IETF repository.

Name:		draft-chen-rtgwg-srv6-midpoint-protection
Revision:	05
Title:		SRv6 Midpoint Protection
Document date:	2021-07-12
Group:		Individual Submission
Pages:		10
URL:            https://www.ietf.org/archive/id/draft-chen-rtgwg-srv6-midpoint-protection-05.txt
Status:         https://datatracker.ietf.org/doc/draft-chen-rtgwg-srv6-midpoint-protection/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-chen-rtgwg-srv6-midpoint-protection
Diff:           https://www.ietf.org/rfcdiff?url2=draft-chen-rtgwg-srv6-midpoint-protection-05

Abstract:
   The current local repair mechanism, e.g., TI-LFA, allows local repair
   actions on the direct neighbors of the failed node to temporarily
   route traffic to the destination.  This mechanism could not work
   properly when the failure happens in the destination point or the
   link connected to the destination.  In SRv6 TE, the IPv6 destination
   address in the outer IPv6 header could be the dedicated endpoint of
   the TE path rather than the destination of the TE path.  When the
   endpoint fails, local repair couldn't work on the direct neighbor of
   the failed endpoint either.  This document defines midpoint
   protection, which enables the direct neighbor of the failed endpoint
   to do the function of the endpoint, replace the IPv6 destination
   address to the other endpoint, and choose the next hop based on the
   new destination address.


                                                                                  


The IETF Secretariat