[rrg] Proposal: 2-phased mapping for Internet core/edge split schemes

wei zhang <zhangwei734@gmail.com> Mon, 21 December 2009 13:25 UTC

Return-Path: <zhangwei734@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id B80E928C11F for <rrg@core3.amsl.com>; Mon, 21 Dec 2009 05:25:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_83=0.6]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id wFJIU0tybsrn for <rrg@core3.amsl.com>; Mon, 21 Dec 2009 05:25:46 -0800 (PST)
Received: from mail-vw0-f203.google.com (mail-vw0-f203.google.com []) by core3.amsl.com (Postfix) with ESMTP id 1C60228C0E3 for <rrg@irtf.org>; Mon, 21 Dec 2009 05:25:46 -0800 (PST)
Received: by vws41 with SMTP id 41so1486131vws.15 for <rrg@irtf.org>; Mon, 21 Dec 2009 05:25:26 -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:content-type; bh=zDOHStxcqVpUOutnnNSjrjvb6roOHQPjh0hud3yzz/8=; b=QLLXzPsOexcRAp8wZR6XjZThuCogkLTHi9R7Tq26KkwR3PY0FXeyPIFKj+BEcZg6u1 3ZAGV9utqotkQJU3MBkT0E9/YPpHjTPud9VYcYeKz2OVXSEfxHjQCVUd67PvH8+Xd/DG Wt4F2KiVpq7ck1aP+2uXjq72H8FXRPZOjEoh8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Mf6M9sDGDSHX+U/UP0VyeGBhOf3yZG3a5pJqOHGLhZZc7Z8cZpj4O3qGLPuVktz9sN Mhb5FAea9436lYnvJBTS9T7TG1BhtmkirPLyoqOxg1zmsOg/Yq1LuLky+iDmtpHcFk+i cyABNGF2Bu6lxBLvwh3nniGWyRGVkdANLs8u8=
MIME-Version: 1.0
Received: by with SMTP id i11mr623718vcr.51.1261401926508; Mon, 21 Dec 2009 05:25:26 -0800 (PST)
Date: Mon, 21 Dec 2009 21:25:26 +0800
Message-ID: <a3c6b13a0912210525i5ff7327au5f8d31592a9df77c@mail.gmail.com>
From: wei zhang <zhangwei734@gmail.com>
To: rrg@irtf.org
Content-Type: multipart/mixed; boundary="001636c92a51bfa05e047b3d0587"
Subject: [rrg] Proposal: 2-phased mapping for Internet core/edge split schemes
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: Mon, 21 Dec 2009 13:25:47 -0000

I propose a 2-phase mapping scheme which could be used and independent
of any core/edge split mechanism(such as LISP or eFIT etc.).

 The motive: to reduce the dynamic of mapping updates and facilitate
effective mapping look up.

1.Mapping from prefixes to ETRs is an M:M mapping. Any change of
(prefix, ETR) pair should be updated timely which can be a heavy
burden to any mapping systems if the relation changes frequently.
2.prefix<->ETR mapping system cannot be deployed efficiently if it is
overwhelmed by the worldwide dynamics. Therefore the mapping itself is
not scalable with this direct mapping scheme.

 My contribution: a 2-phased mapping
1.Introduce AS number in the middle of the mapping, phase I mapping is
prefix<->AS#, phase II mapping is AS#<->ETRs. We have a M:1:M mapping
model now.
2.My assumption is that all ASes know better their local prefixes (in
the IGP) than others. and most likely local prefixes  can be
aggregated when map them to the AS#, which will make the mapping entry
reduction possible, ASes also know clearly their ETRs on its border
between core and edge. So all mapping information can be collected
3.A registry system will take care of the phase I mapping information.
Each AS should have a register agent to notify the local range of IP
address space to the registry. This system can be organized as a
hierarchical infrastructure like DNS, or alternatively as a
centralized registry like "whois" in each RIR. Phase II mapping
information can be distributed between XTRs as a BGP extension.
4. A basic forwarding procedure is that ITR firstly get the
destination AS# from phase I mapper (or from cache) when the packet is
entering the "core". Then it will check the closest ETR of destination
AS#, since phase 2 mapping information has been "pushed" to it through
BGP updates. At last the ITR encap the packet and tunnel it to a
corresponding ETR.

1.Any prefixes reconfiguration (aggregation/ deaggregation) within an
AS will not be notified to mapping system.
2.Possible highly efficient aggregation of the local prefixes (in the
form of an IP space range).
3.Both phase I and phase II mapping can be stable.
4.A stable mapping system will reduce the update overhead introduced
by topology change/routing policy dynamics.ETR.

1.The 2-phased mapping scheme introduces AS# between the mapping
prefixes and ETRs.
2.The decoupling of direct mapping makes highly dynamic updates
stable, therefore it can be more scalable than any direct mapping
3.The 2-phased mapping scheme is adaptable to any core/edge split
based proposals.

Wei Zhang