[Idr] Re: [External] Questions about draft-hcl-idr-extend-tunnel-egress-point

[霍朋飞 <[e-mail]>]

Hi Linda，

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"<[e-mail]>
Date: Tue, Jul 2, 2024, 05:50
Subject: [External] Questions about draft-hcl-idr-extend-tunnel-egress-point
To: "linchangwang"<[e-mail]>, "[e-mail]"<
[e-mail]>
Cc: "[e-mail]"<[e-mail]>, "[e-mail]"<
[e-mail]>

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  “Multi-egress-ports” 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 using
   Multicast protocol to allow each individual port to “JOIN” or “LEAVE” the
   p2MP tunnel.





I copied the IDR mailing list. Any extension to BGP needs to be discussed
in IDR WG.



Thanks, Linda



*From:* linchangwang <[e-mail]>
*Sent:* Monday, July 1, 2024 6:03 AM
*To:* [e-mail]
*Cc:* [e-mail]
*Subject:* [aidc] Fw: [Idr] [RTGWG & IDR] Discussing the Open Scheduled
fabric of AI Network







*发件人**:* 霍朋飞 <huopengfei=[e-mail]>
*发送时间:* 2024年6月30日 12:57
*收件人:* [e-mail]; [e-mail]
*主题:* [Idr] [RTGWG & IDR] Discussing the Open Scheduled fabric 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-ai-network-problem-00

<https://datatracker.ietf.org/doc/html/draft-hcl-rtgwg-osf-framework-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-point-00>
https://datatracker.ietf.org/doc/html/draft-hcl-idr-extend-tunnel-egress-point-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

-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
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!