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

Gyan Mishra <hayabusagsm@gmail.com> Sat, 17 August 2024 00:38 UTC

Return-Path: <hayabusagsm@gmail.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 0C299C180B45 for <idr@ietfa.amsl.com>; Fri, 16 Aug 2024 17:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, 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 (2048-bit key) header.d=gmail.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 q9SOAqr_iU9a for <idr@ietfa.amsl.com>; Fri, 16 Aug 2024 17:38:30 -0700 (PDT)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D9E1C169426 for <idr@ietf.org>; Fri, 16 Aug 2024 17:38:30 -0700 (PDT)
Received: by mail-pg1-x52f.google.com with SMTP id 41be03b00d2f7-7c691c8f8dcso1870597a12.1 for <idr@ietf.org>; Fri, 16 Aug 2024 17:38:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723855110; x=1724459910; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4oAIniErRuq7pTAKxHUu1IyYmnjU3oE/9Fvqzs8jfs8=; b=Fam3EzW5CUDrpgsdi2Ern6A12QEk3ku/eKYo8f2Mx5ek1wuvQSUEubzPPFkUigrry4 zOr9S0vSLHatwIbRWqI8UHoyD/2GOq+qjx0ONrni2N0R8OfGkngjoho3UHBQNmN8daH9 EQ4DAISx63tCASchH/fWQIio07nTJYDoRpVfcr4P8iyudYNIWxL9/o444NZlv2JgbXT5 6Fil2WuyH6RSOPzXZl08nxtf1QtrCT7JOWEYc/LdKThihQIgjPfyaFHCHn9ZoXiRfxKd g3PG7K2TyhDbf7vhZZys7S6AJTQd/1WoPYdiOUw0ZdmQnDeyT8h8xg8GZ6rU+zINFA5r PniQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723855110; x=1724459910; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=4oAIniErRuq7pTAKxHUu1IyYmnjU3oE/9Fvqzs8jfs8=; b=Xyq5NT9WJUBBRCZTM9IP2rzz8SPRQFx4N3u7AP3UM37AZXCBCBQsAgf5ZAH1qoXFaM 8T6ZyUSYXQMmsXUyKpRf1Uh16knxI3U+IjtQPnfl+7Olw8ZMpumsuQoZV1WAYV7A6SwK 1En41V3PY5VxRP9H9d01cZ4sCJV6liMf/wQAmMwYPa/WI6cFiltjVG54uuwATErbt60p BGtyMNgO1bp/8tis/alkYBaGns0p5bYnCi7WKEVbuc4mL9jqUUUSGjy1iwb5/RZ76Mqo yFCESjdkHyig/pDHJg2AF0gCIqCeJ5P3NREm6EQ/sgbkJ8KMZ5BzpT8AFDueBbUkCqmQ krIw==
X-Gm-Message-State: AOJu0Yzfdn0HMk7PYcBWaNoLIDvUFo1WAXRj/YUmRXCth813HzL48Z4g 8MlSXVExJqWoyfGnSygv4FsAmRttJio1dAUE51FRwSi4KqUYbEK/r3wkRafwFMYgAhh2sOpCTLE c2qmhE0JAFmxmsqrJRKWfuibGCb+ssA==
X-Google-Smtp-Source: AGHT+IGyKm3vSC8+TMiRkqde7CBRwhfQY/qCZdSFBm189Jt2+c/R3KqM9/asK6DAxOUUK+8Idl0jfg1Sv8Y1grevBBM=
X-Received: by 2002:a05:6a21:1789:b0:1c6:91e3:e77d with SMTP id adf61e73a8af0-1c904f8f848mr5643759637.16.1723855109446; Fri, 16 Aug 2024 17:38:29 -0700 (PDT)
MIME-Version: 1.0
References: <SJ0PR08MB66220668F30E8B89E4C697C2B3B32@SJ0PR08MB6622.namprd08.prod.outlook.com>
In-Reply-To: <SJ0PR08MB66220668F30E8B89E4C697C2B3B32@SJ0PR08MB6622.namprd08.prod.outlook.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 16 Aug 2024 20:38:18 -0400
Message-ID: <CABNhwV0cg6Kd8dMk040w8i0egUOTZSEfSeXxgfW058GZEKeOZA@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="0000000000007161a0061fd64b17"
Message-ID-Hash: H3IAZZS7THP7ESIO6LMQ2UDX77N434VB
X-Message-ID-Hash: H3IAZZS7THP7ESIO6LMQ2UDX77N434VB
X-MailFrom: hayabusagsm@gmail.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
CC: "idr@ietf.org" <idr@ietf.org>
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/ZbU8Rp2EiODKRPvccD4g8oMfyQk>
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>

I support adoption.



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

Yes this would be very helpful for operators steering over L2 bundle member
link with available bandwidth


   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?

Yes

Thanks


Gyan

On Fri, Aug 2, 2024 at 10:11 AM Susan Hares <shares@ndzh.com> wrote:

> 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
> _______________________________________________
> Idr mailing list -- idr@ietf.org
> To unsubscribe send an email to idr-leave@ietf.org
>