logo
    One-time Address-Prefix Based Outbound Route Filter for BGP-4
    0
    Citation
    0
    Reference
    20
    Related Paper
    This document describes the changes necessary for BGP-4 to route traffic from a specified prefix to a specified prefix.
    Border Gateway Protocol
    Default-free zone
    Citations (0)
    This document defines two new Outbound Router Filter types for BGP, termed Extended Community Outbound Route Filter Type I, and Extended Community Outbound Route Filter Type II, that can be used to perform extended community based route filtering.
    Border Gateway Protocol
    Citations (0)
    The results of analyzing BGP routing tables show that there are a large number of routes of which the mask length of prefix exceeds the maximum mask length as specified by the address allocation policies. Based on the mask length of prefix, a method is presented to slow the growth of BGP routing table down so as to filter routes. For the prefixes of which the mask lengths are longer than those specified by the address allocation policies,they are only allowed to be announced in a certain range of distance. Once the route is traversing the range of given number of autonomous systems, it will be filtered out without announcement. In order to implement the filtering mechanism, the BGP is modified to add a new route attribute in it so as to record the maximum announced distance of the filtered route, thus implementing the route filtration. The method is proved feasible through simulation using actual BGP routing tables and efficient for restraining the growth of BGP routing tables.
    Border Gateway Protocol
    Default-free zone
    Prefix
    Citations (0)
    This document defines a BGP-based mechanism that allows a BGP speaker to send to its BGP peer a set of Outbound Route Filters (ORFs) that the peer would use to constrain/filter its outbound routing updates to the speaker. [STANDARDS-TRACK]
    Border Gateway Protocol
    Citations (9)
    This document defines a new Outbound Router Filter type for BGP, termed Aspath Outbound Route Filter, that can be used to perform aspath based route filtering. This ORF-type supports aspath based route filtering as well as regular expression based matching, for address groups.
    Border Gateway Protocol
    Citations (2)
    This document updates RFC4271 by adding a control mechanism which limits the negative impact of outbound route leaks (RFC7908) in order to prevent resource exhaustion in Border Gateway Protocol (BGP) implementations.
    Prefix
    Citations (0)
    Although most studies of Internet routing treat each IP address block (or prefix) independently, the relationship between prefixes is important because routers ultimately forward packets based on the "longest-matching prefix." In fact, the most-specific prefix for a given destination address may change over time, as BGP routes are announced and withdrawn. Even if the most-specific route is withdrawn, routers may still be able to deliver packets to the destination using a less-specific route. In this paper, we analyze BGP update messages and Netflow traffic traces from a large ISP to characterize both the changes to the longest-matching prefix over time and the resulting effects on end-to-end reachability of the destination hosts. To drive our analysis, we design and implement an efficient online algorithm for tracking changes in the longest-matching prefix for each IP address. We analyze the BGP message traces to identify the reasons for prefix-match changes, including failures, route flapping, sub-prefix hijacking, and load-balancing policies. Our preliminary analysis of the Netflow data suggests that the relationship between BGP updates and IP reachability is sometimes counterintuitive.
    Prefix
    IP forwarding
    Border Gateway Protocol
    Citations (7)
    To help reduce well-known threats against BGP including prefix misannouncing and monkey-in-the-middle attacks, one of the security requirements is the ability to validate the origination Autonomous System (AS) of BGP routes.More specifically, one needs to validate that the AS number claiming to originate an address prefix (as derived from the AS_PATH attribute of the BGP route) is in fact authorized by the prefix holder to do so.This document describes a simple validation mechanism to partially satisfy this requirement.
    Prefix
    Citations (60)