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

霍朋飞 <huopengfei@bytedance.com> Mon, 01 July 2024 02:56 UTC

Return-Path: <huopengfei@bytedance.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 0F563C151552 for <idr@ietfa.amsl.com>; Sun, 30 Jun 2024 19:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=unavailable 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 Ll97chVcTY1X for <idr@ietfa.amsl.com>; Sun, 30 Jun 2024 19:56:33 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 C8D3FC1516EA for <idr@ietf.org>; Sun, 30 Jun 2024 19:56:33 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a724958f118so283398166b.0 for <idr@ietf.org>; Sun, 30 Jun 2024 19:56:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance.com; s=google; t=1719802591; x=1720407391; darn=ietf.org; h=cc:to:subject:message-id:date:in-reply-to:references:mime-version :from:from:to:cc:subject:date:message-id:reply-to; bh=hRRAqtalYsFoNe6bFmFWANGneC5uJkyj5pDYs8bWPqA=; b=I0/VtyynwwMzfWyEuBXOMZl3P6wKd/AQxcYzU7nOOe+VBBgmPUeUx0CX5K8QdY2bU+ 27cvDAGLskoY9QDKRWvxiUYWSxmoykF05zFGxmBhwS7klzkrVSN5We1z/NdWzgwKn8lX sG1hlOUQDzvqfIca7M1zT4nlXApp0zqQL9zm4HR7kqpRnD+DcQOzWGpY5eHFrlrk920K czF1TgTb2moPxrfu3nfeyTN2ArvJqIVR0UiPzEm/rPRQaN/lyQKfFDYkx4Ccpya53rbQ 7lIC6QOzrsZd7Qk27eWWjQVldHTqdjKZxgXOqnRqGbKZMLJ1qj+JsUjDnr6Aq+3JXyOt 8vhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719802591; x=1720407391; h=cc:to:subject:message-id:date:in-reply-to:references:mime-version :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=hRRAqtalYsFoNe6bFmFWANGneC5uJkyj5pDYs8bWPqA=; b=WoPUtz3LzZmY/m7nfznVCPUmMcNKU4bXsH7WXdZNQNqD3q4E20pYHUTDBwbNb15bjt coCCtKPvBUaPXeQ2bVLbb/2ZA3bxnbaa+PHKt8CYQ51zYXKvzldUj3McdXKKvs4hDTzL nKW2fCotunNEhjNEX2tEziToRhCGDZVU3eJPz+cmePoB47q115yCGBllIMajOz5ZKYWH AJVV/cyos5QscbbglgyUQad8CEbsZdWMx0EWJZt/3v7PgSWpy8wmGKgvSBfAYVCcbQpY vgcxJCe21dHC4mqbXA/vO+plVyqeu8kPHErjlDNexCL8Hl6ewTJ6LDWvZ0QZ2EfayeM1 4jVA==
X-Gm-Message-State: AOJu0YwtBcS6GjY7eiJM8xNqr4RWCtgLFFqnfvW4AqoCn1/CQ9oCWR+5 repsko8tP8mQbH4hd9HkO/uPmeQMeXjkYanMLke3de9nD14atOKb/Ghwab/SUFJATJ2GiXQFR+M iGqRUeySLbzSkbA7V4j3uuoL5/6ORH3/c8iAtzzjICIAzVqar
X-Google-Smtp-Source: AGHT+IERV8bO1u8FBv2josU06Y9KQfPz5ndMJn0eYKgsjqAbNawd3ebPyIGwuwAqJXa98C5lNCF8Z0LSxjxlXj3Em+Y=
X-Received: by 2002:a17:906:280e:b0:a6f:dc17:500a with SMTP id a640c23a62f3a-a751445463dmr285758666b.23.1719802590735; Sun, 30 Jun 2024 19:56:30 -0700 (PDT)
Received: from 44278815321 named unknown by gmailapi.google.com with HTTPREST; Sun, 30 Jun 2024 19:56:30 -0700
From: 霍朋飞 <huopengfei@bytedance.com>
Mime-Version: 1.0
References: <135c28ca8d754b1796b40e52939319e7@h3c.com> <2f0a1d1b-d6bc-4b40-9224-61d2751b2181@chinamobile.com>
In-Reply-To: <2f0a1d1b-d6bc-4b40-9224-61d2751b2181@chinamobile.com>
Date: Sun, 30 Jun 2024 19:56:30 -0700
Message-ID: <CA++4kv-GkoUirqHeL76HcbgCHU6c4RwKoPO4nAAuOkBFJc4Qmg@mail.gmail.com>
To: idr-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000814753061c26bece"
Message-ID-Hash: VK2R36F4LHEF26QMM5OOCZQXZXPIZDIJ
X-Message-ID-Hash: VK2R36F4LHEF26QMM5OOCZQXZXPIZDIJ
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: "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/sDvH90gXJWXCwlOXytKt01Z8tYo>
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 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/
<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>
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>, <idr-chairs@ietf.org>
Cc: <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>
*发送时间:* 2024年6月23日 20:24
*收件人:* idr@ietf.org
*抄送:* 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>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://urldefense.com/v3/__https:/trac.tools.ietf.org/wg/idr/trac/wiki/Checklist*20for*20presenting*20at*20an*20IDR*20meeting__;JSUlJSUl!!NEt6yMaO-gk!H0d2cKb4ME4YwpAXW-GuKym9OzLXapx8haPiHMIXz25yrj1K78xsZv9sOxTbkgub87OvOQVZW8Ic-Xyo5eC2eX32W6wXwOY$>
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 (杨锋)