[Docs] [txt|pdf|xml] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-mauch-bgp-reject) 00 01 02 03 04 05 06 07 08 RFC 8212

Global Routing Operations                                       J. Mauch
Internet-Draft                                               J. Snijders
Intended status: Standards Track                                     NTT
Expires: June 30, 2016                                 December 28, 2015


 By default reject propagation when no policy is associated with a BGP
                            peering session.
                     draft-ietf-grow-bgp-reject-00

Abstract

   This document defines the default behaviour of a BGP speaker when no
   explicit policy is associated with a BGP peering session.

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 June 30, 2016.

Copyright Notice

   Copyright (c) 2015 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.





Mauch & Snijders          Expires June 30, 2016                 [Page 1]


Internet-Draft             BGP-DEFAULT-REJECT              December 2015


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  Solution Requirements . . . . . . . . . . . . . . . . . . . .   2
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   BGP [RFC4271] speakers have many default settings which need to be
   revisited as part of improving the routing ecosystem.  There is a
   need to provide guidace to BGP implementors for the default behaviors
   of a well functioning internet ecosystem.  Routing leaks
   [I-D.ietf-idr-route-leak-detection-mitigation] are part of the
   problem, but software defects and operator misconfigurations are just
   a few of the attacks on internet stability we aim to address.

   Usually BGP speakers accept all routes from a configured peer or
   neighbor.  This practice dates back to the early days of internet
   protocols in being very permissive in offering routing information to
   allow all networks to reach each other.  With the core of the
   internet becoming more densely interconnected the risk of a
   misbehaving edge device or BGP speaking customer poses signficiant
   risks to the reachability of critical services.

   This proposal intends to solve this situation with the requiring the
   explicity configuration of BGP policy for any non-iBGP speaking
   session such as customers, peers or confederation boundaries.  When
   this solution is implemented, devices will no longer pass routes
   without explicit policy.

2.  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].

3.  Solution Requirements

   The following requirements apply to the solution described in this
   document:




Mauch & Snijders          Expires June 30, 2016                 [Page 2]


Internet-Draft             BGP-DEFAULT-REJECT              December 2015


   o  Software MUST mark any routes from an eBGP peer as 'invalid' in
      the Adj-RIB-In, if no explicit policy was configured.

   o  Software MUST NOT advertise any routes to an eBGP peer without an
      operator configuring a policy

   o  Software MUST NOT require a configuration directive to operate in
      this mode.

   o  Software MUST provide protection from internal failures preventing
      the advertisement and acceptance of routes

   o  Software MAY provide a configuration option to disable this
      security capability.

4.  Acknowledgements

   The authors would like to thank the following people for their
   comments and support: Shane Amante, Christopher Morrow, Robert
   Raszuk.

5.  Security Considerations

   This document addresses the basic security posture of a BGP speaking
   device within a network.  Operators have a need for implementors to
   address the problem through a behavior change to mitigate against
   possible attacks from a permissive security posture.  Attacks and
   inadvertent advertisements cause business impact necessitating this
   default behavior.

6.  IANA Considerations

   This document has no actions for IANA.

7.  References

7.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC4271]  Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
              Border Gateway Protocol 4 (BGP-4)", RFC 4271,
              DOI 10.17487/RFC4271, January 2006,
              <http://www.rfc-editor.org/info/rfc4271>.




Mauch & Snijders          Expires June 30, 2016                 [Page 3]


Internet-Draft             BGP-DEFAULT-REJECT              December 2015


7.2.  Informative References

   [I-D.ietf-idr-route-leak-detection-mitigation]
              Sriram, K., Montgomery, D., Dickson, B., Patel, K., and A.
              Robachevsky, "Methods for Detection and Mitigation of BGP
              Route Leaks", draft-ietf-idr-route-leak-detection-
              mitigation-01 (work in progress), October 2015.

Authors' Addresses

   Jared Mauch
   NTT Communications, Inc.
   8285 Reese Lane
   Ann Arbor  Michigan 48103
   US

   Email: jmauch@us.ntt.net


   Job Snijders
   NTT Communications, Inc.
   Amsterdam
   NL

   Email: job@ntt.net


























Mauch & Snijders          Expires June 30, 2016                 [Page 4]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/