[GROW] FW: New Version Notification for draft-gu-grow-bmp-route-leak-detection-01.txt

"Guyunan (Yunan Gu, IP Technology Research Dept. NW)" <guyunan@huawei.com> Tue, 12 March 2019 02:01 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 33BC412D829 for <grow@ietfa.amsl.com>; Mon, 11 Mar 2019 19:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 iLN7DakaAren for <grow@ietfa.amsl.com>; Mon, 11 Mar 2019 19:01:07 -0700 (PDT)
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 3539012D84D for <grow@ietf.org>; Mon, 11 Mar 2019 19:01:07 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 6C82EB7234431F657309 for <grow@ietf.org>; Tue, 12 Mar 2019 02:01:05 +0000 (GMT)
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 12 Mar 2019 02:01:05 +0000
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Tue, 12 Mar 2019 02:01:04 +0000
Received: from DGGEML403-HUB.china.huawei.com (10.3.17.33) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Tue, 12 Mar 2019 02:01:04 +0000
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.207]) by DGGEML403-HUB.china.huawei.com ([fe80::74d9:c659:fbec:21fa%31]) with mapi id 14.03.0415.000; Tue, 12 Mar 2019 10:00:52 +0800
From: "Guyunan (Yunan Gu, IP Technology Research Dept. NW)" <guyunan@huawei.com>
To: "grow@ietf.org" <grow@ietf.org>
CC: Zhuangshunwan <zhuangshunwan@huawei.com>, Huanan Chen <chenhn8.gd@chinatelecom.cn>
Thread-Topic: New Version Notification for draft-gu-grow-bmp-route-leak-detection-01.txt
Thread-Index: AQHU2ArD/poRnXcI8EeiG5RAmKKreqYHO/QQ
Date: Tue, 12 Mar 2019 02:00:52 +0000
Message-ID: <C01B0098369B2D4391851938DA6700B71348B2CB@DGGEML532-MBX.china.huawei.com>
References: <155230937426.16927.11495749014917283373.idtracker@ietfa.amsl.com>
In-Reply-To: <155230937426.16927.11495749014917283373.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.184.132]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/6Aj_FFEbYmmtLA66LZ-kxM-P6ho>
Subject: [GROW] FW: New Version Notification for draft-gu-grow-bmp-route-leak-detection-01.txt
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: Tue, 12 Mar 2019 02:01:10 -0000

Hi all,

We just updated the draft-gu-grow-bmp-route-leak-detection-00 with the BMP extension definition. For a quick recap, this document describes a route leak detection method that a single AS or ISP can deploy without relying on other ISP/AS or other data sources. It does not have the business relationship disclosure concern. It does not require any routing protocol extension.

Comments are very welcome!


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, March 11, 2019 9:03 PM
To: Zhuangshunwan <zhuangshunwan@huawei.com>; China Telecom <chenhn8.gd@chinatelecom.cn>; Guyunan (Yunan Gu, IP Technology Research Dept. NW) <guyunan@huawei.com>; Huanan Chen <chenhn8.gd@chinatelecom.cn>
Subject: New Version Notification for draft-gu-grow-bmp-route-leak-detection-01.txt


A new version of I-D, draft-gu-grow-bmp-route-leak-detection-01.txt
has been successfully submitted by Yunan Gu and posted to the IETF repository.

Name:		draft-gu-grow-bmp-route-leak-detection
Revision:	01
Title:		BMP for BGP Route Leak Detection
Document date:	2019-03-11
Group:		Individual Submission
Pages:		8
URL:            https://www.ietf.org/internet-drafts/draft-gu-grow-bmp-route-leak-detection-01.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-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-gu-grow-bmp-route-leak-detection
Diff:           https://www.ietf.org/rfcdiff?url2=draft-gu-grow-bmp-route-leak-detection-01

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.


                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat