BGP ACCEPT_OWN Community Attribute
draft-ietf-l3vpn-acceptown-community-08
Network Working Group J. Uttaro
Internet-Draft ATT
Intended status: Standards Track P. Mohapatra
Expires: November 29, 2014 Sproute Networks
D. Smith
Cisco Systems
R. Raszuk
J. Scudder
Juniper Networks
May 28, 2014
BGP ACCEPT_OWN Community Attribute
draft-ietf-l3vpn-acceptown-community-08.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 November 29, 2014.
Uttaro, et al. Expires November 29, 2014 [Page 1]
Internet-Draft accept-own May 2014
Copyright Notice
Copyright (c) 2014 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. ACCEPT_OWN Community . . . . . . . . . . . . . . . . . . . . 3
2.1. Route Acceptance . . . . . . . . . . . . . . . . . . . . 4
2.2. Propagating ACCEPT_OWN Between Address Families . . . . . 4
2.3. Configuration Control . . . . . . . . . . . . . . . . . . 4
3. Decision Process . . . . . . . . . . . . . . . . . . . . . . 5
4. Deployment Considerations . . . . . . . . . . . . . . . . . . 5
5. Other Applications . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
9. Normative References . . . . . . . . . . . . . . . . . . . . 6
Appendix A. Local Extranet Application (non-informative) . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
Show full document text