IETF Logo Mail Archive

Re: [Idr] Call for IETF102 IDR agenda items

"Dongjie (Jimmy)" <jie.dong@huawei.com> Tue, 26 June 2018 03:44 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 24D25130F3B; Mon, 25 Jun 2018 20:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 WLFn5lzOsmh9; Mon, 25 Jun 2018 20:44:43 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC5AC130F65; Mon, 25 Jun 2018 20:44:42 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7474469CAF283; Tue, 26 Jun 2018 04:44:36 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 26 Jun 2018 04:44:37 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0382.000; Tue, 26 Jun 2018 11:44:27 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "Chengli (IP Technology Research)" <chengli13@huawei.com>, "idr@ietf.org" <idr@ietf.org>
CC: "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "draft-li-idr-bgp-ls-sr-policy-path-segment@ietf.org" <draft-li-idr-bgp-ls-sr-policy-path-segment@ietf.org>, "draft-li-idr-sr-policy-path-segment-distribution@ietf.org" <draft-li-idr-sr-policy-path-segment-distribution@ietf.org>, "Miaofuyou (Miao Fuyou)" <fuyou.miao@huawei.com>
Thread-Topic: Call for IETF102 IDR agenda items
Thread-Index: AdQH4YKyPitT1raYStS5jGIqdLv3hAFEp4ZAAACEstAAAlGnsA==
Date: Tue, 26 Jun 2018 03:44:26 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C927A6E03138@NKGEML515-MBX.china.huawei.com>
References: <76CD132C3ADEF848BD84D028D243C927A6D35F0C@NKGEML515-MBX.china.huawei.com> <76CD132C3ADEF848BD84D028D243C927A6E01B3F@NKGEML515-MBX.china.huawei.com> <C7C2E1C43D652C4E9E49FE7517C236CB01988D0A@dggeml509-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB01988D0A@dggeml509-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.151.75]
Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C927A6E03138NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GXToOiSbrZRreSCT7oAwWCahmdw>
Subject: Re: [Idr] Call for IETF102 IDR agenda items
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 26 Jun 2018 03:44:47 -0000

Hi Cheng,

Your slot request is acknowledged.

Best regards,
Jie

From: Chengli (IP Technology Research)
Sent: Tuesday, June 26, 2018 10:42 AM
To: Dongjie (Jimmy) <jie.dong@huawei.com>; idr@ietf.org
Cc: idr-chairs@ietf.org; draft-li-idr-bgp-ls-sr-policy-path-segment@ietf.org; draft-li-idr-sr-policy-path-segment-distribution@ietf.org; Miaofuyou (Miao Fuyou) <fuyou.miao@huawei.com>
Subject: RE: Call for IETF102 IDR agenda items

Hi,

Request a slot to discuss Path Segment in BGP and BGP-LS:

Drafts:
https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segment-distribution/
https://datatracker.ietf.org/doc/draft-li-idr-bgp-ls-sr-policy-path-segment/

Presenter: Cheng Li

Duration: 10 mins

Reason:  Path Segment is required for identifying an SR-MPLS and SRv6 path in an SR network, and its BGP and BGP-LS extensions are very important for implementation.
A quick presentation will help people to understand the whole picture of these two drafts better.

Thanks!
Cheng


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Dongjie (Jimmy)
Sent: Wednesday, June 20, 2018 9:35 AM
To: idr@ietf.org<mailto:idr@ietf.org>
Cc: idr-chairs@ietf.org<mailto:idr-chairs@ietf.org>
Subject: [Idr] Call for IETF102 IDR agenda items

Dear all,

The agenda of IETF 102 has been published. IDR will meet twice, the first session is on Thursday (July 19th) 18:10-19:10, the second session is on Friday (July 20th) 11:50-13:20. It is planned to have one session for FlowSpec related topics, and the other session for other stuff.

Please send any IDR agenda items you might have to me and CC the chairs. 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 meeting, though earlier is better. If we don't have your slides by the deadline, you may lose your slot. 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 need to use any fancy builds or transitions, please make sure to arrange this with us in advance. Thanks.

And potential presenters, please take a look at the checklist for presenting at IDR:
https://trac.tools.ietf.org/wg/idr/trac/wiki/Checklist%20for%20presenting%20at%20an%20IDR%20meeting

Best regards,
Jie

v2.23.0 | Report a Bug | By Email