Re: [Idr] A naive question about draft-lin-idr-sr-epe-over-l2bundle

linchangwang <linchangwang.04414@h3c.com> Tue, 07 November 2023 13:47 UTC

Return-Path: <linchangwang.04414@h3c.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB22EC16F3F4 for <idr@ietfa.amsl.com>; Tue, 7 Nov 2023 05:47:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 r2iY80xPfm7s for <idr@ietfa.amsl.com>; Tue, 7 Nov 2023 05:47:06 -0800 (PST)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7327EC15155E for <idr@ietf.org>; Tue, 7 Nov 2023 05:47:01 -0800 (PST)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 3A7Dkkks017614; Tue, 7 Nov 2023 21:46:46 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG2EX04-BASE.srv.huawei-3com.com (unknown [10.69.0.52]) by mail.maildlp.com (Postfix) with ESMTP id 17A442004DB5; Tue, 7 Nov 2023 21:49:34 +0800 (CST)
Received: from DAG2EX07-IDC.srv.huawei-3com.com (172.20.54.130) by DAG2EX04-BASE.srv.huawei-3com.com (10.69.0.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Tue, 7 Nov 2023 21:46:48 +0800
Received: from DAG2EX07-IDC.srv.huawei-3com.com ([::1]) by DAG2EX07-IDC.srv.huawei-3com.com ([fe80::fd0a:6e94:67d9:5ce8%10]) with mapi id 15.01.2507.006; Tue, 7 Nov 2023 21:46:48 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>, "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>, "pangran@chinaunicom.cn" <pangran@chinaunicom.cn>, "Mengxiao.Chen" <chen.mengxiao@h3c.com>
CC: Nitsan Dolev <Nitsan.Dolev@rbbn.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: A naive question about draft-lin-idr-sr-epe-over-l2bundle
Thread-Index: AdoRdBapzL3TJgOlSTW8URi5/Vio4gAAVEXAAAH2CcAAAOMI0A==
Date: Tue, 07 Nov 2023 13:46:48 +0000
Message-ID: <6bcfe39503234cfd98171c35a3d2fc75@h3c.com>
References: <PH0PR03MB630032A645D0CF03B292C0BBF6A9A@PH0PR03MB6300.namprd03.prod.outlook.com> <PH0PR03MB6300F02D72F0DE02890565AFF6A9A@PH0PR03MB6300.namprd03.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.76.67]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_6bcfe39503234cfd98171c35a3d2fc75h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 3A7Dkkks017614
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/MCvubklRp4QP0QpW7vXk8H38WaM>
Subject: Re: [Idr] A naive question about draft-lin-idr-sr-epe-over-l2bundle
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2023 13:47:07 -0000

Hi Sasha,

Thank you for your question. The specific response is as follows:

By using BGP EPE to support label distribution based on member ports, the network controller can have fine-grained control over the egress traffic.
Please refer to this presentation material on IDR for more details:
 https://datatracker.ietf.org/meeting/118/materials/slides-118-idr-sessa-1-1segment-routing-bgp-egress-peer-engineering-over-layer-2-bundle
https://datatracker.ietf.org/doc/html/draft-lin-idr-sr-epe-over-l2bundle-03

For example, when a BGP neighbor is established through an aggregate interface with three member ports, BGP can assign labels based on peer_adj and peer_adj_member as follows:


  *   PeerAdj SID TLV (Label-1010)
o    L2 Bundle Member Attribute TLV (Link Local Identifier describing the member link 1)
*L2 Bundle Member PeerAdj SID TLV (Label-1011)
*Min/Max Unidirectional Link Delay TLV (Delay of member link 1)
o    L2 Bundle Member Attribute TLV (Link Local Identifier describing the member link 2)
   *L2 Bundle Member PeerAdj SID TLV (Label-1012)
   *Min/Max Unidirectional Link Delay TLV (Delay of member link 2)
o    L2 Bundle Member Attribute TLV (Link Local Identifier describing the member link 3)
*L2 Bundle Member PeerAdj SID TLV (Label-1013)
  *Min/Max Unidirectional Link Delay TLV (Delay of member link 3)
BGP needs to respond to member interface change events on the aggregate interface.
For example, if member port 1 fails, when advertising BGP-LS EPE information, only member ports 2 and 3 will be advertised as follows:


  *   PeerAdj SID TLV (Label-1010)
o    L2 Bundle Member Attribute TLV (Link Local Identifier describing the member link 2)
  L2 Bundle Member PeerAdj SID TLV (Label-1012)
  Min/Max Unidirectional Link Delay TLV (Delay of member link 2)
o    L2 Bundle Member Attribute TLV (Link Local Identifier describing the member link 3)
* L2 Bundle Member PeerAdj SID TLV (Label-1013)
  *Min/Max Unidirectional Link Delay TLV (Delay of member link 3)
      Then, the controller receives network changes through BGP-LS and performs path computation again.


Thanks,
Changwang

From: Alexander Vainshtein [mailto:Alexander.Vainshtein@rbbn.com]
Sent: Tuesday, November 07, 2023 8:27 PM
To: linchangwang (RD); lizhenqiang@chinamobile.com; pangran@chinaunicom.cn; chenmengxiao (RD)
Subject: FW: A naive question about draft-lin-idr-sr-epe-over-l2bundle

Hi,
Forwarding directly to you – the IETF mailer cannot expand the draft-lin-idr-sr-epe-over-l2bundle@ietf.org<mailto:draft-lin-idr-sr-epe-over-l2bundle@ietf.org> address.


Regards,
Sasha

From: Alexander Vainshtein
Sent: Tuesday, November 7, 2023 2:19 PM
To: draft-lin-idr-sr-epe-over-l2bundle@ietf.org
Cc: idr@ietf.com; Nitsan Dolev <Nitsan.Dolev@rbbn.com>
Subject: A naive question about draft-lin-idr-sr-epe-over-l2bundle

Hi all,
Could the authors of the draft in question<https://datatracker.ietf.org/doc/html/draft-lin-idr-sr-epe-over-l2bundle-03> please clarify what is supposed to happen with the advertised bundle member-specific EPE SID if the link to which it refers fails?

Such failure would not necessarily  result in failure of the BGP neighborship.

Regards, and lots of thanks in advance,
Sasha



Disclaimer

This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.

-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from New H3C, 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!