IETF Logo Mail Archive

[Idr] Re: Call for IETF 121 IDR agenda items

"Dongjie (Jimmy)" <jie.dong@huawei.com> Tue, 22 October 2024 01:19 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 ADA8CC15109A; Mon, 21 Oct 2024 18:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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] autolearn=ham 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 XB0kuWgCAtjG; Mon, 21 Oct 2024 18:19:58 -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 5EEAFC14F71D; Mon, 21 Oct 2024 18:19:58 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4XXZ854Yv6z6D8Wg; Tue, 22 Oct 2024 09:19:01 +0800 (CST)
Received: from lhrpeml100003.china.huawei.com (unknown [7.191.160.210]) by mail.maildlp.com (Postfix) with ESMTPS id 6D4DD1400DB; Tue, 22 Oct 2024 09:19:55 +0800 (CST)
Received: from dggpemf100007.china.huawei.com (7.185.36.214) by lhrpeml100003.china.huawei.com (7.191.160.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Tue, 22 Oct 2024 02:19:54 +0100
Received: from kwepemf100006.china.huawei.com (7.202.181.220) by dggpemf100007.china.huawei.com (7.185.36.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Tue, 22 Oct 2024 09:19:52 +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; Tue, 22 Oct 2024 09:19:52 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>, Jeffrey Haas <jhaas@pfrc.org>
Thread-Topic: Call for IETF 121 IDR agenda items
Thread-Index: AdsZbCM+8/nvE9I9TX60nGigx2m+3gAPzG0gAnUE6AAABEPPgAAj10hg
Date: Tue, 22 Oct 2024 01:19:52 +0000
Message-ID: <8d133fba29ae473ea1a1a94b28f6b1e6@huawei.com>
References: <bfe525ff58794a7b977b065dc73eae22@huawei.com> <CO1PR13MB492020197388D61AA999398E857E2@CO1PR13MB4920.namprd13.prod.outlook.com> <4E503AE9-1C76-4659-8BD4-3119CB9BB7A7@pfrc.org> <CO1PR13MB4920F4F43EECE33E2834644585432@CO1PR13MB4920.namprd13.prod.outlook.com>
In-Reply-To: <CO1PR13MB4920F4F43EECE33E2834644585432@CO1PR13MB4920.namprd13.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.66]
Content-Type: multipart/alternative; boundary="_000_8d133fba29ae473ea1a1a94b28f6b1e6huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: 5H4PJWSVWTJTN6UFXMSN6V7KZNROXOAX
X-Message-ID-Hash: 5H4PJWSVWTJTN6UFXMSN6V7KZNROXOAX
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>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Re: Call for IETF 121 IDR agenda items
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/2vE4TJoOZdDesT7ZBPwRJ4Koe_k>
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 Linda,

Yes I will update your slot request to 10 mins.

-Jie

From: Linda Dunbar [mailto:linda.dunbar@futurewei.com]
Sent: Tuesday, October 22, 2024 12:09 AM
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Dongjie (Jimmy) <jie.dong=40huawei.com@dmarc.ietf.org>; idr@ietf.org; idr-chairs@ietf.org
Subject: RE: Call for IETF 121 IDR agenda items

Jeff,

Thank you very much for the suggestion. I will prepare the slides per your suggestion.

Jie: Can you allocate 10 minutes for us?

Linda

From: Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>
Sent: Monday, October 21, 2024 7:07 AM
To: Linda Dunbar <linda.dunbar@futurewei.com<mailto:linda.dunbar@futurewei.com>>
Cc: Dongjie (Jimmy) <jie.dong=40huawei.com@dmarc.ietf.org<mailto:jie.dong=40huawei.com@dmarc.ietf.org>>; idr@ietf.org<mailto:idr@ietf.org>; idr-chairs@ietf.org<mailto:idr-chairs@ietf.org>
Subject: Re: Call for IETF 121 IDR agenda items

Linda,


On Oct 8, 2024, at 1:57 PM, Linda Dunbar <linda.dunbar@futurewei.com<mailto:linda.dunbar@futurewei.com>> wrote:

Jie, IDR chairs,

Can we get a 5 (or 10)  minutes slot to brief the major changes to draft-ietf-idr-5g-edge-service-metadata-24?

I'd like to suggest 10 minutes.

I'd also like to suggest specific items to be covered during your update in addition to the editorial changes done for -24:

1. An overview of how this mechanism is intended to be deployed.  In particular, what routes should get the metadata attribute.
2. How route selection is intended to be used for routes with the metadata attribute to accomplish the goals in 1.
3. An overview of the limited-domain deployment scenario.  This would be a good place to discuss intentions on how such a domain is defined and provisioned along with attribute escape prevention mechanisms.

Thanks!

-- Jeff

v2.46.0 | Report a Bug | By Email | System Status