IETF Logo Mail Archive

Re: [spring] WGLC for draft-ietf-spring-sr-replication-segment

"Xiejingrong (Jingrong)" <xiejingrong@huawei.com> Thu, 08 December 2022 11:41 UTC

Return-Path: <xiejingrong@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 06873C14CF0B; Thu, 8 Dec 2022 03:41:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 QumdJNhWWMti; Thu, 8 Dec 2022 03:41:23 -0800 (PST)
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 08E34C14F74B; Thu, 8 Dec 2022 03:41:23 -0800 (PST)
Received: from lhrpeml500004.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4NSXJt3d8yz67frp; Thu, 8 Dec 2022 19:40:30 +0800 (CST)
Received: from kwepemi500002.china.huawei.com (7.221.188.171) by lhrpeml500004.china.huawei.com (7.191.163.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Thu, 8 Dec 2022 11:41:18 +0000
Received: from kwepemi500004.china.huawei.com (7.221.188.17) by kwepemi500002.china.huawei.com (7.221.188.171) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Thu, 8 Dec 2022 19:41:17 +0800
Received: from kwepemi500004.china.huawei.com ([7.221.188.17]) by kwepemi500004.china.huawei.com ([7.221.188.17]) with mapi id 15.01.2375.031; Thu, 8 Dec 2022 19:41:17 +0800
From: "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>
To: Rishabh Parekh <rishabhp@gmail.com>
CC: James Guichard <james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>
Thread-Topic: [spring] WGLC for draft-ietf-spring-sr-replication-segment
Thread-Index: AdkDOXX5fD56cgadQLyJ82sZgqL1jQF4qkegABjWyAAAJWriEAANlFIAACtr94A=
Date: Thu, 08 Dec 2022 11:41:16 +0000
Message-ID: <653d349f453c4abbbe033d9f37273759@huawei.com>
References: <MN2PR13MB4206165672BF331105525F8CD2139@MN2PR13MB4206.namprd13.prod.outlook.com> <f120be63ce0c4b4fbe3deede7f3e8343@huawei.com> <CABjMoXa_F3UGCMzh+FBvGBAXpYXyx9kTpaKP-7QKpTy9hGsYEQ@mail.gmail.com> <05668681202f4452a9d2423fec6c063f@huawei.com> <CABjMoXaa4uv1GLvKsYr5vszhOUy3adPOD6iMjEUqJZRM2-6pOQ@mail.gmail.com>
In-Reply-To: <CABjMoXaa4uv1GLvKsYr5vszhOUy3adPOD6iMjEUqJZRM2-6pOQ@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.42]
Content-Type: multipart/alternative; boundary="_000_653d349f453c4abbbe033d9f37273759huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/COOHen_Y6z8Kb9vmRYXZvdlGb0I>
Subject: Re: [spring] WGLC for draft-ietf-spring-sr-replication-segment
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 08 Dec 2022 11:41:27 -0000

Hi Rishabh,

Thank you for your reply very much.
For MPLS data plane, it may be nice to introduce DCB concept since it is different than SRGB or SRLB.
For SRv6 data plane, is it the same as MPLS that has a concept like “DCB” to allocate an SRv6 SID and put after the replication SID ?

-Jingrong

本邮件及其附件可能含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments may contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

From: Rishabh Parekh [mailto:rishabhp@gmail.com]
Sent: Thursday, December 8, 2022 6:52 AM
To: Xiejingrong (Jingrong) <xiejingrong@huawei.com>
Cc: James Guichard <james.n.guichard@futurewei.com>; SPRING WG <spring@ietf.org>; spring-chairs@ietf.org
Subject: Re: [spring] WGLC for draft-ietf-spring-sr-replication-segment

Jingrong,

For the second one regarding the SID after the replication SID, I still have some further question when considering it a “VPN SID”:

In MPLS data plane, Is the SID an Upstream-assigned Label ? Or an SRGB label (though may be a more strictly unique number than SRGB that is a relatively unique index/offset ) ?
In SRv6 data plane, is the SID an “Upstream-assigned SRv6 SID”, which is allocated on Ingress PE and put in the SID list after the replication SID ?

The VPN SID is only required when SR P2MP trees are shared across VPNs. It can be upstream assigned or globally assigned (from DCB) as described in SR P2MP MVPN<https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-evpn-sr-p2mp/> draft. If present, the VPN SID is after the Replication SID. For SR-MPLS, the VPN SID SHOULD NOT be assigned from SRGB or SRLB since it is an overlay context,

-Rishabh

v2.23.0 | Report a Bug | By Email