Return-Path: 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 27D94C1CAE6F for ; Tue, 13 Aug 2024 18:19:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.104 X-Spam-Level: X-Spam-Status: No, score=-2.104 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_DNSWL_NONE=-0.0001, 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 (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 c1tJvM3Ner3t for ; Tue, 13 Aug 2024 18:19:28 -0700 (PDT) Received: from mail-yw1-x1129.google.com (mail-yw1-x1129.google.com [IPv6:2607:f8b0:4864:20::1129]) (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 496B1C1CAE6A for ; Tue, 13 Aug 2024 18:19:28 -0700 (PDT) Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-691c85525ebso57443767b3.0 for ; Tue, 13 Aug 2024 18:19:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723598367; x=1724203167; 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=hIzuEFc9w2734kidXQ39+RshIVkZUHkLsopqg7drgXQ=; b=Ad9kmRM4m4rOlQE/S+atnVLUYvx6Po7Y/yPi+RcYU7rcOwuVaX1mX6oBRoGIH9MX/O iESpsZPVtUC8jdqBSqkiNUJzkVEyiSD/sxiYw+CDGupdX4+OdhBU9Desco+CwRhvR/i8 KNeJlM2+3p0B6E/48CdPiCGprm1emLi6v3wWg/BFjgxiNdES4lQBEVNld9dosF2xzOJA ti1uCngEjawf9sTRaGf1jUr/56vJGCmmRfn8u5/4xEyLzGum25rwaxo7FpZiCmoazoIs bkAgRREcyIxh6y/oDKUjiOszcKJd9TPzEkpa+qpvqewov7E2OogsyMP8Z9obK8CJd3sM ZFsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723598367; x=1724203167; 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=hIzuEFc9w2734kidXQ39+RshIVkZUHkLsopqg7drgXQ=; b=U20/11OecivHPw3TmQxm+tLX6qbBBoj9W3V91bnyPfTlTpx8s7V+TYsOPI9NvQ7tZH L1zBEukIvUo06fULwAdJItMK5yuzyD75H2HkE6kGtlULk4u+4pGh+fYMG2QQY5HLziFZ SPpVmag7B/WY6C5mAa96KpF0ntywVkzSelgzAe90qyiHKSSg8rnaV65xqSHPo5GeTJwB Q2ENaSFngITHqXojP0gCxVhCVKCRG3cPeafdhTUfEozZZa0RaLmOLTUhux3ioK3t9OnE kURHShE3EHXMCl1u46gT97atA+NF/FY76pmPyjOJbOhe4h+FpuIoWGTiKwibOOs4E4hG 58yw== X-Gm-Message-State: AOJu0YzD9CkIA0HoFvXdhZyjiQkHsswkD3w7oGhHdoecdjpEXE0QaNh/ g6p+YWPQXR8ZJHeVtMxAswHMaVi8qwbHEqmmbw2VKJawW8Re7E/CMaKCTMOe7pviT7vbOfFnPPw 2iZl2XV1xtRsSWvkai0rfwsTIsvYzFFEh X-Google-Smtp-Source: AGHT+IEEtUlmEdLaSalo8bNkG1qjwNmvrWhkskhSHPE3QQW2iiTWcEQAT8ROhfjETt/q2oMNE0XxEyp4BQ/mCe2gk5U= X-Received: by 2002:a05:690c:4782:b0:664:80e0:ac7f with SMTP id 00721157ae682-6ac96bb6902mr13257397b3.19.1723598367315; Tue, 13 Aug 2024 18:19:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: allan michael Date: Wed, 14 Aug 2024 09:19:15 +0800 Message-ID: To: Susan Hares Content-Type: multipart/alternative; boundary="0000000000006b5e72061f9a84fd" Message-ID-Hash: RJU5LXITYTRJE24UCAHGCGUGDMOKNGFO X-Message-ID-Hash: RJU5LXITYTRJE24UCAHGCGUGDMOKNGFO X-MailFrom: michaelallenietf@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" X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BIdr=5D_Re=3A_WG_adoption_call_for_draft-lin-idr-sr-epe-over-l2b?= =?utf-8?q?undle-07_=288/2_to_8/16=29?= List-Id: Inter-Domain Routing Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000006b5e72061f9a84fd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Sue, I support WG adoption. I reviewed this document, and it is very helpful for the deployment of cross-domain L2 Bundles. 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? This document focuses on how BGP EPE advertises Peer Adj-SIDs on L2 Bundle member ports, and the existing loop mechanisms apply to this document. 3.Are there any problems in the technology described? I have not seen any problems yet. Regards, Allan On Fri, Aug 2, 2024 at 10:13=E2=80=AFPM Susan Hares 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 > --0000000000006b5e72061f9a84fd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Sue,

I support WG adoption.

I reviewed this document, and i= t is very helpful for the deployment of cross-domain L2 Bundles.


=C2=A0 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?

= This document focuses on how BGP EPE advertises Peer Adj-SIDs on L2 Bundle = member ports,=C2=A0and the existing loop mechanisms apply to this document.

3.Are there any problems in the technology described?=C2= =A0

I=C2=A0have no= t seen any problems yet.

=C2= =A0

Regards,<= /font>

Allan


On Fri, Aug 2, 2024 at 10:13=E2=80=AFPM Susan Hares <shares@ndzh.com> wrote:

= IDR WG:

= =C2=A0

= This begins a 2 week WG adoption call for =C2=A0

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

= https://datatracker.ietf.org/doc/draft-lin-idr-sr-e= pe-over-l2bundle/

= =C2=A0

= =C2=A0

= The authors should reply to this email with an

= IPR statement indicating whether they know of an intellectual property.

= =C2=A0

= 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.

= =C2=A0

= =C2=A0

= In your comments regarding adoption, =C2=A0please consider

= =C2=A0

  1. Does this BGP-LS add= ition help SR Egress Peering points

in operational networks? =C2=A0

  1. Does this draft hand= le the BUM traffic in a way that

Prevents looping?

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

  1. Are there any proble= ms in the technology described?

= =C2=A0

= Cheerily, Sue Hares

_______________________________________________
Idr mailing list -- idr@i= etf.org
To unsubscribe send an email to idr-leave@ietf.org
--0000000000006b5e72061f9a84fd--