Simple Virtual Aggregation (S-VA)
draft-ietf-grow-simple-va-10

The information below is for an old version of the document
Document Type Active Internet-Draft (grow WG)
Last updated 2012-07-05
Stream IETF
Intended RFC status Informational
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Unknown
Telechat date
Needs a YES.
Responsible AD Ron Bonica
IESG note Peter Schoenmaker <pds@lugs.com> is the document shepherd.
Send notices to grow-chairs@tools.ietf.org, draft-ietf-grow-simple-va@tools.ietf.org
GROW Working Group                                             R. Raszuk
Internet-Draft                                                   NTT MCL
Intended status: Informational                                  J. Heitz
Expires: January 6, 2013                                        Ericsson
                                                                   A. Lo
                                                                  Arista
                                                                L. Zhang
                                                                    UCLA
                                                                   X. Xu
                                                                  Huawei
                                                            July 5, 2012

                   Simple Virtual Aggregation (S-VA)
                    draft-ietf-grow-simple-va-10.txt

Abstract

   All BGP routers in the Default Free Zone (DFZ) are required to carry
   all the routes in the Default Free Routing Table (DFRT).  A technique
   is described that allows some BGP routers not to install all of those
   routes into the Forwarding Information Base (FIB).

   Some routers in an Autonomous System (AS) announce an aggregate (the
   VA prefix) in addition to the routes they already announce.  This
   enables other routers not to install the routes covered by the VA
   prefix into the FIB as long as those routes have the same next-hop as
   the VA prefix.

   The VA prefixes that are announced within an AS are not announced to
   any other AS.

Status of this Memo

   This Internet-Draft is submitted to IETF 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 January 6, 2013.

Raszuk, et al.           Expires January 6, 2013                [Page 1]
Internet-Draft                    S-VA                         July 2012

Copyright Notice

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Scope of this Document  . . . . . . . . . . . . . . . . . . 3
     1.2.  Requirements notation . . . . . . . . . . . . . . . . . . . 3
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Operation of S-VA . . . . . . . . . . . . . . . . . . . . . . . 4
   3.  Deployment considerations . . . . . . . . . . . . . . . . . . . 6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 7

Raszuk, et al.           Expires January 6, 2013                [Page 2]
Internet-Draft                    S-VA                         July 2012

1.  Introduction

   A technique called Simple Virtual Aggregation (S-VA) is described.
   It allows some routers not to have to store some routes in the
   Forwarding Information Base (FIB) while still advertising and
   receiving the full Default Free Routing Table (DFRT) in BGP.

   A typical scenario is as follows.  Core routers in the ISP maintain
   the full DFRT in the FIB and RIB.  Edge routers maintain the full
   DFRT in the BGP Loc-RIB, but do not install certain routes in the RIB
   and FIB.  Edge routers may install a default route to core routers,
   to Area Border Routers (ABR) which are installed on the Point of
   Presence (POP), to core boundary routers or to Autonomous System
Show full document text