[happy] Re: Happy @ IETF 126 - calls for agenda items

Xipengxiao <xipengxiao@huawei.com> Fri, 03 July 2026 14:14 UTC

Return-Path: <xipengxiao@huawei.com>
X-Original-To: happy@mail2.ietf.org
Delivered-To: happy@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id C571110DBA978 for <happy@mail2.ietf.org>; Fri, 3 Jul 2026 07:14:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783088046; bh=+E23h7EjDXN92nBq9ThZTo77R2GItx8VRXKcCOlTiuE=; h=From:To:CC:Subject:Date; b=ZUAenGf5IadbNLFer0V1RYTVxBvUNXg5cUaX5JzyfemH1+2XFfWjsbjSBC2K7ZnPs exIaDd2Wz0K/THy7MwzFZA/OOGRNTXGzPfDBVexldZ4PBRKITcCprdwSz9J8ZenMDG TKAfyRzCkH2gqukgin/jGyZEq7+4c6Mvy5SCxBF8=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EixaLEUUNDKQ for <happy@mail2.ietf.org>; Fri, 3 Jul 2026 07:14:05 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D543210DBA967 for <happy@ietf.org>; Fri, 3 Jul 2026 07:14:04 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.224.150]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4gsG1j17NVzHnGgn; Fri, 3 Jul 2026 22:13:13 +0800 (CST)
Received: from frapema100004.china.huawei.com (unknown [7.182.19.128]) by mail.maildlp.com (Postfix) with ESMTPS id 7B8EF40571; Fri, 3 Jul 2026 22:14:03 +0800 (CST)
Received: from frapema500003.china.huawei.com (7.182.19.114) by frapema100004.china.huawei.com (7.182.19.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Fri, 3 Jul 2026 16:14:03 +0200
Received: from frapema500003.china.huawei.com ([7.182.19.114]) by frapema500003.china.huawei.com ([7.182.19.114]) with mapi id 15.02.1544.011; Fri, 3 Jul 2026 16:14:03 +0200
From: Xipengxiao <xipengxiao@huawei.com>
To: Tim Chown <Tim.Chown@jisc.ac.uk>, "ekinnear@apple.com" <ekinnear@apple.com>
Thread-Topic: Re: [happy] Happy @ IETF 126 - calls for agenda items
Thread-Index: Ad0K9MsQepjuSIGFTsmdEv5zAj0J5A==
Date: Fri, 03 Jul 2026 14:14:03 +0000
Message-ID: <d5a4e24a915e475d8769e340f688de37@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.221.76.221]
Content-Type: multipart/alternative; boundary="_000_d5a4e24a915e475d8769e340f688de37huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: NOSZ3GTCU6GFEEX3D4PSVQ4EFUAUB7LK
X-Message-ID-Hash: NOSZ3GTCU6GFEEX3D4PSVQ4EFUAUB7LK
X-MailFrom: xipengxiao@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "happy@ietf.org" <happy@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [happy] Re: Happy @ IETF 126 - calls for agenda items
List-Id: "Discussion list for Heuristics and Algorithms to Prioritize Protocol deploYment (HAPPY)" <happy.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/happy/rM9Re3u-IX8e1hT3R6BiqsVYLpM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/happy>
List-Help: <mailto:happy-request@ietf.org?subject=help>
List-Owner: <mailto:happy-owner@ietf.org>
List-Post: <mailto:happy@ietf.org>
List-Subscribe: <mailto:happy-join@ietf.org>
List-Unsubscribe: <mailto:happy-leave@ietf.org>

Hi Tim, Eric,

I would like to request a 10m slot to present "Enhanced Dual Stack and the Need for an HEv3 OS Implementation Profile".  The related Enhanced Dual Stack (EDS) draft is: https://datatracker.ietf.org/doc/draft-xiao-v6ops-eds/

Thank you.

XiPeng