Global Routing Operations J. Mauch
Internet-Draft J. Snijders
Intended status: Standards Track NTT
Expires: November 11, 2016 May 10, 2016

By default reject propagation when no policy is associated with a BGP peering session.


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

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 November 11, 2016.

Copyright Notice

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

Table of Contents

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 guidance 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 by requiring the explicit 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:

4. Acknowledgements

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

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.
[RFC4271] Rekhter, Y., Li, T. and S. Hares, "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006.

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", Internet-Draft draft-ietf-idr-route-leak-detection-mitigation-02, March 2016.

Authors' Addresses

Jared Mauch NTT Communications, Inc. 8285 Reese Lane Ann Arbor, Michigan 48103 US EMail:
Job Snijders NTT Communications, Inc. Theodorus Majofskistraat 100 Amsterdam, 1065 SZ NL EMail: