Re: [GROW] Agenda Slot Requests - IETF 103
Christopher Morrow <christopher.morrow@gmail.com> Mon, 05 November 2018 02:09 UTC
Return-Path: <christopher.morrow@gmail.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 5D572127333; Sun, 4 Nov 2018 18:09:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 SGbwx_sdvJnE; Sun, 4 Nov 2018 18:09:54 -0800 (PST)
Received: from mail-it1-x12b.google.com (mail-it1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9E09126BED; Sun, 4 Nov 2018 18:09:53 -0800 (PST)
Received: by mail-it1-x12b.google.com with SMTP id k206-v6so10644202ite.0; Sun, 04 Nov 2018 18:09:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GqaBeqpxGU9fIUnLtnQETNecBeX8dexoh6583DDk5vg=; b=SJy0Koh/H0isxPDaufaL6B3C8NaIDct2Ovg/NNnX2CQY5Luy2LtBtpDcQb6Zch2jqx 5prpmub22cF3Run9s69qbF7pRtf0hdZ20CvdLy4sly+GffePSZJWB33hw2CQM3/RJBaA dCoWOWSOfzujM+bwtaNTg1c46plgDoD2gIioVo6aq4uFzm00dqmhp9atTj1AC8X0SlGk xAA/XvH4j9oPf73SBNXgG5hhptr0XINkFbIVhcVc+l7n/oXusx1WZfC0YUO6tbxtQMMD 7a995HpYU64vn3KayVg5WqhgmyaN16wv8H3vp4dRzSauPC09Qgz8A/xGxzg+TuTqwUvO 0EkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GqaBeqpxGU9fIUnLtnQETNecBeX8dexoh6583DDk5vg=; b=MjkLgq21fLLAnrP4SNvMNcKXg2ltmFAhpOJ/73HukTsOCnNB7VdNluejE1tFJj9e4G AIy8XyEv6N08D4dQ97vpiPEAiKK9C34YwXQHUHqTlkR7qRAoPxYu8GnZxsghWaPvuynh cDvm6FHtTnDl30Ph1us3eyM2wRyE7P4jV++6ZJNrXx5EhhLG0ZFrObeLNglEtUzZ9CCE bYgPXtL9Be/LBs7wMK4mVEVb1k6JsKWg8MnumvEShz1AFvI6pngow2XDpQxmNaoODhfT xAE3YkTHEmv3DrbB5Sq5CbtIVf3hE+Lj4r9bydVlba2O/NhqyQ4DtuXO6GOV6C7FJ8U9 C8CQ==
X-Gm-Message-State: AGRZ1gKBbQKQ4q9eo2whhlUMAg2IvVI/PZ2iFMjVPJESVmzBZr2taReA cm1yMhyXtGBbSJYDv0IBLf3udcGdLRDwqW6Inw0=
X-Google-Smtp-Source: AJdET5cSYg9Ui4kVShswQ62iX3LxECmzehNbR3uJ+Lus0Y9hjvw/ISUER/CCqa4Yj027z0yOQ5uTB//TsO3J1zCCAS8=
X-Received: by 2002:a02:85c9:: with SMTP id d67-v6mr19820738jai.137.1541383792904; Sun, 04 Nov 2018 18:09:52 -0800 (PST)
MIME-Version: 1.0
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> <C01B0098369B2D4391851938DA6700B7D74DE6@DGGEMI524-MBS.china.huawei.com>
In-Reply-To: <C01B0098369B2D4391851938DA6700B7D74DE6@DGGEMI524-MBS.china.huawei.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Mon, 05 Nov 2018 13:09:41 +1100
Message-ID: <CAL9jLaY8XWuzwuj1=RaZEQZKe18uXrLrSxt=AQ8KfVJPCh_-yg@mail.gmail.com>
To: guyunan@huawei.com
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "<grow-chairs@ietf.org>" <grow-chairs@ietf.org>, grow-ads@tools.ietf.org
Content-Type: multipart/alternative; boundary="0000000000007052910579e1613b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/NWBQ5wyZrc9uKPZjoy1yLbXiLQ4>
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: Mon, 05 Nov 2018 02:09:56 -0000
Yunan, was this set of slides what you wanted to present for today? Did you have alternate slides? On Mon, Nov 5, 2018 at 1:11 AM Guyunan (Yunan Gu, IP Technology Research Dept. NW) <guyunan@huawei.com> wrote: > 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 > <christopher.morrow@gmail.com>] > *Sent:* 2018年10月24日 9:46 > *To:* Guyunan (Yunan Gu, IP Technology Research Dept. NW) < > guyunan@huawei.com> > *Cc:* grow@ietf.org grow@ietf.org <grow@ietf.org>; <grow-chairs@ietf.org> > <grow-chairs@ietf.org>; 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> 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] *On Behalf Of *Christopher > Morrow > *Sent:* 2018年10月24日 4:41 > *To:* grow@ietf.org grow@ietf.org <grow@ietf.org>; <grow-chairs@ietf.org> > <grow-chairs@ietf.org>; 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> 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