Covering Prefixes Outbound Route Filter for BGP-4
draft-ietf-bess-orf-covering-prefixes-00

The information below is for an old version of the document
Document Type Active Internet-Draft (bess WG)
Last updated 2014-12-08 (latest revision 2014-11-10)
Replaces draft-ietf-l3vpn-orf-covering-prefixes
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd Martin Vigoureux
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Martin Vigoureux" <martin.vigoureux@alcatel-lucent.com>
BESS Routing Working Group                                       H. Jeng
Internet-Draft                                                      AT&T
Intended status: Standards Track                                L. Jalil
Expires: May 14, 2015                                            Verizon
                                                               R. Bonica
                                                              Y. Rekhter
                                                        Juniper Networks
                                                                K. Patel
                                                           Cisco Systems
                                                                 L. Yong
                                                                   X. Xu
                                                     Huawei Technologies
                                                       November 10, 2014

           Covering Prefixes Outbound Route Filter for BGP-4
                draft-ietf-bess-orf-covering-prefixes-00

Abstract

   This document defines a new ORF-type, called the "Covering Prefixes
   ORF (CP-ORF)".  CP-ORF is applicable in Virtual Hub-and-Spoke VPNs.
   It also is applicable in BGP/MPLS Ethernet VPN (EVPN) Networks.

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].

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 May 14, 2015.

Jeng, et al.              Expires May 14, 2015                  [Page 1]
Internet-Draft            Covering Prefixes ORF            November 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.

Table of Contents

   1.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  CP-ORF Encoding . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Processing Rules  . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Applicability In Virtual Hub-and-Spoke VPNs . . . . . . . . .   9
     4.1.  Multicast Considerations  . . . . . . . . . . . . . . . .  12
   5.  Applicability In BGP/MPLS Ethernet VPN (EVPN) . . . . . . . .  12
   6.  Clean-up  . . . . . . . . . . . . . . . . . . . . . . . . . .  16
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  17
   10. Normative References  . . . . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Problem Statement

   A BGP [RFC4271] speaker can send Outbound Route Filters (ORF)
   [RFC5291] to a peer.  The peer uses ORFs to filter routing updates
   that it sends to the BGP speaker.  Using ORF, a BGP speaker can
   realize a "route pull" paradigm, in which the BGP speaker, on demand,
   pulls certain routes from the peer.

   This document defines a new ORF-type, called the "Covering Prefixes
   ORF (CP-ORF)".  CP-ORF is applicable in Virtual Hub-and-Spoke VPNs
   [RFC7024] [RFC4364].  It also is applicable BGP/MPLS Ethernet VPN
   (EVPN) [I-D.ietf-l2vpn-evpn] Networks.

Jeng, et al.              Expires May 14, 2015                  [Page 2]
Internet-Draft            Covering Prefixes ORF            November 2014

1.1.  Terminology

   This document uses the following terms:

   o  Address Family Indicator (AFI) - defined in [RFC4760]
Show full document text