Re: [rrg] Summary of Tuneled Inter-domain Routing (TIDR)
Tony Li <tony.li@tony.li> Thu, 24 December 2009 00:38 UTC
Return-Path: <tony.li@tony.li>
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 BFFC13A6825 for <rrg@core3.amsl.com>; Wed, 23 Dec 2009 16:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.24
X-Spam-Level:
X-Spam-Status: No, score=-2.24 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599]
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 aJ707MkKvh9X for <rrg@core3.amsl.com>; Wed, 23 Dec 2009 16:38:56 -0800 (PST)
Received: from QMTA02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by core3.amsl.com (Postfix) with ESMTP id E20BB3A6806 for <rrg@irtf.org>; Wed, 23 Dec 2009 16:38:55 -0800 (PST)
Received: from OMTA03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by QMTA02.emeryville.ca.mail.comcast.net with comcast id LoJ01d0150b6N64A2oegLK; Thu, 24 Dec 2009 00:38:40 +0000
Received: from [192.168.0.110] ([24.6.155.154]) by OMTA03.emeryville.ca.mail.comcast.net with comcast id Loef1d0013L8a8Q8PoefAQ; Thu, 24 Dec 2009 00:38:39 +0000
Message-ID: <4B32B80C.7050001@tony.li>
Date: Wed, 23 Dec 2009 16:38:36 -0800
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Juan Jose Adan <juanjose.adan@gmail.com>
References: <a33fd8400912221348s79c950f5l22f575cab14dd02a@mail.gmail.com>
In-Reply-To: <a33fd8400912221348s79c950f5l22f575cab14dd02a@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: rrg@irtf.org
Subject: Re: [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: Thu, 24 Dec 2009 02:23:09 -0000
Received and incorporated. Tony Juan Jose Adan wrote: > 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) > > > > ------------------------------------------------------------------------ > > _______________________________________________ > rrg mailing list > rrg@irtf.org > http://www.irtf.org/mailman/listinfo/rrg