[Int-area] Identifier-locator separation work and routing scalability

Jari Arkko <jari.arkko@piuha.net> Wed, 25 April 2007 10:47 UTC

Return-path: <int-area-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgf1e-0001dx-It; Wed, 25 Apr 2007 06:47:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgf1d-0001dm-QE for int-area@ietf.org; Wed, 25 Apr 2007 06:47:05 -0400
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hgf1d-0003rg-Az for int-area@ietf.org; Wed, 25 Apr 2007 06:47:05 -0400
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A8A5119868C; Wed, 25 Apr 2007 13:47:04 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 6CD2B19868B; Wed, 25 Apr 2007 13:47:04 +0300 (EEST)
Message-ID: <462F31A9.3050408@piuha.net>
Date: Wed, 25 Apr 2007 13:47:05 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: ram@iab.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: Internet Area <int-area@ietf.org>
Subject: [Int-area] Identifier-locator separation work and routing scalability
X-BeenThere: int-area@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Jari Arkko <jari.arkko@piuha.net>, ram@iab.org
List-Id: IETF Internet Area Mailing List <int-area.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/int-area>
List-Post: <mailto:int-area@lists.ietf.org>
List-Help: <mailto:int-area-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=subscribe>
Errors-To: int-area-bounces@lists.ietf.org

At the last IETF meeting in Prague, we spent our int-area
open meeting time presenting on and providing open mic
discussion for identifier/locater split solution design in
general, as well as in specific reference to recent energy
from the service provider community looking for
fundamental routing scalability improvements.

Work on the routing and addressing problem is happening
in several parallel efforts, including implementation
improvements by vendors, review of operational practices,
modest improvements to the BGP protocol, and more
fundamental architectural changes either through
new types of routing architectures or identifier-locator
separation.

Some of these activities fall clearly on one forum, whereas
in others we've had more confusion where  the work
belongs. In particular, there is a lot of  current
identifier-locator and locator-locator separation effort
in the Internet area, we held int-area, rtg-area, and
plenary meetings in Prague, and the Routing Research
Group (RRG) is now looking at new routing and addressing
architectures. To avoid duplication of effort, the Internet
ADs would like to recommend that for solving the routing
scalability problem, the research and exploration phase
needed before standardization work should continue in
the RRG for now rather than in the IETF.

Current id/loc and loc/loc work for mobility and multihoming
in the int-area (such as HIP) will continue unabated, and we
encourage  participation in the discussion sponsored by the
IAB and IRTF.

When the RRG reaches a point where part or all of its effort
requires engineering work, we are eager to create a new or
recharter an existing working group for this via the normal
IETF process. We will send another note later on how to best
start such work in the IETF. Work does not have to come from
the RRG alone, but we are not going to actively cultivate
work in the int-area on this at this time.

Given this, we will not be hosting an Interim meeting on this
topic before Chicago. The RRG and IAB still may on their own
accord, but the main activity that we are currently aware of is
the RRG meeting in Chicago (Friday, July 27th).

Jari Arkko
Mark Townsley


_______________________________________________
Int-area mailing list
Int-area@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/int-area