[Date Next]
[Thread Prev]
[Thread Next]
AS and IP network needs
- To: not-rr@town.hall.org
- Subject: AS and IP network needs
- From: Marten Terpstra <marten@BayNetworks.com>
- Date: Wed, 29 Nov 1995 15:06:44 -0500
- Reply-To: not-rr@town.hall.org
- Sender: owner-not-rr@town.hall.org
Well, I thought a bit more of our AS and IP network number needs and I think we will need the following:
NPB - use IP nets that are already there - use another subnet for the T3 to MAE-EAST - use AS number already in use
MAE-EAST - possibly a new AS number - depends on transit arrangements between MAE-EAST to NPB and MAE-EAST to WTN - no need for IP networks currently - T3 to NPB will get IP addr from NPB - MAE EAST will get IP addr from BBN - T3 to WTN will get IP addr from WTN
WTN - a new AS number - one class C - link to MAE-EAST - link to Tokyo - loopback
(DC is the most difficult one, because of all the backup transit possibilities)
TOKYO - a new AS number - no need for IP addresses IF - the interconnect in Tokyo is already numbered - T3 from WTN is numbered from WTN addr space - central park server lives on this interconnect
Amsterdam - a new AS number (to be requested from RIPE NCC) - an IP address (to be requested from RIPE NCC or primary transit provider in Amsterdam) - for central park server net
London (when it happens) - a new AS number (from RIPE NCC) IF - no one provides backup transit from London to MAE-EAST - a class C (from RIPE NCC) IF - interconnect in London is not yet numbered - assuming T3 to London would go to a FAIR site that has an IP network number
That is as far as I could think right now. The need for all these ASes with only one router is ugly, but necessary since we have no redundancy between the routers and backup transit arrangements. We cannot split our AS due to line failure...
-Marten
[Date Prev]
[Date Next]
[Thread Prev]
[Thread Next]