Re: [Idr] Call for IETF113 IDR agenda items

"Dongjie (Jimmy)" <jie.dong@huawei.com> Wed, 23 February 2022 16:18 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 B55BB3A112D; Wed, 23 Feb 2022 08:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w5OlLH9UcmhJ; Wed, 23 Feb 2022 08:18:49 -0800 (PST)
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 0DE263A1131; Wed, 23 Feb 2022 08:18:49 -0800 (PST)
Received: from fraeml706-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4K3h1L0szVz67Cp2; Thu, 24 Feb 2022 00:13:58 +0800 (CST)
Received: from dggeme704-chm.china.huawei.com (10.1.199.100) by fraeml706-chm.china.huawei.com (10.206.15.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.21; Wed, 23 Feb 2022 17:18:45 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme704-chm.china.huawei.com (10.1.199.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.21; Thu, 24 Feb 2022 00:18:43 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.2308.021; Thu, 24 Feb 2022 00:18:43 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Randy Bush <randy@psg.com>
CC: idr chairs <idr-chairs@ietf.org>, Interminable Discussion Room <idr@ietf.org>
Thread-Topic: [Idr] Call for IETF113 IDR agenda items
Thread-Index: Adgm9HDZQvDpfgPIScC5XgxvRK1SvwBO+myAACgac/A=
Date: Wed, 23 Feb 2022 16:18:43 +0000
Message-ID: <0b335480b88a400086989bbca0803ddd@huawei.com>
References: <45e2623445a6437f9f68b0ddf05e694d@huawei.com> <m2czjemap8.wl-randy@psg.com>
In-Reply-To: <m2czjemap8.wl-randy@psg.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.239.25]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ebTlGPzlO--v8S72bWgRsZhCwZE>
Subject: Re: [Idr] Call for IETF113 IDR agenda items
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2022 16:18:54 -0000

Hi Randy, 

Your slot request is acked. Please pay attention to the draft idr agenda when posted. Thanks.

Best regards,
Jie

> -----Original Message-----
> From: Randy Bush [mailto:randy@psg.com]
> Sent: Wednesday, February 23, 2022 1:09 PM
> To: Dongjie (Jimmy) <jie.dong@huawei.com>
> Cc: idr chairs <idr-chairs@ietf.org>; Interminable Discussion Room
> <idr@ietf.org>
> Subject: Re: [Idr] Call for IETF113 IDR agenda items
> 
> it is probably worth 10-15 minutes to discuss some of the tradeoffs taken in
> 
>     draft-ymbk-idr-l3nd
>     draft-ymbk-idr-l3nd-ulpc
> 
> ( this is NOT L3DL, but layer-3 )
> 
> and try to start getting some consensus on them.  the big ones might be
>   - the L3 multicast HELLO
>   - TLS, naked TCP, and the trust model
>   - restart
> 
> randy