From emv@garnet.msen.com Fri Mar 26 23:18:22 1993
Received: from [148.59.1.11] by fido.wps.com (5.67/1.34)
	id AA04041; Fri, 26 Mar 93 23:18:13 -0800
Received: by garnet.msen.com (/\==/\ Smail3.1.25.1 #25.5)
	id <m0ncVB2-001IDqC@garnet.msen.com>; Sat, 27 Mar 93 02:19 WET
Message-Id: <m0ncVB2-001IDqC@garnet.msen.com>
To: tomj@fido.wps.com (Tom Jennings)
Cc: toaster-list@psg.com (toasternet mailing list)
Subject: Re: Updated 'questions for IP carriers'... 
In-Reply-To: Your message of Fri, 26 Mar 93 21:31:56.
             <9303270531.AA03961@fido.wps.com> 
Date: Sat, 27 Mar 93 02:19:21 EST
From: Edward Vielmetti <emv@mail.msen.com>
Status: OR

if you are going to act like a network (rather than a batch of hosts)
the right quetsion might be

  o Will you be an EGP/BGP peer with our network?

The adminstrative structure necessary for this runs like so:

- network applies for an "autonomous system number" from the NIC
- individual nets within the group get added to this autonomous system
- the EGP/BGP peering exchanges routing information on an
  autonomous system to autonomous system level, not just one route 
  at a time.

To pull this off you need a cisco or a BSD machine running 'gated' to
act as the peer.  No harder than e.g. keeping your clocks current with
ntp, but the fraternity that understands how this stuff works keeps it
close to themselves.

  Edward Vielmetti, vice president for research, Msen Inc. emv@Msen.com
Msen Inc., 628 Brooks, Ann Arbor MI  48103 +1 313 998 4562 (fax: 998 4563)


From emv@garnet.msen.com Fri Mar 26 23:57:41 1993
Received: from garnet.msen.com by fido.wps.com (5.67/1.34)
	id AA04102; Fri, 26 Mar 93 23:57:34 -0800
Received: by garnet.msen.com (/\==/\ Smail3.1.25.1 #25.5)
	id <m0ncVne-001IDqC@garnet.msen.com>; Sat, 27 Mar 93 02:59 WET
Message-Id: <m0ncVne-001IDqC@garnet.msen.com>
To: tomj@fido.wps.com (Tom Jennings)
Subject: Re: Updated 'questions for IP carriers'... 
In-Reply-To: Your message of Fri, 26 Mar 93 23:30:31.
             <9303270730.AA04076@fido.wps.com> 
Date: Sat, 27 Mar 93 02:59:15 EST
From: Edward Vielmetti <emv@mail.msen.com>
Status: OR

EGP is "Exterior Gateway Protocol" from back in the days when there
was an "interior" network, the ARPANET core, and "exterior" networks
forming around it.

BGP is "Border Gateway Protocol" or maybe "Border Gateway Patrol" :)

gated sources are on gated.cornell.edu

The NIC assigns autonomous system numbers without much fanfare, just
ask and you get one.  The NSFnet has forms which you fill out on line
and send in to Ann Arbor to change your NSFnet routing information.
Then you just need to get your EGP or BGP session to be heard
throughout the net.

The idea I think is that if you behave like a regional network you get
treated like one, and that not *everyone* needs to be a regional network.

  Edward Vielmetti, vice president for research, Msen Inc. emv@Msen.com
Msen Inc., 628 Brooks, Ann Arbor MI  48103 +1 313 998 4562 (fax: 998 4563)


