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 9074DC15106B for ; Tue, 2 Jul 2024 00:31:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.607 X-Spam-Level: X-Spam-Status: No, score=-1.607 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, GB_ABOUTYOU=0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bytedance.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 0XVVrO5vIX74 for ; Tue, 2 Jul 2024 00:31:07 -0700 (PDT) Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CC87C169431 for ; Tue, 2 Jul 2024 00:31:06 -0700 (PDT) Received: by mail-ej1-x629.google.com with SMTP id a640c23a62f3a-a6fd513f18bso465094466b.3 for ; Tue, 02 Jul 2024 00:31:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance.com; s=google; t=1719905464; x=1720510264; 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=WWbAzs/lzz4UimJxSDFRAfZCgF4rqJpEDBSFj5v1M3E=; b=lTE0iKWZtyCBuGXc28NO1m+B3GLIq+Nvbwcy+T4qEXajIg1r/HMasqs023j05VYsTT H3D8Qo5rPHTAo9xpc7/PUmm5eewuxglJgvD7i9NV/AfyiBdNpB43McYd33pjNzPb3xM/ Cr1sjs0fLlFYs2wk809ls1khmvtfywSgymho9l498Ndu0fxkyLCWk0S7zV4wvPPkE+QD yeBdY/dOAlnbW8Drqrzs7IQ4oSt49Aik1V13PdIFDxdWjxSANgZt6JPgbpoN7LLv77uN Smp68zqsM56DxrTgutjWabk36a4uk/PcWmpFHNnvFgk/kfBS8wwS7n8WB+BkNpF3xmel FtFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719905464; x=1720510264; 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=WWbAzs/lzz4UimJxSDFRAfZCgF4rqJpEDBSFj5v1M3E=; b=aiWVenSRgV2mkMG61trk7u7+SYERw2OkaAK32kAnqIkizXSVe/2i/0DrG+U1bzxk3f +POR3YnPsLe7gqjji6cHt+qXFkJyUkfdPRi7HZQgCltGnlXeUdoxaSSxVIA5ZgQ+JwJL FIrRKuubxF6/5BvR9FcmsYpcJ7MDs3DkzNMW81HmuupPIKq+7x9n2RMDxMTm+lNnYrGI eftwZoBdCwOyqvGBV4cgRqPrB/xlBHaAbYkF9Bl7rlTRhf4gkIwvrmlfjKyMN3+mgmQH 10vislpCZPaelPnfmLzT2zWAfEMiFtH5+gN6UkWCExv9eKdGm6J2xnY4zQNQz+4ydy4e dUDQ== X-Forwarded-Encrypted: i=1; AJvYcCUMfpsDehVnkqubRpm/+VckVdTuz4CzRVGunw4UMyPIZ8XQJZ708bhuShMk2meM0csM/wfFg6J8HtLc60M= X-Gm-Message-State: AOJu0YwM5LAHuUUdgvSEbkmhiiXo5CmWL4P7NrreeQUI8BhF2UrnVywh RhushE5Frmmq0rhqWcsdYoA3wr+cRoGYqDIPhKs3uM1myIfj2rMeeRgaszd2PEC22LmIKfRxS+b ABPnfIf6wL+KWVHBKNDH6vUpdRTanEJ2IeXlbWUZophhkIxUa X-Google-Smtp-Source: AGHT+IH7ipxY3aLC9GEkeiqDWVWd24Qix+iIrmsq3+VnfINSBSMeJsSY7f/hn9IrhPg5/pdCA32nmEUNJdRlNTU/ZbA= X-Received: by 2002:a17:906:3a99:b0:a6f:2a43:e956 with SMTP id a640c23a62f3a-a75144b51a3mr466243166b.74.1719905464003; Tue, 02 Jul 2024 00:31:04 -0700 (PDT) Received: from 44278815321 named unknown by gmailapi.google.com with HTTPREST; Tue, 2 Jul 2024 03:31:03 -0400 Mime-Version: 1.0 References: <5c390c2f3dfc47ceb22ad541a17c8436@h3c.com> In-Reply-To: From: =?UTF-8?B?6ZyN5pyL6aOe?= Date: Tue, 2 Jul 2024 03:31:03 -0400 Message-ID: To: Linda Dunbar Content-Type: multipart/alternative; boundary="0000000000003ad2b0061c3eb22e" Message-ID-Hash: BVXVC63S5IDFNDKTWSPNTZLQNKD4VZ44 X-Message-ID-Hash: BVXVC63S5IDFNDKTWSPNTZLQNKD4VZ44 X-MailFrom: huopengfei@bytedance.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: "aidc@ietf.org" , "idr@ietf.org" X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BIdr=5D_Re=3A_=5BExternal=5D_Questions_about_draft-hcl-idr-exten?= =?utf-8?q?d-tunnel-egress-point?= List-Id: Inter-Domain Routing Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000003ad2b0061c3eb22e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Linda=EF=BC=8C Thanks for your comments. Yes , we are asking for a new Tunnel Type. To avoid any confusion over the name, we are considering a new name. Thanks, Pengfei From: "Linda Dunbar" Date: Tue, Jul 2, 2024, 05:50 Subject: [External] Questions about draft-hcl-idr-extend-tunnel-egress-poin= t To: "linchangwang", "aidc@ietf.org"< aidc@ietf.org> Cc: "huopengfei@bytedance.com", "idr@ietf.org"< idr@ietf.org> PengFei, I have some questions about your draft-hcl-idr-extend-tunnel-egress-point-00 requesting to expend the Tunnel Egress point. - Is the Tunnel Egress point same as the Tunnel End Point described in RFC9012? The Tunnel Egress Endpoint of RFC9012 is a SubTLV inside the Tunnel Encapsulation Attribute, which is an IPv4 or IPv6 address of the Egress Endpoint. Your draft seems to ask for a new Tunnel Type to the Tunnel Encapsulation Attribute. It would be less confusing if you use a different name. From the attributes described in your draft, this new tunnel type is to list a list of SysPorts for the tunnel. Is it more like asking a Tunnel Type to indicate that there are multiple egress ports? Maybe =E2=80=9CMulti-egress-ports=E2=80=9D Tunnel Type is a= more accurate name? - If you do want to have a tunnel with multiple egress ports, like P2MP (point to multipoint tunnel), then it makes more sense to consider usin= g Multicast protocol to allow each individual port to =E2=80=9CJOIN=E2=80= =9D or =E2=80=9CLEAVE=E2=80=9D the p2MP tunnel. I copied the IDR mailing list. Any extension to BGP needs to be discussed in IDR WG. Thanks, Linda *From:* linchangwang *Sent:* Monday, July 1, 2024 6:03 AM *To:* aidc@ietf.org *Cc:* huopengfei@bytedance.com *Subject:* [aidc] Fw: [Idr] [RTGWG & IDR] Discussing the Open Scheduled fabric of AI Network *=E5=8F=91=E4=BB=B6=E4=BA=BA**:* =E9=9C=8D=E6=9C=8B=E9=A3=9E *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2024=E5=B9=B46=E6=9C=8830=E6=97=A5 = 12:57 *=E6=94=B6=E4=BB=B6=E4=BA=BA:* idr@ietf.org; rtgwg@ietf.org *=E4=B8=BB=E9=A2=98:* [Idr] [RTGWG & IDR] Discussing the Open Scheduled fab= ric of AI Network Hi Wg, Link: https://datatracker.ietf.org/doc/html/draft-hcl-rtgwg-ai-network-problem-00 https://datatracker.ietf.org/doc/html/draft-hcl-rtgwg-osf-framework-00 https://datatracker.ietf.org/doc/html/draft-hcl-idr-extend-tunnel-egress-po= int-00 These documents describe the main disturbances caused by AI applications to the network and propose solutions based on open schedulable network architecture developed to address these issues. It primarily focuses on the following aspects: 1. Open Scheduled Fabric An open network architecture that resolves hash issues through dynamic scheduling based on network measurements. 2. Bgp Extension for Tunnel Egress Point A method for implementing the OSF network architecture involves using BGP uniformly in the control plane, extending the data plane as a new tunnel encapsulation, and providing the necessary control information transmission for the data plane. 3. Extending the BGP protocol to carry Tunnel Egress Point information within the community attribute. We welcome any comments and discussions. Thank you! Thanks, Pengfei ---------------------------------------------------------------------------= ---------------------------------------------------------- =E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84=E4=BB=B6=E5=90=AB=E6= =9C=89=E6=96=B0=E5=8D=8E=E4=B8=89=E9=9B=86=E5=9B=A2=E7=9A=84=E4=BF=9D=E5=AF= =86=E4=BF=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA=8E=E5=8F=91=E9=80=81= =E7=BB=99=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD=E5=88=97=E5=87=BA =E7=9A=84=E4=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84=E3=80=82=E7=A6=81=E6= =AD=A2=E4=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4=BB=A5=E4=BB=BB=E4=BD= =95=E5=BD=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C=85=E6=8B=AC=E4=BD=86= =E4=B8=8D=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96=E9=83=A8=E5=88=86=E5= =9C=B0=E6=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=E3=80=81 =E6=88=96=E6=95=A3=E5=8F=91=EF=BC=89=E6=9C=AC=E9=82=AE=E4=BB=B6=E4=B8=AD=E7= =9A=84=E4=BF=A1=E6=81=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6=82=A8=E9=94=99=E6=94= =B6=E4=BA=86=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF=B7=E6=82=A8=E7=AB=8B= =E5=8D=B3=E7=94=B5=E8=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6=E9=80=9A=E7=9F=A5=E5= =8F=91=E4=BB=B6=E4=BA=BA=E5=B9=B6=E5=88=A0=E9=99=A4=E6=9C=AC =E9=82=AE=E4=BB=B6=EF=BC=81 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! --0000000000003ad2b0061c3eb22e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Linda=EF=BC= =8C

Thanks for your comments.=C2=A0
Yes , we are asking for a new Tunn= el Type. To avoid any confusion over the name, we are considering a new nam= e.
<= span style=3D"font-size:14.6667px">
Thanks, Pengfei=
<= div id=3D"lark-mail-quote-e4be8c02542356c453e5f5bdc03c3527">
From: &qu= ot;Linda Dunbar"<linda.dunbar@futurewei.com>= ;
Date: Tue, Jul 2, 2024, 05:50
Subject: [External] Questions about draft-hcl-idr-extend-tunnel-egress-point
To: "linchangwang"&l= t;linchangwang.04414@h3c.com>, "aidc@ietf.org"<aidc@ietf.org>
Cc: "huopengfei@bytedanc= e.com"<huopengfei@bytedance.com>, "idr@ietf.org"<idr@ietf.o= rg>

<= span style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif">= PengFei,

=C2=A0

I have some questions about your draft-hcl= -idr-extend-tunnel-egress-point-00 requesting to expend the Tunnel Egress p= oint.

  • I= s the Tunnel Egress point same as the Tunnel End Point described in RFC9012= ?

The Tunnel Egress Endpoint of RFC9012 is a SubTLV inside the Tunne= l Encapsulation Attribute, which is an IPv4 or IPv6 address of the Egress E= ndpoint.

Your draft seems to ask for a new Tunnel Type to the Tunnel Encapsulatio= n Attribute.

It would be less confusing if you use a different name. From the attribu= tes described in your draft, this new tunnel type is to list a list of SysP= orts for the tunnel.

Is it more like asking a Tunnel Type to indicate that t= here are multiple egress ports?=C2=A0 Maybe =C2=A0=E2=80=9CMulti-egress-por= ts=E2=80=9D Tunnel Type is a more accurate name?

=C2=A0

  • I= f you do want to have a tunnel with multiple egress ports, like P2MP (point= to multipoint tunnel), =C2=A0then it makes more sense to consider using Multicast protocol to allow each individual port t= o =E2=80=9CJOIN=E2=80=9D or =E2=80=9CLEAVE=E2=80=9D the p2MP tunnel.

=C2=A0

<= p style=3D"margin-left:.5in" class=3D"MsoNormal lme-line-signal">=C2=A0

I copied the IDR mailing li= st. Any extension to BGP needs to be discussed in IDR WG.

=C2=A0

Thanks, Linda

=C2=A0

From: linchangwang <linchangwang.04414@= h3c.com>
Sent: Monday, July 1, 2024 6:03 AM
To: aidc@ietf.org
Cc: huopengfei@bytedance.com
Subject: [aidc] Fw: [Idr] [RTGWG & IDR] Discussing the Open Sche= duled fabric of AI Network

=C2=A0

=C2=A0

=C2=A0

=E5=8F=91= =E4=BB=B6=E4=BA=BA: =E9=9C=8D=E6=9C=8B=E9=A3=9E <huopengfei=3D40bytedance.com@dmarc.ietf.org>
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 20= 24=E5=B9=B46=E6=9C=8830=E6=97=A5 12:57
=E6=94=B6=E4=BB=B6=E4=BA=BA: idr@ietf.org; rtgw= g@ietf.org
=E4=B8=BB=E9=A2=98: [Idr] [RTGWG & I= DR] Discussing the Open Scheduled fabric of AI Network

=C2=A0

Hi Wg,

=C2=A0

Link:

These documents describe the main disturbances caused by AI applicati= ons to the network and propose solutions based on open schedulable network architecture developed to address these issues.

It primarily focuses on the following aspects:

=C2=A0

1. Open Scheduled Fabric

=C2=A0 An open network architecture that resolves has= h issues through dynamic scheduling based on network measurements.

= =C2=A0

2. Bgp Extension for Tunnel Egress P= oint

=C2=A0 A method for implementin= g the OSF network architecture involves using BGP uniformly in the control = plane, extending the data plane as a new tunnel encapsulation, and providing the necessary control information tran= smission for the data plane.=

=C2= =A0

3. Extending the BGP protocol to carry Tunnel Egress Point information w= ithin the community attribute.

=

=C2= =A0

We welcome any comments and discussions.

=C2=A0

Thank you!

=C2=A0<= /span>

<= div>

T= hanks,

Pengfei

-= ---------------------------------------------------------------------------= ---------------------------------------------------------
=E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84= =E4=BB=B6=E5=90=AB=E6=9C=89=E6=96=B0=E5=8D=8E=E4=B8=89=E9=9B=86=E5=9B=A2=E7= =9A=84=E4=BF=9D=E5=AF=86=E4=BF=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA= =8E=E5=8F=91=E9=80=81=E7=BB=99=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD= =E5=88=97=E5=87=BA
=E7=9A=84=E4=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84= =E3=80=82=E7=A6=81=E6=AD=A2=E4=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4= =BB=A5=E4=BB=BB=E4=BD=95=E5=BD=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C= =85=E6=8B=AC=E4=BD=86=E4=B8=8D=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96= =E9=83=A8=E5=88=86=E5=9C=B0=E6=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=E3= =80=81
=E6=88=96=E6=95=A3=E5=8F=91=EF=BC=89=E6=9C=AC=E9=82=AE= =E4=BB=B6=E4=B8=AD=E7=9A=84=E4=BF=A1=E6=81=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6= =82=A8=E9=94=99=E6=94=B6=E4=BA=86=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF= =B7=E6=82=A8=E7=AB=8B=E5=8D=B3=E7=94=B5=E8=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6= =E9=80=9A=E7=9F=A5=E5=8F=91=E4=BB=B6=E4=BA=BA=E5=B9=B6=E5=88=A0=E9=99=A4=E6= =9C=AC
=E9=82=AE=E4=BB=B6=EF=BC=81
This e-mail and its attachments contain confidential inform= ation from New H3C, which is
intended only for the person or entity whose address is listed above. Any u= se of the
information contained herein in any way (including, but not limited to, tot= al or partial
disclosure, reproduction, or dissemination) by persons other than the inten= ded
recipient(s) is prohibited. If you receive this e-mail in error, please not= ify the sender
by phone or email immediately and delete it!

<= /div>
--0000000000003ad2b0061c3eb22e--