Skip to main content

Route Leaks -- Requirements for Detection and Prevention thereof
draft-dickson-sidr-route-leak-reqts-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Author Brian Dickson
Last updated 2012-03-05
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-dickson-sidr-route-leak-reqts-00
sidr                                                          B. Dickson
Internet-Draft                                             Brian Dickson
Expires: September 6, 2012                                 March 5, 2012

    Route Leaks -- Requirements for Detection and Prevention thereof
                 draft-dickson-sidr-route-leak-reqts-00

Abstract

   The Border Gateway Protocol, version 4, (BGP4) provides the means to
   advertise reachability for IP prefixes.  This reachability
   information is propagated in a peer-to-peer topology.  Sometimes
   routes are announced to peers for which the local peering policy does
   not permit.  And sometimes routes are propagated indiscriminantly,
   once they have been accepted.

   This document considers the situations that can lead to routes being
   leaked, and tries to find acceptable definitions for describing these
   scenarios.

   The purpose of these definitions is to facilitate discussion on what
   a route leak is, and what the scope of the problem space for route
   leaks is.  This, in turn, is intended to inform a requirements
   document for detection of (and prevention of) route leaks.  And
   finally, the definitions and requirements are intended to allow
   proposed solutions which meet these criteria, and to facilitate
   evaluation of proposed solutions.

   The fundamental objective is to "solve the route leaks problem".

Author's Note

   Intended Status: Informational.

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

Dickson                 Expires September 6, 2012               [Page 1]
Internet-Draft      Route Leak Detection Requirements         March 2012

   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 6, 2012.

Copyright Notice

   Copyright (c) 2012 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Dickson                 Expires September 6, 2012               [Page 2]
Internet-Draft      Route Leak Detection Requirements         March 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 4
     1.1.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . 4
     1.2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . 4
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
   2.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 4
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     5.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
     5.2.  Informative References  . . . . . . . . . . . . . . . . . . 5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 5

Dickson                 Expires September 6, 2012               [Page 3]
Internet-Draft      Route Leak Detection Requirements         March 2012

1.  Introduction

1.1.  Rationale

   This document is a placeholder, version 00 to meet the cut-off
   deadline.

1.2.  Requirements

   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 [RFC2119].

1.3.  Terminology

   The reader is assumed to be familiar with the IETF.

2.  Security Considerations

   None per se.

3.  IANA Considerations

   This document contains no IANA-specific material.

4.  Acknowledgements

   To be added later.

5.  References

5.1.  Normative References

   [RFC1033]  Lottor, M., "Domain administrators operations guide",
              RFC 1033, November 1987.

   [RFC1034]  Mockapetris, P., "Domain names - concepts and facilities",
              STD 13, RFC 1034, November 1987.

   [RFC1035]  Mockapetris, P., "Domain names - implementation and
              specification", STD 13, RFC 1035, November 1987.

   [RFC2136]  Vixie, P., Thomson, S., Rekhter, Y., and J. Bound,
              "Dynamic Updates in the Domain Name System (DNS UPDATE)",

Dickson                 Expires September 6, 2012               [Page 4]
Internet-Draft      Route Leak Detection Requirements         March 2012

              RFC 2136, April 1997.

   [RFC2181]  Elz, R. and R. Bush, "Clarifications to the DNS
              Specification", RFC 2181, July 1997.

   [RFC2308]  Andrews, M., "Negative Caching of DNS Queries (DNS
              NCACHE)", RFC 2308, March 1998.

   [RFC4033]  Arends, R., Austein, R., Larson, M., Massey, D., and S.
              Rose, "DNS Security Introduction and Requirements",
              RFC 4033, March 2005.

   [RFC4034]  Arends, R., Austein, R., Larson, M., Massey, D., and S.
              Rose, "Resource Records for the DNS Security Extensions",
              RFC 4034, March 2005.

   [RFC5011]  StJohns, M., "Automated Updates of DNS Security (DNSSEC)
              Trust Anchors", RFC 5011, September 2007.

   [RFC5155]  Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS
              Security (DNSSEC) Hashed Authenticated Denial of
              Existence", RFC 5155, March 2008.

5.2.  Informative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

Author's Address

   Brian Dickson
   Brian Dickson
   703 Palmer Drive,
   Herndon, VA  20170
   USA

   Email: brian.peter.dickson@gmail.com

Dickson                 Expires September 6, 2012               [Page 5]