Browse Prior Art Database

Default External BGP (EBGP) Route Propagation Behavior without Policies (RFC8212)

IP.com Disclosure Number: IPCOM000250368D
Original Publication Date: 2017-Jul-01
Included in the Prior Art Database: 2017-Jul-06
Document File: 14 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Mauch: AUTHOR [+3]

Abstract

BGP routing security issues need to be addressed in order to make the Internet more stable. Route leaks [RFC7908] are part of the problem, but software defects or operator misconfiguration can also contribute. This document updates [RFC4271] so that routes are neither imported nor exported unless specifically enabled by configuration. This change reduces the consequences of these problems and improves the default level of Internet routing security.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 21% of the total text.

Internet Engineering Task Force (IETF)                          J. Mauch Request for Comments: 8212                                        Akamai Updates: 4271                                                J. Snijders Category: Standards Track                                            NTT ISSN: 2070-1721                                               G. Hankins                                                                    Nokia                                                                July 2017

 Default External BGP (EBGP) Route Propagation Behavior without Policies

Abstract

   This document updates RFC 4271 by defining the default behavior of a    BGP speaker when there is no Import or Export Policy associated with    an External BGP session.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8212.

Copyright Notice

   Copyright (c) 2017 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, et al.                Standards Track                    [Page 1]
 RFC 8212                   BGP Default Reject                  July 2017

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3

     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3

   3.  Changes to RFC 4271 . . . . . . . . . . . . . . . . . . . . .   3

   4...