--- 1/draft-ietf-grow-va-03.txt 2011-02-22 14:21:20.000000000 +0100 +++ 2/draft-ietf-grow-va-04.txt 2011-02-22 14:21:20.000000000 +0100 @@ -1,103 +1,103 @@ Network Working Group P. Francis Internet-Draft MPI-SWS Intended status: Informational X. Xu -Expires: March 4, 2011 Huawei +Expires: August 26, 2011 Huawei H. Ballani Cornell U. D. Jen UCLA R. Raszuk Cisco L. Zhang UCLA - August 31, 2010 + February 22, 2011 FIB Suppression with Virtual Aggregation - draft-ietf-grow-va-03.txt + draft-ietf-grow-va-04.txt Abstract The continued growth in the Default Free Routing Table (DFRT) stresses the global routing system in a number of ways. One of the most costly stresses is FIB size: ISPs often must upgrade router hardware simply because the FIB has run out of space, and router vendors must design routers that have adequate FIB. FIB suppression is an approach to relieving stress on the FIB by NOT loading selected RIB entries into the FIB. Virtual Aggregation (VA) allows ISPs to shrink the FIBs of any and all routers, easily by an order of magnitude with negligible increase in path length and load. FIB suppression deployed autonomously by an ISP (cooperation between ISPs is not required), and can co-exist with legacy routers in the ISP. + There are no changes from the 03 version. 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 March 4, 2011. + This Internet-Draft will expire on August 26, 2011. Copyright Notice - Copyright (c) 2010 IETF Trust and the persons identified as the + Copyright (c) 2011 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 . . . . . . . . . . . . . . . . . . 4 - 1.2. Requirements notation . . . . . . . . . . . . . . . . . . 5 - 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 - 2. Overview of Virtual Aggregation (VA) . . . . . . . . . . . . . 6 - 2.1. Mix of legacy and VA routers . . . . . . . . . . . . . . . 8 - 2.2. Summary of Tunnels and Paths . . . . . . . . . . . . . . . 9 - 3. Specification of VA . . . . . . . . . . . . . . . . . . . . . 10 - 3.1. VA Operation . . . . . . . . . . . . . . . . . . . . . . . 11 - 3.1.1. Legacy Routers . . . . . . . . . . . . . . . . . . . . 11 - 3.1.2. Advertising and Handling Virtual Prefixes (VP) . . . . 11 - 3.1.3. Border VA Routers . . . . . . . . . . . . . . . . . . 15 - 3.1.4. Advertising and Handling Sub-Prefixes . . . . . . . . 15 - 3.1.5. Suppressing FIB Sub-prefix Routes . . . . . . . . . . 16 - 3.2. New Configuration . . . . . . . . . . . . . . . . . . . . 17 - 4. Usage of Tunnels . . . . . . . . . . . . . . . . . . . . . . . 18 - 4.1. MPLS tunnels . . . . . . . . . . . . . . . . . . . . . . . 18 - 4.2. Usage of Inner Label . . . . . . . . . . . . . . . . . . . 19 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 19 - 6.1. Properly Configured VA . . . . . . . . . . . . . . . . . . 19 - 6.2. Mis-configured VA . . . . . . . . . . . . . . . . . . . . 20 - 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 - 8.1. Normative References . . . . . . . . . . . . . . . . . . . 21 - 8.2. Informative References . . . . . . . . . . . . . . . . . . 21 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 1.1. Scope of this Document . . . . . . . . . . . . . . . . . . 5 + 1.2. Requirements notation . . . . . . . . . . . . . . . . . . 6 + 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 + 2. Overview of Virtual Aggregation (VA) . . . . . . . . . . . . . 7 + 2.1. Mix of legacy and VA routers . . . . . . . . . . . . . . . 9 + 2.2. Summary of Tunnels and Paths . . . . . . . . . . . . . . . 10 + 3. Specification of VA . . . . . . . . . . . . . . . . . . . . . 11 + 3.1. VA Operation . . . . . . . . . . . . . . . . . . . . . . . 12 + 3.1.1. Legacy Routers . . . . . . . . . . . . . . . . . . . . 12 + 3.1.2. Advertising and Handling Virtual Prefixes (VP) . . . . 12 + 3.1.3. Border VA Routers . . . . . . . . . . . . . . . . . . 16 + 3.1.4. Advertising and Handling Sub-Prefixes . . . . . . . . 16 + 3.1.5. Suppressing FIB Sub-prefix Routes . . . . . . . . . . 17 + 3.2. New Configuration . . . . . . . . . . . . . . . . . . . . 18 + 4. Usage of Tunnels . . . . . . . . . . . . . . . . . . . . . . . 19 + 4.1. MPLS tunnels . . . . . . . . . . . . . . . . . . . . . . . 19 + 4.2. Usage of Inner Label . . . . . . . . . . . . . . . . . . . 20 + 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 20 + 6.1. Properly Configured VA . . . . . . . . . . . . . . . . . . 20 + 6.2. Mis-configured VA . . . . . . . . . . . . . . . . . . . . 21 + 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 + 8.1. Normative References . . . . . . . . . . . . . . . . . . . 22 + 8.2. Informative References . . . . . . . . . . . . . . . . . . 22 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 1. Introduction 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 growth outstrips the size of the FIB. This is too expensive for many ISPs. They would prefer to extend the lifetime of routers whose FIBs can no longer hold the full DFRT. A common approach taken by lower-tier ISPs is to default route to