[Idr] Re: [External] Re: Call for IETF 120 IDR agenda items

"Dongjie (Jimmy)" <jie.dong@huawei.com> Mon, 01 July 2024 12:53 UTC

Return-Path: <jie.dong@huawei.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 9EE11C18DB8A; Mon, 1 Jul 2024 05:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
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 8anLtEX75H1T; Mon, 1 Jul 2024 05:53:28 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE991C18DB83; Mon, 1 Jul 2024 05:53:27 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4WCQsM1DYBz6K9XM; Mon, 1 Jul 2024 20:51:35 +0800 (CST)
Received: from lhrpeml100005.china.huawei.com (unknown [7.191.160.25]) by mail.maildlp.com (Postfix) with ESMTPS id DC9E21400D1; Mon, 1 Jul 2024 20:53:24 +0800 (CST)
Received: from dggpemf200007.china.huawei.com (7.185.36.2) by lhrpeml100005.china.huawei.com (7.191.160.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Mon, 1 Jul 2024 13:53:23 +0100
Received: from kwepemf100006.china.huawei.com (7.202.181.220) by dggpemf200007.china.huawei.com (7.185.36.2) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Mon, 1 Jul 2024 20:53:21 +0800
Received: from kwepemf100006.china.huawei.com ([7.202.181.220]) by kwepemf100006.china.huawei.com ([7.202.181.220]) with mapi id 15.02.1544.011; Mon, 1 Jul 2024 20:53:21 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: 霍朋飞 <huopengfei=40bytedance.com@dmarc.ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Thread-Topic: [Idr] Re: [External] Re: Call for IETF 120 IDR agenda items
Thread-Index: AQHaySwsO8+kraHNTa2IfQ7qUBj2+LHgrBcAgAErw8A=
Date: Mon, 01 Jul 2024 12:53:21 +0000
Message-ID: <5a2c2aeb55534a259beaf5f00125d5aa@huawei.com>
References: <135c28ca8d754b1796b40e52939319e7@h3c.com> <2f0a1d1b-d6bc-4b40-9224-61d2751b2181@chinamobile.com> <CA++4kv-GkoUirqHeL76HcbgCHU6c4RwKoPO4nAAuOkBFJc4Qmg@mail.gmail.com>
In-Reply-To: <CA++4kv-GkoUirqHeL76HcbgCHU6c4RwKoPO4nAAuOkBFJc4Qmg@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.170.96]
Content-Type: multipart/alternative; boundary="_000_5a2c2aeb55534a259beaf5f00125d5aahuaweicom_"
MIME-Version: 1.0
Message-ID-Hash: IUJNYK535OATTLXUZLV2E7LVV3GD3S4E
X-Message-ID-Hash: IUJNYK535OATTLXUZLV2E7LVV3GD3S4E
X-MailFrom: jie.dong@huawei.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>, "li_meng_limeng@h3c.com" <li_meng_limeng@h3c.com>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: [External] Re: Call for IETF 120 IDR agenda items
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/XQ--C59n05h3T7ez38SiP95Qh1g>
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>

Hi Pengfei,

Your slot request is acked, please pay attention to the draft idr agenda when posted.

Best regards,
Jie

From: 霍朋飞 <huopengfei=40bytedance.com@dmarc.ietf.org>
Sent: Monday, July 1, 2024 10:57 AM
To: idr-chairs@ietf.org
Cc: idr@ietf.org; li_meng_limeng@h3c.com
Subject: [Idr] Re: [External] Re: Call for IETF 120 IDR agenda items

Hi chairs & Jie,
I would like to request 10 mins to present  the new version of  draft-hcl-idr-extend-tunnel-egress-point

In AI networks, flow characteristics often exhibit a low number of
   flows but with high bandwidth per flow, making it easy to cause
   network congestion when using traditional flow-level load balancing
   methods. Currently, the direction of traffic scheduling focuses on
   load sharing individual packets of the same flow, which requires
   sorting based on the Tunnel Egress Point information from the remote
   end.

This document describes the method of publishing Tunnel Egress
   Point through the BGP protocol.


The link is:https://datatracker.ietf.org/doc/draft-hcl-idr-extend-tunnel-egress-point/
Presenter:  PengFei Huo<https://datatracker.ietf.org/person/huopengfei@bytedance.com>

Thanks,
PengFei
From: "Feng Yang"<yangfeng@chinamobile.com<mailto:yangfeng@chinamobile.com>>
Date: Fri, Jun 28, 2024, 15:25
Subject: [External] [Idr] Re: Call for IETF 120 IDR agenda items
To: "Dongjie (Jimmy)"<jie.dong@huawei.com<mailto:jie.dong@huawei.com>>, <idr-chairs@ietf.org<mailto:idr-chairs@ietf.org>>
Cc: <idr@ietf.org<mailto:idr@ietf.org>>
Hi chairs & Jie,

I would like to request 5 mins to present  the new version of  draft-yang-idr-sr-policy-weight-timerange-00


Where there are multiple segment list paths, traffic

   load balancing can be achieved based on the weight value assigned to

   each path. Typically, the weight value for each path is fixed.


This document defines an extension of BGP SR Policy for setting the

   weight value for each path based on time range.


The link is:https://datatracker.ietf.org/doc/html/draft-yang-idr-sr-policy-weight-timerange-00

Presenter:  Feng Yang

发件人: Dongjie (Jimmy) <jie.dong=40huawei.com@dmarc.ietf.org<mailto:jie.dong=40huawei.com@dmarc.ietf.org>>
发送时间: 2024年6月23日 20:24
收件人: idr@ietf.org<mailto:idr@ietf.org>
抄送: idr-chairs@ietf.org<mailto:idr-chairs@ietf.org>
主题: [Idr] Call for IETF 120 IDR agenda items

Dear all,

The preliminary agenda of IETF 120 is available at https://datatracker.ietf.org/meeting/120/agenda. IDR will meet twice this time:

- Monday Session I  9:30 - 11:30 (local time)   Plaza B
- Friday Session III  15:30 - 17:00 (local time)  Plaza B

Please start to send any IDR agenda item request to me and CC the chairs (idr-chairs@ietf.org<mailto:idr-chairs@ietf.org>). Please include the name of the person who will be presenting, and the estimate time you'll need (including Q/A).

If you plan to make a presentation, please keep in mind the IDR tradition, "no Internet Draft - no time slot". You should also plan to send your slides to me and CC the chairs no later than 24 hours prior to the IDR session, though earlier is better. Please number your slides for the benefit of remote attendees. By default your slides will be converted to PDF and presented from the PDF. If you do need to use any fancy builds or transitions, please make sure to arrange this with us in advance to avoid any surprise. Thanks.

Potential presenters may want to take a look at the checklist for presenting at IDR:

https://trac.tools.ietf.org/wg/idr/trac/wiki/Checklist%20for%20presenting%20at%20an%20IDR%20meeting


Best regards,
Jie

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

--

BR,

Feng Yang (杨锋)