[rrg] Summary of Tuneled Inter-domain Routing (TIDR)

Juan Jose Adan <juanjose.adan@gmail.com> Tue, 22 December 2009 21:48 UTC

Return-Path: <juanjose.adan@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91AEC3A6894 for <rrg@core3.amsl.com>; Tue, 22 Dec 2009 13:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2PsvxeZvTA6z for <rrg@core3.amsl.com>; Tue, 22 Dec 2009 13:48:54 -0800 (PST)
Received: from mail-ew0-f210.google.com (mail-ew0-f210.google.com [209.85.219.210]) by core3.amsl.com (Postfix) with ESMTP id 319B73A6839 for <rrg@irtf.org>; Tue, 22 Dec 2009 13:48:53 -0800 (PST)
Received: by ewy2 with SMTP id 2so7735978ewy.7 for <rrg@irtf.org>; Tue, 22 Dec 2009 13:48:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=1LJQgEWXVw3Rk63RL7+ySc5bxcaW3ZZsBldO0NElBiQ=; b=BS9L4ehs8rLCU3CrAVtopB4YUM8z5tJBDv3eErXO2Pj/Xe6+exR0+ze6x0eAl0dsn5 4XXIRj8WOoxVhM+zBxedY+DfPZ8nrHOYk5bfhsVaB4951d6QLPXDFdGBvAGu3icGTIWS APfQ59Dq9wswYXzHFaI73+DrBfV5W96M3RiJQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=dznYiFE/aNOArKUH7zQ1WF3e8gIDBAvSUDw6DJRf7f4xV11fTGHj8AFoniDKuih/L6 5z3jEbUvvphZiRlxVPwLe0zec91HiHyk2AMrya+RXbPgO6RJH2YKwV70lN5cj7vqWYeA WtW0LOx7gHGt5khdcUtAHLCkwbX/cMhd1Bb20=
MIME-Version: 1.0
Received: by 10.216.88.83 with SMTP id z61mr3126485wee.140.1261518515911; Tue, 22 Dec 2009 13:48:35 -0800 (PST)
Date: Tue, 22 Dec 2009 22:48:35 +0100
Message-ID: <a33fd8400912221348s79c950f5l22f575cab14dd02a@mail.gmail.com>
From: Juan Jose Adan <juanjose.adan@gmail.com>
To: Lixia Zhang <lixia@cs.ucla.edu>
Content-Type: multipart/alternative; boundary=0016e6d6417704bc6f047b582b58
Cc: rrg@irtf.org
Subject: [rrg] Summary of Tuneled Inter-domain Routing (TIDR)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Dec 2009 21:48:55 -0000

Hi Lixia:

Here is the summary of Tunneled Inter-domain Routing (TIDR).

Merry Christmas.

Juanjo



PROPOSAL
--------

Tunneled Inter-domain Routing (TIDR)


KEY IDEA
--------
Provides a method for locator-identifier separation using tunnels between
routers
of the edge of the Internet transit infrastructure. It enrichs BGP protocol
for
distributing the identifier-to-locator mapping. Using new BGP atributes
"identifier
prefixes" are assigned interdomain routing locators so that they will not be
installed in the RIB and will be moved to a new table called Tunnel
Information Base
(TIB). Afterwards, when routing a packet to the "identifier prefix", the TIB
will be
searched first to perform tunnel imposition, and secondly the RIB for actual
routing.
After the edge router performs tunnel imposition, all routers in the middle
will
route this packet until the router being the tail-end of the tunnel.

GAINS
-----
- Smooth deployment
- Size Reduction of the Global RIB Table
- Deterministic Customer Traffic Engineering for Incoming Traffic
- Numerous Forwarding Decisions for a Particular Address Prefix
- TIDR Stops AS Number Space Depletion
- Improved BGP Convergence
- Protection of the Inter-domain Routing Infrastructure
- Easy Separation of Control Traffic and Transit Traffic
- Different Layer-2 Protocol-IDs for Transit and Non-Transit Traffic
- Multihoming Resilience
- New Address Families and Tunneling Techniques
- TIDR for IPv4 or IPv6, and Migration to IPv6
- Scalability, Stability and Reliability
- Faster Inter-domain Routing

COSTS
-----
- Routers of the edge of the interdomain infrastructure will need to be
 upgraded
to hold the mapping database (i.e. the TIB)

- "Mapping updates" will need to be treated differently from usual BGP
"routing updates"




DOCUMENTATION
-------------
The draft I submitted to the IETF is located on:
http://tools.ietf.org/html/draft-adan-idr-tidr-01

Here there are some other links that add more information:

--> on scalability of the global BGP table and reducing BGP churn
http://www.ietf.org/mail-archive/web/ram/current/msg01308.html
[RAM] TIDR using the IDENTIFIERS attribute (19-April-2007)

--> on the different role of transit and non-transit ASes
http://www.ops.ietf.org/lists/rrg/2007/msg00902.html
[RRG] LISP etc architecture  (20-Sept-2007)

--> on AS-based routing with very fine granularity
http://www.ops.ietf.org/lists/rrg/2008/msg00716.html
[RRG] yetAnotherProposal: AS-number forwarding  (11-March-2008)