Re: [rrg] belated msg: further description of the recommendation process

Vince Fuller <vaf@cisco.com> Tue, 15 December 2009 00:17 UTC

Return-Path: <vaf@cisco.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 3D2013A63D3 for <rrg@core3.amsl.com>; Mon, 14 Dec 2009 16:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_BIZOP=0.7]
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 N8KtzOb9jcps for <rrg@core3.amsl.com>; Mon, 14 Dec 2009 16:17:32 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 0CC583A686D for <rrg@irtf.org>; Mon, 14 Dec 2009 16:17:32 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAA9kJkurR7Ht/2dsb2JhbADBO5ZahCsEgxWKDw
X-IronPort-AV: E=Sophos;i="4.47,397,1257120000"; d="scan'208";a="228778465"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 15 Dec 2009 00:17:19 +0000
Received: from vaf-lnx1 (vaf-lnx1.cisco.com [128.107.165.254]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id nBF0HJB5017435; Tue, 15 Dec 2009 00:17:19 GMT
Received: by vaf-lnx1 (Postfix, from userid 113818) id 9076B20815; Mon, 14 Dec 2009 16:16:30 -0800 (PST)
Date: Mon, 14 Dec 2009 16:16:30 -0800
From: Vince Fuller <vaf@cisco.com>
To: Lixia Zhang <lixia@CS.UCLA.EDU>
Message-ID: <20091215001630.GA15671@vaf-lnx1.cisco.com>
References: <5976B445-7209-4DE5-9D83-E2920265EB27@CS.UCLA.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5976B445-7209-4DE5-9D83-E2920265EB27@CS.UCLA.EDU>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: rrg@irtf.org
Subject: Re: [rrg] belated msg: further description of the recommendation process
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, 15 Dec 2009 00:17:33 -0000

> 1/ To steer efforts toward that goal, we would like each proposal to
> make a concise summary, preferably no longer than ~1000 words (it
> may contain pointer to more detailed document), that describes the
> key ideas of the proposal of exactly how it addresses routing
> scalability issue, where is its cost, and where is its gain.

Lixia, Tony-

Here is the response for LISP.

	--Vince
	(on behalf of the other LISP authors: Dino, Dave, and Darrel)

		--------------------

proposal:
---------
Locator Identifier Separation Protocol (LISP)

key idea:
---------
Implements a locator-identifier separation mechanism using encapsulation
between routers at the "edge" of the Internet. Such a separation allows
topological aggregation of the routeable addresses (locators) while
providing stable and portable numbering of end systems (identifiers).

gains:
------
- topological aggregation of numbering space (RLOCs) used for routing,
  which greatly reduces both the overall size and the "churn rate" of
  the information needed to operate the Internet global routing system
- seperate numbering space (EIDs) for end-systems, effectively allowing "PI
  for all" (no renumbering cost for connectivity changes) without adding
  state to the global routing system
- improved traffic engineering capabilities that explicitly do not add
  state to the global routing system and whose deployment will allow
  active removal of more-specific state currently used
- no changes required to end systems
- no changes to Internet "core" routers
- minimal and straightforward changes to "edge" routers
- day-one advatanges for early adopters
- defined router-to-router protocol
- defined database mapping system
- defined deployment plan
- defined interoperability/interworking mechanisms
- defined scalable end-host mobility mechanisms
- prototype implementation already exists and undergoing testing
- production implementations in progress

costs:
------
- mapping system infrastructure (map servers, map resolvers, ALT routers)
  (new potential business opportunity)
- Interworking infrastructure (proxy ITRs)
  (new potential business opportunity)
- overhead for determining/maintaining locator/path liveness (common issue
  for all id/loc separation proposals)

full documentation:
-------------------
draft-ietf-lisp-05.txt (LISP base specifiction, LISP WG draft)
draft-ietf-lisp-alt-01.txt (LISP+ALT mapping database, LISP WG draft)
draft-ietf-lisp-ms-02.txt (LISP Map Server, LISP WG draft)
draft-ietf-lisp-interworking-00.txt (Interworking mechanisms, LISP WG draft)
draft-meyer-lisp-mn-00.txt (LISP Mobile Node Architecture)
draft-farinacci-lisp-lig-01.txt (LISP Internet Groper debugging tool)
draft-meyer-lisp-loc-id-implications-01.txt (locator liveness considerations)