Re: [GROW] Agenda Slot Requests - IETF 103
"Guyunan (Yunan Gu, IP Technology Research Dept. NW)" <guyunan@huawei.com> Sun, 04 November 2018 14:11 UTC
Return-Path: <guyunan@huawei.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF57A130E11; Sun, 4 Nov 2018 06:11:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 qcstKROw1NU6; Sun, 4 Nov 2018 06:11:48 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 108C2130E6C; Sun, 4 Nov 2018 06:11:46 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 563A3C5C926C1; Sun, 4 Nov 2018 14:11:41 +0000 (GMT)
Received: from DGGEMI404-HUB.china.huawei.com (10.3.17.142) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 4 Nov 2018 14:11:38 +0000
Received: from DGGEMI524-MBS.china.huawei.com ([169.254.8.58]) by dggemi404-hub.china.huawei.com ([10.3.17.142]) with mapi id 14.03.0399.000; Sun, 4 Nov 2018 22:11:29 +0800
From: "Guyunan (Yunan Gu, IP Technology Research Dept. NW)" <guyunan@huawei.com>
To: "Guyunan (Yunan Gu, IP Technology Research Dept. NW)" <guyunan@huawei.com>, Christopher Morrow <christopher.morrow@gmail.com>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
CC: "<grow-chairs@ietf.org>" <grow-chairs@ietf.org>, "grow-ads@tools.ietf.org" <grow-ads@tools.ietf.org>
Thread-Topic: [GROW] Agenda Slot Requests - IETF 103
Thread-Index: AQHUZv4fb7dUB1O6TUG5/YnyoR14u6UszT+AgADZG5D//3wWAIAAiVQggBIRyRA=
Date: Sun, 04 Nov 2018 14:11:28 +0000
Message-ID: <C01B0098369B2D4391851938DA6700B7D74DE6@DGGEMI524-MBS.china.huawei.com>
References: <CAL9jLaa-aRvVqDW2qs3ar7_i3qjHvthDOiKN6JYhh+aoZH9rKg@mail.gmail.com> <CAL9jLabccdo0ri6trsiLDSv+e9pDifPoYP8hYLOjN2VbAa-1SA@mail.gmail.com> <C01B0098369B2D4391851938DA6700B7D68D5F@DGGEMI524-MBS.china.huawei.com> <CAL9jLabLX85dZRXWVeUkoC4p35T1zUHk+qeBrMtkhwA+sk4zTA@mail.gmail.com> <C01B0098369B2D4391851938DA6700B7D68D8B@DGGEMI524-MBS.china.huawei.com>
In-Reply-To: <C01B0098369B2D4391851938DA6700B7D68D8B@DGGEMI524-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.126.174.147]
Content-Type: multipart/mixed; boundary="_004_C01B0098369B2D4391851938DA6700B7D74DE6DGGEMI524MBSchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/3_tQ1Hb_-7wtUA_oVrvlbJLLLAU>
Subject: Re: [GROW] Agenda Slot Requests - IETF 103
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2018 14:11:52 -0000
Dear Grow members, We have attached the slides to better illustrate our draft: “draft-gu-grow-bmp-route-leak-detection-00”. We basically explained the ideas of 1. The conventional route leak PROTECTION methods; 2. the intra-AS route leak PROTECTION method -- using BGP open policy method proposed by “draft-ietf-idr-bgp-open-policy-03”, and 3. our intra-AS route leak DETECTION method. We believe that our method provides a route leak self-checking method for a single ISP, which is complementary to any existing route leak protection methods as a way of validation. Although we don’t have a slot for discussion tomorrow at the meeting, we do hope to solicit more comments. Thanks. Yunan From: GROW [mailto:grow-bounces@ietf.org] On Behalf Of Guyunan (Yunan Gu, IP Technology Research Dept. NW) Sent: Wednesday, October 24, 2018 9:28 AM To: Christopher Morrow <christopher.morrow@gmail.com>; grow@ietf.org grow@ietf.org <grow@ietf.org> Cc: <grow-chairs@ietf.org> <grow-chairs@ietf.org>; grow-ads@tools.ietf.org Subject: Re: [GROW] Agenda Slot Requests - IETF 103 Hi Chris, Sure! We’d also like to solicit some comments on our draft. Hi, Grow folks, This draft proposes a method for detecting BGP route leaks using BMP. We mainly identified the requirements and concerns for the route leak detection, such as implementation dependency on other ISPs, detection accuracy and so on. We feel that BMP might be a good choice for the detection information collection with minor extension work while meeting these requirements. Please, feel free to comment on either the motivation or solution. https://www.ietf.org/internet-drafts/draft-gu-grow-bmp-route-leak-detection-00.txt Yunan From: Christopher Morrow [mailto:christopher.morrow@gmail.com] Sent: 2018年10月24日 9:46 To: Guyunan (Yunan Gu, IP Technology Research Dept. NW) <guyunan@huawei.com<mailto:guyunan@huawei.com>> Cc: grow@ietf.org<mailto:grow@ietf.org> grow@ietf.org<mailto:grow@ietf.org> <grow@ietf.org<mailto:grow@ietf.org>>; <grow-chairs@ietf.org<mailto:grow-chairs@ietf.org>> <grow-chairs@ietf.org<mailto:grow-chairs@ietf.org>>; grow-ads@tools.ietf.org<mailto:grow-ads@tools.ietf.org> Subject: Re: [GROW] Agenda Slot Requests - IETF 103 Can we get some discussion on-list prior please? On Tue, Oct 23, 2018 at 9:41 PM Guyunan (Yunan Gu, IP Technology Research Dept. NW) <guyunan@huawei.com<mailto:guyunan@huawei.com>> wrote: Hi Chris, I’d like to request a 15 min discussion for “draft-gu-grow-bmp-route-leak-detection-00” Thanks. Yunan A new version of I-D, draft-gu-grow-bmp-route-leak-detection-00.txt has been successfully submitted by Shunwan Zhuang and posted to the IETF repository. Name: draft-gu-grow-bmp-route-leak-detection Revision: 00 Title: BMP for BGP Route Leak Detection Document date: 2018-10-22 Group: Individual Submission Pages: 8 URL: https://www.ietf.org/internet-drafts/draft-gu-grow-bmp-route-leak-detection-00.txt Status: https://datatracker.ietf.org/doc/draft-gu-grow-bmp-route-leak-detection/ Htmlized: https://tools.ietf.org/html/draft-gu-grow-bmp-route-leak-detection-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-gu-grow-bmp-route-leak-detection Abstract: According to RFC7908 [RFC7908], Route leaks refer to case that the delivery range of route advertisements is beyond the expected range. For many current security protection solutions, the ISPs (Internet Service Providers) are focusing on finding ways to detect the happening of route leaks. However, the real-time route leak detection if any occurs is important as well. This document extends the BGP Monitoring Protocol (BMP) [RFC7854] to provide a routing security scheme suitable for ISPs to detect BGP route leaks within their own networks. From: GROW [mailto:grow-bounces@ietf.org<mailto:grow-bounces@ietf.org>] On Behalf Of Christopher Morrow Sent: 2018年10月24日 4:41 To: grow@ietf.org<mailto:grow@ietf.org> grow@ietf.org<mailto:grow@ietf.org> <grow@ietf.org<mailto:grow@ietf.org>>; <grow-chairs@ietf.org<mailto:grow-chairs@ietf.org>> <grow-chairs@ietf.org<mailto:grow-chairs@ietf.org>>; grow-ads@tools.ietf.org<mailto:grow-ads@tools.ietf.org> Subject: Re: [GROW] Agenda Slot Requests - IETF 103 Howdy Grow Folks... topics for discussion? On Thu, Oct 18, 2018 at 12:16 PM Christopher Morrow <christopher.morrow@gmail.com<mailto:christopher.morrow@gmail.com>> wrote: Howdy GrowFolks: Please send along agenda requests as time permits... We are planning to meet in Bangkok, unless no one can find agenda topics? :) -chris
- [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Guyunan (Yunan Gu, IP Technology Research Dept. NW)
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Guyunan (Yunan Gu, IP Technology Research Dept. NW)
- Re: [GROW] Agenda Slot Requests - IETF 103 Sriram, Kotikalapudi (Fed)
- [GROW] Comments on draft-ietf-idr-route-leak-dete… Sriram, Kotikalapudi (Fed)
- Re: [GROW] Agenda Slot Requests - IETF 103 Paolo Lucente
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Randy Bush
- Re: [GROW] Agenda Slot Requests - IETF 103 Job Snijders
- Re: [GROW] Agenda Slot Requests - IETF 103 Guyunan (Yunan Gu, IP Technology Research Dept. NW)
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Guyunan (Yunan Gu, IP Technology Research Dept. NW)
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Paolo Lucente
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow
- Re: [GROW] Agenda Slot Requests - IETF 103 Paolo Lucente
- Re: [GROW] Agenda Slot Requests - IETF 103 Christopher Morrow