[Idr] Re: WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)

Liyan Gong <gongliyan@chinamobile.com> Mon, 05 August 2024 10:33 UTC

Return-Path: <gongliyan@chinamobile.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 CAE46C15155A for <idr@ietfa.amsl.com>; Mon, 5 Aug 2024 03:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 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_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 yS7DwCq5SjAz for <idr@ietfa.amsl.com>; Mon, 5 Aug 2024 03:33:42 -0700 (PDT)
Received: from cmccmta2.chinamobile.com (cmccmta2.chinamobile.com [111.22.67.135]) by ietfa.amsl.com (Postfix) with ESMTP id 0289CC15152F for <idr@ietf.org>; Mon, 5 Aug 2024 03:33:41 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[10.188.0.87]) by rmmx-syy-dmz-app07-12007 (RichMail) with SMTP id 2ee766b0aa83860-f5863; Mon, 05 Aug 2024 18:33:39 +0800 (CST)
X-RM-TRANSID: 2ee766b0aa83860-f5863
X-RM-SPAM-FLAG: 00000000
Received: from gongliyan@chinamobile.com ( [10.2.146.45] ) by ajax-webmail-syy-spmd05-11015 (Richmail) with HTTP; Mon, 5 Aug 2024 18:33:39 +0800 (CST)
Date: Mon, 05 Aug 2024 18:33:39 +0800
From: Liyan Gong <gongliyan@chinamobile.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Message-ID: <2b0766b099a5a8d-0007a.Richmail.00000032854960200027@chinamobile.com>
References: <SJ0PR08MB66220668F30E8B89E4C697C2B3B32@SJ0PR08MB6622.namprd08.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_134024_1335822576.1722854019498"
X-Priority: 3
X-RM-TRANSID: 2b0766b099a5a8d-0007a
Encrypt-Channel: web
X-RM-OA-ENC-TYPE: 0
X-RM-FontColor: 0
X-CLIENT-INFO: X-TIMING=0&X-MASSSENT=0&X-SENSITIVE=0
X-Mailer: Richmail_Webapp(V2.5.01)
Message-ID-Hash: YJCEXKC3MUYPVJ7MUFB2Q7XJ4FRQTB45
X-Message-ID-Hash: YJCEXKC3MUYPVJ7MUFB2Q7XJ4FRQTB45
X-MailFrom: gongliyan@chinamobile.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: WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/f7Gj6tMzyx7-mLrnXCm1Mps1TqE>
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,

I support this adoption. please see my response to the following questions. 



Does this BGP-LS addition help SR Egress Peering points in operational networks?  


     Yes.

  2.Does this draft handle the BUM traffic in a way that Prevents looping?(Broadcast, Unknown Unicast, and Multicast (BUM))


            Yes. This document is merely an announcement of the EPE39s L2 Bundle and does not involve any new looping mechanisms. The existing looping mechanisms apply to this document.


     3. Are there any problems in the technology described?


No





Best Regards,

Liyan



----邮件原文----发件人:Susan Hares  <shares@ndzh.com>收件人:"idr@ietf.org" <idr@ietf.org>抄 送: (无)发送时间:2024-08-02 22:11:31主题:[Idr] WG adoption call for   draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)
    

IDR WG: 


 


This begins a 2 week WG adoption call for  


draft-lin-idr-sr-epe-over-l2bundle-07.txt


https://datatracker.ietf.org/doc/draft-lin-idr-sr-epe-over-l2bundle/


 


 


The authors should reply to this email with an 


IPR statement indicating whether they know of an intellectual property. 


 


This document describes how to support Segment Routing 


BGP Egress Peer Engineering over Layer 2 bundle members. 


This document updates [RFC9085] to allow the L2 Bundle Member 


Attributes TLV to be added to the BGP-LS Attribute


associated with the Link NLRI of BGP peering link.


 


 


In your comments regarding adoption,  please consider 


 

Does this BGP-LS addition help SR Egress Peering points


in operational networks?  

Does this draft handle the BUM traffic in a way that 


Prevents looping?


(Broadcast, Unknown Unicast, and Multicast (BUM))

Are there any problems in the technology described? 


 


Cheerily, Sue Hares