[comp.protocols.tcp-ip] routing to net 26

oleary@NOC.SURA.NET (dave o'leary) (07/28/90)

Currently there is no mailbridge connection at FIX East, and therefore
we do not inject routing information about Milnet networks into the
NSFnet here.  We are working with DCA and the staff at Mitre to bring
back the connection to the Mitre Mailbridge as an interim solution.
Further down the road (possibly September) there will be a mailbridge
connected directly to the FIX East ethernet here in our machine room.

This explains why packets to *any* host with Milnet-only connectivity
will traverse the NSFnet backbone to the NSS in Palo Alto (BARRnet),
where the Milnet routes are being advertised to the NSFnet.

Even when the East Coast FIX node is peering directly with the NSS, 
the NSS here accepts a route to net 26 only as a secondary (at least 
this is my understanding of the situation).  The East Coast mailbridge
node will be primary for those nets in the Eastern US, and the West 
coast node primary for the networks in the Western US.  However, 
net 26 is accepted as a primary advertisement at the BARRnet NSS, 
so as long as that peering is working, packets addressed to hosts 
on net 26 will go via the BARRnet NSS and Moffett Field Mailbridge, 
regardless of the geographic location of beginning and end points.

The situation is explained in more detail in RFC1133.

Thanks,

					dave o'leary
					SURAnet

					oleary@noc.sura.net
					(301)982-3214