[GROW] RFC 7908 on Problem Definition and Classification of BGP Route Leaks
rfc-editor@rfc-editor.org Tue, 21 June 2016 23:59 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 AB56012D85C; Tue, 21 Jun 2016 16:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 aHRxX2JevR8X; Tue, 21 Jun 2016 16:58:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18EE812DEC4; Tue, 21 Jun 2016 16:58:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 129E0B80D34; Tue, 21 Jun 2016 16:58:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160621235836.129E0B80D34@rfc-editor.org>
Date: Tue, 21 Jun 2016 16:58:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/WV1DOfrd0srVnswijoNNLStz3nw>
Cc: grow@ietf.org, rfc-editor@rfc-editor.org
Subject: [GROW] RFC 7908 on Problem Definition and Classification of BGP Route Leaks
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Jun 2016 23:59:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7908
Title: Problem Definition and Classification of
BGP Route Leaks
Author: K. Sriram, D. Montgomery,
D. McPherson, E. Osterweil,
B. Dickson
Status: Informational
Stream: IETF
Date: June 2016
Mailbox: ksriram@nist.gov,
dougm@nist.gov,
dmcpherson@verisign.com,
eosterweil@verisign.com,
brian.peter.dickson@gmail.com
Pages: 11
Characters: 25417
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-grow-route-leak-problem-definition-06.txt
URL: https://www.rfc-editor.org/info/rfc7908
DOI: http://dx.doi.org/10.17487/RFC7908
A systemic vulnerability of the Border Gateway Protocol routing
system, known as "route leaks", has received significant attention in
recent years. Frequent incidents that result in significant
disruptions to Internet routing are labeled route leaks, but to date
a common definition of the term has been lacking. This document
provides a working definition of route leaks while keeping in mind
the real occurrences that have received significant attention.
Further, this document attempts to enumerate (though not
exhaustively) different types of route leaks based on observed events
on the Internet. The aim is to provide a taxonomy that covers
several forms of route leaks that have been observed and are of
concern to the Internet user community as well as the network
operator community.
This document is a product of the Global Routing Operations Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC