BGP ACCEPT_OWN Community Attribute
draft-ietf-l3vpn-acceptown-community-10

 
Document Type Active Internet-Draft (bess WG)
Last updated 2015-06-29 (latest revision 2015-06-24)
Replaces draft-pmohapat-l3vpn-acceptown-community
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication Nov 2013 Nov 2014
Consensus Yes
Document shepherd Thomas Morin
Shepherd write-up Show (last changed 2014-11-23)
IESG IESG state RFC Ed Queue
Telechat date
Responsible AD Alvaro Retana
Send notices to draft-ietf-l3vpn-acceptown-community@ietf.org, bess-chairs@ietf.org, thomas.morin@orange.com, bess@ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
Network Working Group                                          J. Uttaro
Internet-Draft                                                       ATT
Intended status: Standards Track                            P. Mohapatra
Expires: December 26, 2015                              Sproute Networks
                                                                D. Smith
                                                           Cisco Systems
                                                               R. Raszuk
                                                           Mirantis Inc.
                                                              J. Scudder
                                                        Juniper Networks
                                                           June 24, 2015

                   BGP ACCEPT_OWN Community Attribute
              draft-ietf-l3vpn-acceptown-community-10.txt

Abstract

   Under certain conditions it is desirable for a Border Gateway
   Protocol (BGP) route reflector to be able to modify the Route Target
   (RT) list of a Virtual Private Network (VPN) route that the route
   reflector distributes, enabling the route reflector to control how a
   route originated within one Virtual Routing and Forwarding (VRF) is
   imported into other VRFs.  This technique works effectively as long
   as the VRF that exports the route is not on the same Provider Edge
   (PE) router than the VRF(s) that import the route.  However, due to
   the constraints of the BGP protocol, it does not work if the two are
   on the same PE.  This document describes a modification to the BGP
   protocol allowing this technique to work when the VRFs are on the
   same PE, and to be used in a standard manner throughout an autonomous
   system.

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 December 26, 2015.

Uttaro, et al.          Expires December 26, 2015               [Page 1]
Internet-Draft                 accept-own                      June 2015

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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  ACCEPT_OWN Community  . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Route Acceptance  . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Propagating ACCEPT_OWN Between Address Families . . . . .   4
     2.3.  Configuration Control . . . . . . . . . . . . . . . . . .   4
   3.  Decision Process  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Deployment Considerations . . . . . . . . . . . . . . . . . .   5
   5.  Other Applications  . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Local Extranet Application (non-normative) . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   In certain scenarios, a BGP speaker may maintain multiple VRFs
   [RFC4364].  Under certain conditions, it is desirable for a route
   reflector to be able to modify the RT list of a VPN route that the
   route reflector distributes, enabling the route reflector to control
   how a route originated within one VRF is imported into other VRFs.
Show full document text