BMP for BGP Route Leak Detection
draft-gu-grow-bmp-route-leak-detection-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-10-22
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group Y. Gu
Internet-Draft S. Zhuang
Intended status: Standards Track Huawei
Expires: April 25, 2019 October 22, 2018
BMP for BGP Route Leak Detection
draft-gu-grow-bmp-route-leak-detection-00
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.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 25, 2019.
Gu & Zhuang Expires April 25, 2019 [Page 1]
Internet-Draft Route Leak Detection October 2018
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. ISP Route Leak Prevention Methods . . . . . . . . . . . . 3
2.2. Challenge of the Current Route Leak Prevention Methods . 4
3. Existing RLD Methods Discussion . . . . . . . . . . . . . . . 4
4. BMP Extension for RLD . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Terminology
BMP: BGP Monitoring Protocol
BMS: BGP Monitoring Station
C2P: Customer to Provider
ISP: Internet Service Provider
P2P: Peer to Peer
RIB: Routing Information Base
RLD: Route Leak Detection
Gu & Zhuang Expires April 25, 2019 [Page 2]
Internet-Draft Route Leak Detection October 2018
2. Introduction
RFC 7908 defines "Route Leak" as: A route leak is the propagation of
routing announcement(s) beyond their intended scope, which can result
in possible situations such as eavesdropping, device overload, route
black hole and so on. More specifically, the intended scope of route
announcements is usually defined by local route filtering/
distribution policies within devices. These policies are designed to
realise the pair-wise peering business relationships between ASes
(autonomous systems), which include Customer to Provider (C2P), Peer
to Peer (Peer to Peer), and Provider to Customer (P2C). In a C2P
relationship, the customer pays the provider for traffic sent between
the two ASes. In return, the customer gains access to the ASes the
provider can reach, including those which the provider reaches
Show full document text