comment on numbers of border routers
barns@cove.mitre.org Tue, 07 April 1992 17:35 UTC
Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa05909;
7 Apr 92 13:35 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa19978;
7 Apr 92 13:38 EDT
Received: from PARK-STREET.BBN.COM by NRI.Reston.VA.US id aa19974;
7 Apr 92 13:38 EDT
Received: from park-street by PARK-STREET.bbn.COM id aa04217;
7 Apr 92 13:15 EDT
Received: from BBN.COM by PARK-STREET.BBN.COM id aa04213; 7 Apr 92 13:14 EDT
Received: from gateway.mitre.org by BBN.COM id aa16508; 7 Apr 92 13:13 EDT
Return-Path: <barns@cove.mitre.org>
Received: from [128.29.31.100] by gateway.mitre.org (5.61/SMI-2.2)
id AA04927; Tue, 7 Apr 92 13:13:05 -0400
Received: by cove.mitre.org (4.1/SMI-4.1)
id AA13861; Tue, 7 Apr 92 13:12:06 EDT
Message-Id: <9204071712.AA13861@cove.mitre.org>
To: idpr-wg@bbn.com
Cc: barns@cove.mitre.org
Subject: comment on numbers of border routers
In-Reply-To: Gene Tsudik's message of "Tue, 07 Apr 92 16:56:04 +0700."
<9204071510.AA03543@gateway.mitre.org>
Date: Tue, 07 Apr 92 13:12:02 -0400
From: barns@cove.mitre.org
I think one of the main reasons that people buy routers in the first place is to create "borders". (For example, you want to keep the NFS traffic on "THEIR" ethernet from slowing down "YOUR" traffic.) Not all kinds of "borders" necessarily correspond to logical applications for IDPR or policy routing in general, but it doesn't seem surprising to me that a lot of routers turn up at "border" locations. If it seemed reasonable for the traffic on "both sides" of a router to be the same, you could have used a bridge or a wire, right? Of course I'm over-generalizing but I think there is an element of Scalable Truth here. /Bill Barns