Re: [rrg] Inter/intra-domain routing separation

"Fleischman, Eric" <eric.fleischman@boeing.com> Tue, 12 May 2009 15:47 UTC

Return-Path: <eric.fleischman@boeing.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 ED3073A6BAD for <rrg@core3.amsl.com>; Tue, 12 May 2009 08:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.11
X-Spam-Level:
X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
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 39Ti-PWd0uyU for <rrg@core3.amsl.com>; Tue, 12 May 2009 08:47:32 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 34D173A6912 for <rrg@irtf.org>; Tue, 12 May 2009 08:47:32 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n4CFn32A026297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <rrg@irtf.org>; Tue, 12 May 2009 08:49:03 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n4CFn2wU006047 for <rrg@irtf.org>; Tue, 12 May 2009 10:49:02 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n4CFmvNo005516 for <rrg@irtf.org>; Tue, 12 May 2009 10:49:02 -0500 (CDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 12 May 2009 08:48:59 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 May 2009 08:48:58 -0700
Message-ID: <474EEBD229DF754FB83D256004D021080BB9A6F4@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <200905070540.06216.irtf@tonistoev.info>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rrg] Inter/intra-domain routing separation
Thread-Index: AcnOvSnJ6DURObQHQ9K7BgZuYU76FAEWfsXQ
References: <200905051235.41286.irtf@tonistoev.info><200905060235.52415.irtf@tonistoev.info> <200905070540.06216.irtf@tonistoev.info>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: IRTF RRG <rrg@irtf.org>
X-OriginalArrivalTime: 12 May 2009 15:48:59.0530 (UTC) FILETIME=[2A5F46A0:01C9D319]
Subject: Re: [rrg] Inter/intra-domain routing separation
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, 12 May 2009 15:47:33 -0000

It is my personal opinion that most of these definitions are already
well established in Internet parlance and therefore re-definitions are
not warranted (or needed).

It is also my personal opinion that some of the recent postings could
have been resolved by reference to well-established traditional
architectural principals such as the IP Topology Hierarchy, which
defines topology layers such as "autonomous systems" as well as routing
concepts such as intra-domain and inter-domain.

Coworkers who think as I do in terms of historic Internet constructs
such as those articulated by Catenet, the ROAD Group, or NIMROD will
probably think in terms of recursion and the possibility of creating
complex structures within IP Topology Hierarchy layers. The power and
beauty of this historic model when applied to the IP Topology Hierarchy
framework is amazingly impressive. But that is the topic for another
posting... The goal of this posting is solely to express my personal
opinion that historic Internet concepts and traditional Internet
terminology retain great value, power, and usefulness and should not
easily be overlooked (or modified).