datatracker.ietf.org
Sign in
Version 5.12.0.p2, 2015-03-02
Report a bug

Filtering of Overlapping Routes
draft-white-grow-overlapping-routes-03

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-10-20
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                           R. White
Internet-Draft                                                  Ericsson
Intended status: Informational                                 A. Retana
Expires: April 23, 2015                              Cisco Systems, Inc.
                                                                S. Hares
                                                                  Huawei
                                                        October 20, 2014

                    Filtering of Overlapping Routes
                 draft-white-grow-overlapping-routes-03

Abstract

   This document proposes an optional mechanism to remove a prefix when
   it overlaps with a functionally equivalent shorter prefix.  The
   proposed mechanism does not require any changes to the BGP protocol.

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 http://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 23, 2015.

Copyright Notice

   Copyright (c) 2014 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
   (http://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

White, et al.            Expires April 23, 2015                 [Page 1]
Internet-Draft         Overlapping Route Filtering          October 2014

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Overlapping Route Filtering Mechanism . . . . . . . . . . . .   3
     3.1.  Marking Overlapping Routes  . . . . . . . . . . . . . . .   4
     3.2.  Preferring Marked Routes  . . . . . . . . . . . . . . . .   4
       3.2.1.  Using a Cost Community  . . . . . . . . . . . . . . .   4
       3.2.2.  Using the Local Preference  . . . . . . . . . . . . .   4
     3.3.  Handling Marked Routes Within the AS  . . . . . . . . . .   5
     3.4.  Handling Marked Routes at the Outbound Edge . . . . . . .   5
   4.  Examples of Filtering Overlapping Routes  . . . . . . . . . .   5
     4.1.  IPv4 Example  . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  IPv6 Example  . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Operational Considerations  . . . . . . . . . . . . . . . . .   6
     5.1.  Advantages to the Service Provider  . . . . . . . . . . .   7
     5.2.  Implications for Router processing  . . . . . . . . . . .   7
     5.3.  Implications for Convergence Time . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   8
     A.1.  Changes between the -00 and -01 versions. . . . . . . . .   8
     A.2.  Changes between the -01 and -02 versions  . . . . . . . .   9
     A.3.  Changes between the -02 and -03 versions  . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   One cause of the growth of the global Internet's default free zone
   table size is overlapping routes injected into the routing system to
   steer traffic among various entry points into a network.  Because
   padding AS Path lengths can only steer inbound traffic in a very
   small set of cases, and other mechanisms used to steer traffic to a
   particular inbound point are ineffective when multiple upstream

[include full document text]