Re: [rrg] RANGER(S)
"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 19 May 2009 16:33 UTC
Return-Path: <Fred.L.Templin@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 1ABA93A69E4 for <rrg@core3.amsl.com>; Tue, 19 May 2009 09:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.004
X-Spam-Level:
X-Spam-Status: No, score=-6.004 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
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 PnJOVA2op-q9 for <rrg@core3.amsl.com>; Tue, 19 May 2009 09:33:11 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 57D4D3A68B0 for <rrg@irtf.org>; Tue, 19 May 2009 09:33:11 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n4JGYiWP004487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 19 May 2009 11:34:45 -0500 (CDT)
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 n4JGYiuf003618; Tue, 19 May 2009 11:34:44 -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 n4JGYiZC003591; Tue, 19 May 2009 11:34:44 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 19 May 2009 09:34:44 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9D89F.B6BE8EE9"
Date: Tue, 19 May 2009 09:34:42 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105F43B01@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <d49.472abe45.3743ba4b@aol.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rrg] RANGER(S)
Thread-Index: AcnYU2tlKwyfUJtsQ6+lOP42lqOCfAAStFwg
References: <d49.472abe45.3743ba4b@aol.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: HeinerHummel@aol.com, rrg@irtf.org
X-OriginalArrivalTime: 19 May 2009 16:34:44.0520 (UTC) FILETIME=[B767C280:01C9D89F]
Subject: Re: [rrg] RANGER(S)
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, 19 May 2009 16:33:14 -0000
Heiner, > I have never understood either that inter- and intra-domain routing architectures have to be such orthogonal. > So whatever I proposed or supported so far was aiming to a consistent architectural framework, too. > Routing, which is not based on address summarization, would make sense inside of intra-domain-networks as well. Do these other approaches show how they recurse from the Internet core all the way to a singleton node as the limiting factor for recursion - or even to virtual networks within a singleton node? Do the other approaches provide for discovery and utilization of multiple border routers? Do they have fully-articulated specifications for automatic EID and RLOC address configuration? Do they support multihoming? Provider-independent addressing? IPv6 deployment? Traffic engineering? Secure redirection? Ingress filtering? What about mobility? MTU handling for tunnels? _Do the other approaches have their base mechanisms widely deployed in shipping implementations for many years, and with many millions of users?_ Is maturity important to this group? What about completeness? Fred fred.l.templin@boeing.com ________________________________ From: HeinerHummel@aol.com [mailto:HeinerHummel@aol.com] Sent: Tuesday, May 19, 2009 12:31 AM To: Templin, Fred L; rrg@irtf.org Subject: Re: [rrg] RANGER(S) In einer eMail vom 19.05.2009 01:26:57 Westeuropäische Normalzeit schreibt Fred.L.Templin@boeing.com: but in our experience RANGER(S) is the only proposal with a consistent architectural framework that applies recursively in a "network-of-networks" fashion from the global Internet core all the way outward to even the simplest of edge networks. I have never understood either that inter- and intra-domain routing architectures have to be such orthogonal. So whatever I proposed or supported so far was aiming to a consistent architectural framework, too. Routing, which is not based on address summarization, would make sense inside of intra-domain-networks as well. Heiner
- Re: [rrg] RANGER(S) HeinerHummel
- Re: [rrg] RANGER(S) Templin, Fred L
- Re: [rrg] RANGER(S) HeinerHummel