[Idr] Re: status draft-lin-idr-sr-epe-over-l2bundle-06
linchangwang <linchangwang.04414@h3c.com> Thu, 25 July 2024 02:14 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 C2B09C1D8774 for <idr@ietfa.amsl.com>; Wed, 24 Jul 2024 19:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 gk19jo-cmQSg for <idr@ietfa.amsl.com>; Wed, 24 Jul 2024 19:14:18 -0700 (PDT)
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 A10B1C1D8752 for <idr@ietf.org>; Wed, 24 Jul 2024 19:14:18 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 46P2Dqrx005182; Thu, 25 Jul 2024 10:13:52 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (unknown [10.153.34.10]) by mail.maildlp.com (Postfix) with ESMTP id 7F51B2004BA2; Thu, 25 Jul 2024 10:18:25 +0800 (CST)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (10.153.34.10) by DAG6EX08-BJD.srv.huawei-3com.com (10.153.34.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Thu, 25 Jul 2024 10:13:51 +0800
Received: from DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738]) by DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738%17]) with mapi id 15.02.1258.027; Thu, 25 Jul 2024 10:13:51 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: status draft-lin-idr-sr-epe-over-l2bundle-06
Thread-Index: AdreN/RIWtSuJpybSimrRfDFSFlK7A==
Date: Thu, 25 Jul 2024 02:13:51 +0000
Message-ID: <0a57f0daec1a4147b7dbf02322e84d88@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.142.192.247]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_0a57f0daec1a4147b7dbf02322e84d88h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 46P2Dqrx005182
Message-ID-Hash: ANPV46IKQPFROH4WTZMCIKR66JLRNEYF
X-Message-ID-Hash: ANPV46IKQPFROH4WTZMCIKR66JLRNEYF
X-MailFrom: linchangwang.04414@h3c.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: status draft-lin-idr-sr-epe-over-l2bundle-06
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-90Fj_Oci6qC3lSgY0vVS6DXHDY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>
Hi Sue and WG, We just submitted version 07 and resolved the comments. The link is: https://datatracker.ietf.org/doc/draft-lin-idr-sr-epe-over-l2bundle/07/ Thanks. Best Regards, Changwang ·¢¼þÈË: Susan Hares <shares@ndzh.com> ·¢ËÍʱ¼ä: 2024Äê7ÔÂ20ÈÕ 23:23 ÊÕ¼þÈË: idr@ietf.org; linchangwang (RD) <linchangwang.04414@h3c.com> Ö÷Ìâ: status draft-lin-idr-sr-epe-over-l2bundle-06 Changwang: Below is the status report from 5/20. Version 07 needs to answer Keyur¡¯s questions on the looping of BUM traffic. The only question I have is if there are MC-LAG bundles across devices (MC-LAG), there are mechanism to prevent BUM traffic from looping. This draft should add a section on 1) how the BUM Traffic would not be affected, 2) How there are no "loops" in the network. If you add this section, we will start WG adoption call for this draft. Cheers, Sue Status report: The combined status from 5/20 was at: https://mailarchive.ietf.org/arch/msg/idr/XQkAVav3Kg23B5UsOO764_CPvOE/ or the interim status at: https://datatracker.ietf.org/meeting/interim-2024-idr-04/materials/minutes-interim-2024-idr-04-202405201400-01 4. Segment Routing BGP Egress Peer Engineering over Layer 2 Bundle Members [15 minutes] draft-lin-idr-sr-epe-over-l2bundle-06 ¨C [Changwang Lin] Keyur: I think this is good as it stands. The only question I have is if there are MC-LAG bundles across devices (MC-LAG), there are mechanism to prevent BUM traffic from looping. This draft should add a section on 1) how the BUM Traffic would not be affected, 2) How there are no "loops" in the network. Sue: Any other comments? Ketan: Thank you to Alvaro for his comments that this draft needs to update the BGP-LS draft. He makes a good point, and we'll discuss it among the authors whether is is needed. If the WG chairs have feedback, Sue: I would like to see the information on BUM traffic and the ability to avoid loops before we go to adoption. We'll send this to Spring and IDR for adoption. Alvaro: This does not need to hold up for Spring. ------------------------------------------------------------------------------------------------------------------------------------- ±¾Óʼþ¼°Æ丽¼þº¬ÓÐлªÈý¼¯Íŵı£ÃÜÐÅÏ¢£¬½öÏÞÓÚ·¢Ë͸øÉÏÃæµØÖ·ÖÐÁгö µÄ¸öÈË»òȺ×é¡£½ûÖ¹ÈκÎÆäËûÈËÒÔÈκÎÐÎʽʹÓ㨰üÀ¨µ«²»ÏÞÓÚÈ«²¿»ò²¿·ÖµØй¶¡¢¸´ÖÆ¡¢ »òÉ¢·¢£©±¾ÓʼþÖеÄÐÅÏ¢¡£Èç¹ûÄú´íÊÕÁ˱¾Óʼþ£¬ÇëÄúÁ¢¼´µç»°»òÓʼþ֪ͨ·¢¼þÈ˲¢É¾³ý±¾ Óʼþ£¡ 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!
- [Idr] Re: status draft-lin-idr-sr-epe-over-l2bund… linchangwang
- [Idr] status draft-lin-idr-sr-epe-over-l2bundle-06 Susan Hares