IETF Logo Mail Archive

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

lihaovip <lihaovip@163.com> Wed, 14 August 2024 02:12 UTC

Return-Path: <lihaovip@163.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 92FFEC18DB96 for <idr@ietfa.amsl.com>; Tue, 13 Aug 2024 19:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_BL=0.001, RCVD_IN_MSPIKE_L3=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=163.com
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 jU68CNTgaYP5 for <idr@ietfa.amsl.com>; Tue, 13 Aug 2024 19:12:12 -0700 (PDT)
Received: from m16.mail.163.com (m16.mail.163.com [117.135.210.5]) by ietfa.amsl.com (Postfix) with ESMTP id C0402C16941D for <idr@ietf.org>; Tue, 13 Aug 2024 19:12:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Subject:Content-Type:MIME-Version: Message-ID; bh=GUfZMeATXVDxyfeRYxmSrM7nuk9MsqsZrFM+s6uXZ60=; b=e lyGPMj17ONb7wwH8eRwbYo5l69DP2AVPnj50xno3CveaDLh1NGQnxsLOIg9g6rsz O0Xl3uSm8SMflIJbmJ19Eomrucd3KoSDKbl0bgfpHtiYuD3ID81uJYXSzpmWf4t8 1qYuGzX0tQcSKHbv0Rd09JlOnHlkmVB4KFNZJ8Kric=
Received: from lihaovip$163.com ( [117.128.51.72] ) by ajax-webmail-wzpm-k8s-gz (Coremail) ; Wed, 14 Aug 2024 10:12:01 +0800 (GMT+08:00)
X-Originating-IP: [117.128.51.72]
From: lihaovip <lihaovip@163.com>
To: "shares@ndzh.com" <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version 2023.1-cmXT build 20230828(bca80109) MailMasterAndroid/7.19.7_(12) Copyright (c) 2002-2024 www.mailtech.cn 163com
X-NTES-SC: AL_Qu2ZAfqbvk0p5yCQZ+kZnEkXh+w5XsS1uf4u3oJQOJ80nSXXxzkdVEVxEUbU4uaFCwCViiKwchN21sZFVIxCfLkKfEKgU+ZUcjnGpw7oreuV
Content-Type: multipart/alternative; boundary="----=_Part_572809_2004488294.1723601521091"
MIME-Version: 1.0
Message-ID: <19583986.2363f.1914ea809c4.Coremail.lihaovip@163.com>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: _____wD3_0FyErxmFtILAA--.37529W
X-CM-SenderInfo: 5olkt0xylsqiywtou0bp/1tbiRxs7XWV4K1dY6QABsr
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
X-MailFrom: lihaovip@163.com
X-Mailman-Rule-Hits: nonmember-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0
Message-ID-Hash: R5K3WCAPYCDWBGNSPORT3DP2KC6JPUTC
X-Message-ID-Hash: R5K3WCAPYCDWBGNSPORT3DP2KC6JPUTC
X-Mailman-Approved-At: Wed, 28 Aug 2024 08:41:59 -0700
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/L99AyAi7jNiEI_yFc10v3SW6SAk>
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>
Date: Thu, 15 Aug 2024 00:43:48 -0000
X-Original-Date: Wed, 14 Aug 2024 10:12:01 +0800 (GMT+08:00)






Hi WG:

 

I support the adoption of this draft.

 

 

1)  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.

 

3)  Are there any problems in the technology described?

 

                No

 

 

Best Wishes.

 




From: Susan Hares [mailto:shares@ndzh.com]
Sent: Friday, August 02, 2024 10:12 PM
To:idr@ietf.org
Subject: [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

 

1)  Does this BGP-LS addition help SR Egress Peering points

in operational networks?  

2)  Does this draft handle the BUM traffic in a way that

Prevents looping?

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

3)  Are there any problems in the technology described?

 

Cheerily, Sue Hares

---------------------------------

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