[Idr] 答复: Call for IETF107 IDR agenda items

wangyali <wangyali11@huawei.com> Fri, 13 March 2020 11:04 UTC

Return-Path: <wangyali11@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3BD273A15C6; Fri, 13 Mar 2020 04:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id EctpzVfmC6eY; Fri, 13 Mar 2020 04:04:44 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (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 394493A15C3; Fri, 13 Mar 2020 04:04:44 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 57F80E0407E2905AC190; Fri, 13 Mar 2020 11:04:41 +0000 (GMT)
Received: from DGGEML401-HUB.china.huawei.com ( by LHREML711-CAH.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 13 Mar 2020 11:04:40 +0000
Received: from DGGEML524-MBX.china.huawei.com ([]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0439.000; Fri, 13 Mar 2020 19:04:28 +0800
From: wangyali <wangyali11@huawei.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "idr@ietf.org" <idr@ietf.org>
CC: "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Thread-Topic: Call for IETF107 IDR agenda items
Thread-Index: AdXunrcdMKoa4WeRSgShAXufYV34nwJbSdsAAAnJI9A=
Date: Fri, 13 Mar 2020 11:04:28 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F404DB31D6@dggeml524-mbx.china.huawei.com>
References: <e0f57c32ee21457aaf5544b329caed66@huawei.com>
In-Reply-To: <e0f57c32ee21457aaf5544b329caed66@huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_1520992FC97B944A9979C2FC1D7DB0F404DB31D6dggeml524mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/sJVNwpm7g-fgwln-X6KpvpOVfuQ>
Subject: [Idr] 答复: Call for IETF107 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: Fri, 13 Mar 2020 11:04:46 -0000

Hi Jimmy, WG

This is Yali. I would link to request a presentation time slot for following two drafts. Comments are welcome. Thank you.

>>#1 Title: Extensions to BGP-LS for Advertising In-situ Flow Information Telemetry (IFIT) Node Capability (draft-wang-idr-bgp-ls-ifit-node-capability-03)
Presenter: Yali Wang
Duration: 10 min
This document defines a way for a Border Gateway Protocol Link-State
(BGP-LS) speaker to announce In-situ Flow Information Telemetry
(IFIT) node capabilities of routers to BGP-LS consumer (e.g. a
centralized controller). In this document, IFIT Node Capability TLV
is defined as a new Node Attribute TLV that is encoded in the BGP-LS
attribute with Node NLRIs [RFC7752]. Such advertisements enable a
centralized controller that can leverage this information in
determining whether a particular IFIT Option type can be supported in
a given network.

>>#2 Title: BGP Flow Specification Extensions to Enable In-situ Flow Information Telemetry (IFIT) (draft-liu-idr-flowspec-ifit-03)
Presenter: Yali Wang
Duration: 10 min
BGP Flowspec mechanism propagates both traffic Flow Specifications
and Traffic Filtering Actions by making use of the BGP NLRI and the
  BGP Extended Community encoding formats.  This document specifies a
   new BGP Extended Community named IFIT Action Specific Extended
   Community to distribute In-situ Flow Information Telemetry (IFIT)
   actions so as to address the automatic deployment of IPv6 unicast
   and VPNv6 unicast on-path flow telemetry.

Best regards,

From: Dongjie (Jimmy)
Sent: Saturday, February 29, 2020 9:32 AM
To: idr@ietf.org<mailto:idr@ietf.org>
Cc: idr-chairs@ietf.org<mailto:idr-chairs@ietf.org>
Subject: Call for IETF107 IDR agenda items

Dear all,

The final agenda of IETF 107 is available at https://datatracker.ietf.org/meeting/107/agenda.html. IDR has two sessions:

Session 1: Monday, 23 March 2020, Morning Session I 1000-1200
Room Name: Regency F

Session 2: Tuesday, 24 March 2020, Afternoon Session II 1550-1720
Room Name: Regency D

Please start to send any IDR agenda item request 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). You may also indicate which session you would prefer.

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. 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 do need to use any fancy builds or transitions, please make sure to arrange this with us in advance to avoid any surprise. Thanks.

And potential presenters, please take a look at the checklist for presenting at IDR:

Best regards,