IETF Logo Mail Archive

Re: [spring] Comments on draft-geng-spring-sr-redundancy-protection

"Yangfan (IP Standard)" <shirley.yangfan@huawei.com> Mon, 17 May 2021 13:20 UTC

Return-Path: <shirley.yangfan@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 56BD33A3783 for <spring@ietfa.amsl.com>; Mon, 17 May 2021 06:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 aw1nydVlIqrm for <spring@ietfa.amsl.com>; Mon, 17 May 2021 06:20:21 -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 600723A3782 for <spring@ietf.org>; Mon, 17 May 2021 06:20:21 -0700 (PDT)
Received: from fraeml705-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FkKKL3n94z6wjNQ; Mon, 17 May 2021 21:11:50 +0800 (CST)
Received: from dggeme703-chm.china.huawei.com (10.1.199.99) by fraeml705-chm.china.huawei.com (10.206.15.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 17 May 2021 15:20:18 +0200
Received: from nkgeml701-chm.china.huawei.com (10.98.57.156) by dggeme703-chm.china.huawei.com (10.1.199.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 17 May 2021 21:20:16 +0800
Received: from nkgeml701-chm.china.huawei.com ([10.98.57.156]) by nkgeml701-chm.china.huawei.com ([10.98.57.156]) with mapi id 15.01.2176.012; Mon, 17 May 2021 21:20:16 +0800
From: "Yangfan (IP Standard)" <shirley.yangfan@huawei.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, 'Rishabh Parekh' <rishabhp@gmail.com>
CC: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, "'Rishabh Parekh (riparekh)'" <riparekh@cisco.com>, "'Arvind Venkateswaran (arvvenka)'" <arvvenka@cisco.com>, "'spring@ietf.org'" <spring@ietf.org>
Thread-Topic: [spring] RE: Comments on draft-geng-spring-sr-redundancy-protection
Thread-Index: AddLHpkEAMIRIqXpQ2aOJ04/NHpAdQ==
Date: Mon, 17 May 2021 13:20:16 +0000
Message-ID: <101996923664441492159b346eee7d98@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.115]
Content-Type: multipart/alternative; boundary="_000_101996923664441492159b346eee7d98huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/lDzLaW5l1uk3n-i4hVhEfDUKGSw>
Subject: Re: [spring] Comments on draft-geng-spring-sr-redundancy-protection
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, 17 May 2021 13:20:25 -0000

Hi Jeffrey,

To summarize the discussions a bit, I have two questions and hope to hear your comments and clarifications.
Q1: Are there any questions for clarifications or open issues with the current solution of redundancy-SID+Merging-SID+redundancy policy? If so, we would like to clarify them first.
Q2:
Figure 1 in draft-geng-spring-sr-redundnacy-protection is the typical topology for Redundancy Protection in SR domain, as shown below.
R1------R-------R3-------M-------R2
+-------R4-------+
Could you please explain how exactly Tree-SID solution is used in data plane for redundancy protection? For example, how the SR SID List is assigned, how the packet is encapsulated and forwarded from R1 to R2 in data plane, how Tree-SID and Replication SID are configured on network nodes, etc.
I don’t think I understand the entire forwarding flow correctly. In fact we are very interested in Tree-SID solution as it has been adopted as a WG work. It would be very helpful if you or anyone can provide a detailed illustration or comparison, for instance like the way of the Appendix in replication SID/Tree SID drafts.

Looking forward to your reply!
Best,
Fan

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