IETF Logo Mail Archive

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

Jeffrey Haas <jhaas@pfrc.org> Mon, 21 October 2024 14:06 UTC

Return-Path: <jhaas@pfrc.org>
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 4C622C1E55C0; Mon, 21 Oct 2024 07:06:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 qZ-aUrTIEKkU; Mon, 21 Oct 2024 07:06:47 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 72F97C18DB87; Mon, 21 Oct 2024 07:06:47 -0700 (PDT)
Received: from smtpclient.apple (172-125-100-52.lightspeed.livnmi.sbcglobal.net [172.125.100.52]) by slice.pfrc.org (Postfix) with ESMTPSA id F309A1E039; Mon, 21 Oct 2024 10:06:46 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_4D8F0150-F475-4A4D-AF80-3A9793B97F4B"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.10\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <CO1PR13MB492020197388D61AA999398E857E2@CO1PR13MB4920.namprd13.prod.outlook.com>
Date: Mon, 21 Oct 2024 10:06:46 -0400
Message-Id: <4E503AE9-1C76-4659-8BD4-3119CB9BB7A7@pfrc.org>
References: <bfe525ff58794a7b977b065dc73eae22@huawei.com> <CO1PR13MB492020197388D61AA999398E857E2@CO1PR13MB4920.namprd13.prod.outlook.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>
X-Mailer: Apple Mail (2.3696.120.41.1.10)
Message-ID-Hash: 4ZZO2KEX3CTSXYQE36PT5X5RQ7FMPLJZ
X-Message-ID-Hash: 4ZZO2KEX3CTSXYQE36PT5X5RQ7FMPLJZ
X-MailFrom: jhaas@pfrc.org
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: "Dongjie (Jimmy)" <jie.dong=40huawei.com@dmarc.ietf.org>, "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/dFp3VTxQywIUpMbxvMSyanqACt0>
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>

Linda,


> On Oct 8, 2024, at 1:57 PM, Linda Dunbar <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