draft-ietf-grow-simple-va-00.txt   draft-ietf-grow-simple-va-01.txt 
Network Working Group P. Francis Network Working Group P. Francis
Internet-Draft MPI-SWS Internet-Draft MPI-SWS
Intended status: Informational X. Xu Intended status: Informational X. Xu
Expires: September 2, 2010 Huawei Expires: March 4, 2011 Huawei
H. Ballani H. Ballani
Cornell U. Cornell U.
R. Raszuk R. Raszuk
Cisco Cisco
L. Zhang L. Zhang
UCLA UCLA
March 1, 2010 August 31, 2010
Simple Virtual Aggregation (S-VA) Simple Virtual Aggregation (S-VA)
draft-ietf-grow-simple-va-00.txt draft-ietf-grow-simple-va-01.txt
Abstract Abstract
The continued growth in the Default Free Routing Table (DFRT) The continued growth in the Default Free Routing Table (DFRT)
stresses the global routing system in a number of ways. One of the stresses the global routing system in a number of ways. One of the
most costly stresses is FIB size: ISPs often must upgrade router most costly stresses is FIB size: ISPs often must upgrade router
hardware simply because the FIB has run out of space, and router hardware simply because the FIB has run out of space, and router
vendors must design routers that have adequate FIB. FIB suppression vendors must design routers that have adequate FIB. FIB suppression
is an approach to relieving stress on the FIB by NOT loading selected is an approach to relieving stress on the FIB by NOT loading selected
RIB entries into the FIB. Simple Virtual Aggregation (S-VA) is a RIB entries into the FIB. Simple Virtual Aggregation (S-VA) is a
skipping to change at page 1, line 42 skipping to change at page 1, line 42
to extend the life of edge routers. S-VA can be deployed to extend the life of edge routers. S-VA can be deployed
autonomously by an ISP (cooperation between ISPs is not required), autonomously by an ISP (cooperation between ISPs is not required),
and can co-exist with legacy routers in the ISP. and can co-exist with legacy routers in the ISP.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on March 4, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 2, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Scope of this Document . . . . . . . . . . . . . . . . . . 5 1.1. Scope of this Document . . . . . . . . . . . . . . . . . . 5
1.2. Requirements notation . . . . . . . . . . . . . . . . . . 5 1.2. Requirements notation . . . . . . . . . . . . . . . . . . 5
1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
1.4. Temporary Sections . . . . . . . . . . . . . . . . . . . . 6
1.4.1. Document revisions . . . . . . . . . . . . . . . . . . 6
2. Operation of S-VA . . . . . . . . . . . . . . . . . . . . . . 6 2. Operation of S-VA . . . . . . . . . . . . . . . . . . . . . . 6
2.1. Tunnels . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.1. Tunnels . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2. Legacy Routers . . . . . . . . . . . . . . . . . . . . . . 8 2.2. Legacy Routers . . . . . . . . . . . . . . . . . . . . . . 8
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
6. Normative References . . . . . . . . . . . . . . . . . . . . . 9 6. Normative References . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
ISPs today manage constant DFRT growth in a number of ways. One way, ISPs today manage constant DFRT growth in a number of ways. One way,
of course, is for ISPs to upgrade their router hardware before DFRT of course, is for ISPs to upgrade their router hardware before DFRT
growth outstrips the size of the FIB. This is too expensive for many growth outstrips the size of the FIB. This is too expensive for many
skipping to change at page 6, line 17 skipping to change at page 6, line 17
the FIB. In other words, the phrase "install a route" means the FIB. In other words, the phrase "install a route" means
"install a route into the FIB", and the phrase "suppress a route" "install a route into the FIB", and the phrase "suppress a route"
means "do not install a route into the FIB". means "do not install a route into the FIB".
Legacy Router: A router that does not run S-VA, and has no knowledge Legacy Router: A router that does not run S-VA, and has no knowledge
of S-VA. of S-VA.
Routing Information Base (RIB): The term RIB is used rather sloppily Routing Information Base (RIB): The term RIB is used rather sloppily
in this document to refer either to the loc-RIB (as used in in this document to refer either to the loc-RIB (as used in
[RFC4271]), or to the combined Adj-RIBs-In, the Loc-RIB, and the [RFC4271]), or to the combined Adj-RIBs-In, the Loc-RIB, and the
Adj-RIBs-Out. Adj-RIBs-Out.
1.4. Temporary Sections
This section contains temporary information, and will be removed in
the final version.
1.4.1. Document revisions
Note that S-VA was formerly specified in [I-D.ietf-grow-va]. No new
functionality is specified in this draft.
2. Operation of S-VA 2. Operation of S-VA
There are three types of routers in S-VA, FIB-Installing routers There are three types of routers in S-VA, FIB-Installing routers
(FIR), FIB-Suppressing routers (FSR), and optionally legacy routers. (FIR), FIB-Suppressing routers (FSR), and optionally legacy routers.
While any router can be an FIR or an FSR (there are no topology While any router can be an FIR or an FSR (there are no topology
constraints), the simplist form of deployment is for border routers constraints), the simplist form of deployment is for border routers
to be configured as edge routers, and for non-border routers (for to be configured as edge routers, and for non-border routers (for
instance the routers used as route reflectors) to be configured as instance the routers used as route reflectors) to be configured as
core routers. S-VA, however, does not mandate this deployment per core routers. S-VA, however, does not mandate this deployment per
se. se.
 End of changes. 9 change blocks. 
27 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/