MAGIC, AAI, and the vBNS are all federally-funded research networks. Researchers on the three networks would like to be able to share data across the network boundaries. In particular, researchers at NCAR (connected to the vBNS) and NAVO Stennis (connected to AAI) have an application which can make use of data at the EROS Data Center (EDC) (connected to MAGIC). As a backup to EDC, researchers would also like access to data on hosts at the Sprint TIOC (connected to MAGIC and AAI) and SRI (connected to MAGIC).
AAI and the vBNS come very close to each other at the San Diego Supercomputer Center (SDSC). SDSC is therefore a natural place to interconnect the three networks.
This document provides a plan for the interconnection of MAGIC, AAI, and the vBNS. It is expected to change as the plan evolves.
MAGIC and AAI are already interconnected at the Sprint TIOC. ATM switches in the two networks exchange ATM-level routing information, making the two networks effectively a single ATM network. An end system attached to either network can open a VCC to any other end system attached to either network.
There are links which connect ATM switches belonging to the vBNS and AAI, via an ATM switch at SDSC (see Figure 1 ). There is no exchange of ATM-level routing information, however, leaving the vBNS as a separate ATM network.
No new ATM links are required to interconnect the three networks, but it is necessary to perform some further configuration (e.g. establishing PVCs or PVPs) to allow cells to flow.
There is currently no direct IP connectivity between the three networks. Table 1 shows the IP network numbers used by each network.
While MAGIC and AAI effectively run on the same ATM network, they comprise seperate Logical IP Subnets (LISs). There is no routing of IP packets between hosts on the two networks. If a host on MAGIC needs to communicate with a host on AAI, it is usually configured as an AAI host. This involves:
Packets from the vBNS are not currently routed directly to either MAGIC or AAI. In order to enable routing between the two networks, there must be an exchange of IP-level routing information between them. The natural choice for this exchange would be to establish a connection between the I-DREN and vBNS routers at SDSC using an exterior gateway protocol such as BGP4.
There are two main approaches to interconnecting the networks:
An ATM-level connection would connect one or more of the vBNS's ATM switches to MAGIC/AAI ATM switches. The switches would exchange ATM-level routing information. ATM VCCs could be established between any two end systems attached to the three networks.
An IP-level connection would connect a vBNS router to a MAGIC/AAI router. The routers would exchange IP-level routing information (e.g. via BGP4). IP datagrams could be exchanged between the routers, but no end-to-end ATM VCCs would exist. As shown in Figure 1 , the routers in this case could communicate via either FDDI or ATM. IP-level connection was chosen as the most practical way to achieve the interconnection.
Figure 1 shows the paths at SDSC between AAI and the vBNS. SDSC has both a vBNS node and a connection to the Interim Defense Research and Engineering Network (I-DREN). The I-DREN router at SDSC has potential ATM connectivity to AAI via an ATM switch at NCCOSC, but is not part of any AAI IP network.
The interconnection of the networks was discussed on a conference call in late August 1997 and via email and the following options were explored:
The consensus of the group was that no. 2 was the preferred option in the absence of a direct connection between the SDSC and vBNS ATM switches but that no. 3 was preferred. For no. 3 , the following work items must be accomplished:
Initially, connectivity will be established via method no. 3 , but will be changed to no. 4 as circumstances permit, since this results in one fewer hop between the networks, and fewer administrative bodies need to be involved.
The following work items have been completed:
With these items done, the interconnection between MAGIC/AAI and the vBNS is complete.