Path: utzoo!attcan!telly!lethe!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!MERIT.EDU!hwb From: hwb@MERIT.EDU (Hans-Werner Braun) Newsgroups: comp.protocols.tcp-ip Subject: Re: connect: Network is unreachable, (or) I want my FTP Message-ID: <9010132308.AA16298@kiddo.merit.edu> Date: 13 Oct 90 23:08:22 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 170 Ed Vielmetti: Given all your frequent interactions with the Merit/UMnet/NSFNET NOC with the hope for increased knowledge on your part about how things interact, I find it regrettable that you have to air your frustrations in public, in particular given the tone you used. Look, you describe access to a University, for which in general NSF takes a quite liberal view. If there is a University in at least a country that the US is friends with, NSF, to the best of my knowledge, never objected to have them be known to the NSFNET. With some international sites we need to get concurrance from a national coordination body, in the case you mentioned, University of Passau in Germany, we need concurrance from, e.g., DFN as a german national coordination body. Once we receive a confirmation we need to request permission from the NSF for each and every international network to be configured. The NSF confirmation is to protect both NSF as well as Merit. Sometimes, including in this case, where a network is requested to be configured via multiple NSS entry points, we also need to confirm the announcements with all the sites a network should be configured for, to allow for the proper coordination as well as the proper metric configuration for primary, secondary, etc. paths. All of this is standard procedure and should not take more than a few days. If a network is unknown, it has typically either not been requested for addition to the policy data base or it is not been dynamically announced at the time you tried by the client network to the NSS where it would be announced to or there is a time window between a request and the configuration (which should typically not last for more than a few days and only happen once until it is configured). I will attach some relevant messages which show you that you got caught in the window between request and configuration. An intelligent approach towards dealing with these kind of issues would be to communicate with your local provider of campus networking. Generally this should work fine with most campuses, which then deal with the appropriate regional network and/or the NSFNET NOC. In your case, as you know, they are all the same (UMnet + Merit + NSFNET) and you should have been able to get the information easily. You are otherwise wasting alot of time, effort and bandwidth. Hans-Werner Braun ------------------------------------------------------------------------------- To: nsfnet-admin@merit.edu Subject: Network Announcement Change Request Cc: hostmaster@mcsun.EU.net, hostmaster@germany.eu.net, kaehler@zpl.dfn.dbp.de, wilhelm@zpl.dfn.dbp.de, staff@sunic.sunet.se, ops@uunet.uu.net, Ruediger Volk From: hostmaster@mcsun.EU.net X-Organisation: EUnet/Alternet X-Phone: +31 20 5924112 Date: Wed, 10 Oct 90 19:50:39 +0100 Sender: dfk@mcsun.EU.net Hi, Please add the following networks to the NSFnet routing database. All networks are in Germany (no problems with east and west anymore :-). All of them have ICS sponsored by NSF according to their admins. Routing is coordinated within RIPE and US connectivity is via EUnet/Alternet with backup via NORDUnet. Thank you for your cooperation Daniel Karrenberg EUnet/Alternet Routing Contact ***** Network Announcement Change Request ***** Inbound Announcements Add/Del to NSFNET or Change --------------------------- --------- Network Number/Name 1stAS# 2ndAS# 3rdAS# 4thAS# A/D/C Country ------------------- ------ ------ ------ ------ --------- ------- 130.149 TUB 701 224 97 A Germany 132.180 UNIBT-LAN 701 224 97 A Germany 132.231 UNI-PASSAU 701 224 97 A Germany 134.100 UNIHH 701 224 97 A Germany 134.107 MPPMU-LAN 701 224 97 A Germany 141.1 DFN-WIN1 (ECRCNET) 701 224 97 A Germany 141.2 DFN-WIN2 (UNI-FFM) 701 224 97 A Germany 192.54.41 EMBNET 701 224 97 A Germany ------------------------------------------------------------------------------ Date: 12 Oct 90 15:47 GMT+0100 From: Martin Wilhelm To: ip-register@MERIT.EDU Cc: hostmaster%germany.eu.dbp.de@RELAY.CS.NET Subject: Request for Handling Sheri, can you please process the following request of Ruediger Volk ? All he institutes mentioned below belong to the academia and are members of the DFN association. Best regards and thanks a lot -martin ------------------------------ cut here --------------------------------- >From rv Mon Oct 8 07:57:35 1990 To: kaehler@zpl.dfn.dbp.de, wilhelm@zpl.dfn.dbp.de Subject: Zulassung zum NSFnet Cc: hostmaster@Germany.EU.net, hostmaster@noc.EU.net Dear Colleagues, please, forward this request to admit the following IP networks to use the NSFnet backbone to MERIT. To enable us and other people involved to follow the procedure and help if anything should hang I suggest to use Cc: hostmaster@noc.EU.net, hostmaster@Informatik.Uni-Dortmund.DE on all transactions. net name net number organization DMSWWU-ETHER 128.176 Univ. Muenster UEGNET 132.252 Univ. Essen UNI-OLDENBURG 134.106 Univ. Oldenburg WICOB 192.55.244 Wissenschaftskolleg Berlin For the first three networks listed the appropriate NOCs will be sending requests for including routing information into the NSFnet routing policy data base in parallel. The appropriate NOCs also will request routing support at MERIT for the following networks, which - to my knowledge - already have NSF's approval; for smoothing the procedure I ask you to confirm these networks to MERIT as well. Net name net number Organization TUB 130.149 TU Berlin UNIBT-LAN 132.180 Univ. Bayreuth UNI-PASSAU 132.231 Uni Passau UNIHH 134.100 Univ. Hamburg MPPMU-LAN 134.107 MPI f. Physik, Munich EMBNET 192.54.41 EMBL Heidelberg DFN-WIN1 (ECRCNET) 141.1 ECRC Munich DFN-WIN2 (UNIFFM-NET) 141.2 Univ. Frankfurt Thanks for your cooperation, Ruediger Volk ---------- End of Copy ---------- ------------------------------------------------------------------------------