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

The information below is for an old version of the document
Document Type Active Internet-Draft (l3vpn WG)
Last updated 2012-07-30
Replaces draft-pmohapat-l3vpn-acceptown-community
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document Nov 2013 Nov 2014
Other - see Comment Log
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          J. Uttaro
Internet-Draft                                                      AT&T
Intended status: Standards Track                            P. Mohapatra
Expires: February 1, 2013                                       D. Smith
                                                           Cisco Systems
                                                               R. Raszuk
                                                            NTT MCL Inc.
                                                              J. Scudder
                                                        Juniper Networks
                                                           July 31, 2012

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

Abstract

   Under certain conditions it is desirable for a BGP route reflector to
   be able to modify the Route Target list of a VPN route that is
   distributed by the route reflector, enabling the route reflector to
   control how a route originated within one VRF is imported into other
   VRFs.  This technique works effectively as long as the VRF that
   exports the route is not on the same PE as 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, allowing the technique 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 February 1, 2013.

Copyright Notice

Uttaro, et al.          Expires February 1, 2013                [Page 1]
Internet-Draft            accept-own community                 July 2012

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Uttaro, et al.          Expires February 1, 2013                [Page 2]
Internet-Draft            accept-own community                 July 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 4
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . . . 4
   2.  ACCEPT_OWN Community  . . . . . . . . . . . . . . . . . . . . . 4
     2.1.  Route Acceptance  . . . . . . . . . . . . . . . . . . . . . 5
     2.2.  Propagating ACCEPT_OWN Between Address Families . . . . . . 5
     2.3.  Configuration Control . . . . . . . . . . . . . . . . . . . 5
   3.  Decision Process  . . . . . . . . . . . . . . . . . . . . . . . 6
   4.  Deployment Considerations . . . . . . . . . . . . . . . . . . . 6
   5.  Other Applications  . . . . . . . . . . . . . . . . . . . . . . 6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
Show full document text