Date: Wed, 9 May 90 02:24:22 EDT From: atina!dcsc.umd.edu!gricart (Glenn Ricart) To: atina!pete Malcom, Jorge, etc. Here are the official request forms as I've filled them out. Some of the answers are "necessary," for example, showing number of systems to be connected at least as large as I've put in. Other answers you should please fill in. This is especially true where I have put ***Please fill in***. In addition, if the administrative contact should not be Jorge, please change it. If the technical contact should be someone else, please insert their information. Please mail back to me; I'll double check it and forward it on to the number assigners. You need to think about some name for your network. ARNET (Argentina Network?). Perhaps there is a good acronym in Spanish you'd like to use. The Autonomous System Name is not much used; usually it is based on the network name. for example: ARNET-AS. Any questions, please put *****s around your questions so I'll notice them for sure. Thanks!!! ... Glenn [ NETINFO:INTERNET-NUMBER-TEMPLATE.TXT ] [4/90, LM] This form must be completed as part of the application process for obtaining an Internet Protocol (IP) Network Number. To obtain an Internet number, please provide the following information online, via electronic mail, to HOSTMASTER@NIC.DDN.MIL. If electronic mail is not available to you, please mail hardcopy to: DDN Network Information Center SRI International Room EJ210 333 Ravenswood Avenue Menlo Park, CA 94025 1) If the network will be connected to the Internet, you must provide the name of the sponsoring organization, and the name, title, mailing address, phone number, net mailbox, and NIC Handle (if any) of the contact person (POC) at that organization who has authorized the network connection. This person will serve as the POC for administrative and policy questions about authorization to be a part of the Internet. Examples of such sponsoring organizations are: Defense Communications Agency (DCA), Defense Advanced Research Projects Agency (DARPA), the National Science Foundation (NSF), or similar military or government sponsors. NOTE: If the network will NOT be connected to the Internet, then you do not need to provide this information. 1a. Sponsoring Organization: NSFnet, SURAnet, UMD 1b. Contact name (Lastname, Firstname): Glenn Ricart, Stephen Wolff 1c. Contact title: PI SURAnet, Head DNCRI 1d. Mail Address : Glenn Ricart Computer Science Center University of Maryland College Park, MD 20742-2411 Stephen Wolff DNCRI National Science Foundation 1e. Phone : Ricart: 301-454-8800 until 8/17/90 Ricart: 301-405-7700 after 8/17/90 Wolff: 202-357-9717 1f. Net mailbox : Glenn_Ricart@umail.umd.edu, steve@note.nsf.gov 1g. NIC handle (if known): gr11, ? 2) Provide the name, title, mailing address, phone number, and organization of the administrative POC for the network requesting the number. This is the POC for administrative and policy questions about the network itself. If the network is associated with a research project this POC should be the Principal Investigator of the project. The online mailbox and NIC Handle (if any) of this person should also be included. 2a. NIC handle (if known): 2b. Administrator name (Lastname, Firstname): Amodio, Jorge Marcelo 2c. Administrator title: ****please fill in**** 2d. Mail address : Ministerio de Relaciones Exteriores y Culto, Argentina Reconquista 1088 1er. Piso - Informatica Buenos Aires, Argentina. 2e. Phone : +54-1-313-8082 or fax +54-1-311-1249 2f. Net Mailbox : pete@atina.ar 3) Provide the name, title, mailing address, phone number, and organization of the technical POC. The online mailbox and NIC Handle (if any) of the technical POC should also be included. This is the POC for resolving technical problems associated with the network and for updating information about the network. The technical POC may also be responsible for hosts attached to this network. 3a. NIC handle (if known): 3b. Technical POC name (Lastname, Firstname): same as in #2 3c. Technical POC title: 3d. Mail address : 3e. Phone : 3f. Net Mailbox : 4) Supply the short mnemonic name for the network (up to 12 characters). This is the name that will be used as an identifier in internet name and address tables. 4. Network name: ****please fill in**** (perhaps: ARNET????) 5) Identify the network geographic location and the responsible organization establishing the network. 5a. Geographical address: Buenos Aires, Argentina 5b. Name of Organization: joint project of U.N. Development Program Project ARG 86-026, Ministerio de Relaciones Exteriores, the Argentine Secretariat for Science and Technology, and ENTel, the local PTT 6) Provide a citation to a document that describes the technical aspects of the network. If the document is online, give a pathname suitable for online retrieval. 6. Citation: contact people listed in #1 and #2. 7) Gateway information required: If the network is to be connected to the Internet, answer questions 7a and 7b. 7a) Describe the Gateway that connects the new network to the Internet, and the date it will be operational. The gateway must be either a core gateway supplied and operated by BBN, or a gateway of another Autonomous System. If this gateway is not a core gateway, then an identifiable gateway in this gateway's Autonomous System must exchange routing information with a known core gateway via EGP. A good way to answer this question is to say "Our gateway is supplied by person or company X and does whatever their standard issue gateway does". 7a. Gateway description: via CISCO router to SURAnet 7b) Describe the gateway machine, including: 7b. Hardware: CISCO gateway 7c. Network address: 128.167.x.y 7d. Software: standard CISCO 8) Estimate the number of hosts that will be on the network: 8a. Initially:5 8b. Within one year: 20 8c. Within two years: 50 8d. Within five years: 1000 9) Unless a strong and convincing reason is presented, the network (if it qualifies at all) will be assigned a class C network number. If a class C network number is not acceptable for your purposes state why. (Note: If there are plans for more than a few local networks, and more than 100 hosts, you are strongly urged to consider subnetting. [See RFC 950]) 9. Reason: This network number is intended to be used by a city-wide scientific and higher education network in Buenos Aires; please assign class B 10) Networks are characterized as being either Research, Defense, Government - Non Defense, or Commercial, and the network address space is shared between these three areas. Which type is this network? 10. Type of network: research 11) What is the purpose of the network? 11. Purpose: link scientists in Argentina with their counterparts throughout the world PLEASE ALLOW AT LEAST 10 WORKING DAYS FOR PROCESSING THIS APPLICATION For further information contact the DDN/ARPANET Network Information Center (NIC): Via electronic mail: HOSTMASTER@NIC.DDN.MIL Via telephone: (800) 235-3155 Via postal mail: SRI International DDN Network Information Center 333 Ravenswood Avenue EJ210 Menlo Park, CA 94025 RECOMMENDED READING (available from the NIC) Feinler, E.J.; Jacobsen, O.J.; Stahl, M.K.; Ward, C.A., eds. DDN Protocol Handbook: Menlo Park, CA: SRI International, DDN Network Information Center; 1985 December; NIC 50004 and NIC 50005 and NIC 50006. 2749 p. Garcia-Luna-Aceves, J.J.; Stahl, M.K.; Ward, C.A., eds. Internet Protocol Handbook: The Domain Name System (DNS) Handbook. Menlo Park, CA: SRI International, Network Information Systems Center; 1989 August; 219 p. AD A214 698. Dorio, N.; Johnson, M.; Lederman, S.; Redfield, E.; Ward, C.A., eds. DDN Protocol Implementations and Vendors Guide. Menlo Park, CA: SRI International, DDN Network Information Center; 1989 February; NIC 50002 (February 1989). 386 p. (NIC.DDN.MIL NETINFO:VENDORS-GUIDE.DOC). Braden, R.T.; Postel, J.B. Requirements for Internet Gateways. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1987 June; RFC 1009. 55 p. (NIC.DDN.MIL RFC:RFC1009.TXT). Mogul, J.; Postel, J.B. Internet Standard Subnetting Procedure. Stanford, CA: Stanford University; 1985 August; RFC 950. 18 p. (NIC.DDN.MIL RFC:RFC950.TXT). Postel, J.B. Internet Control Message Protocol. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1981 September; RFC 792. 21 p. (NIC.DDN.MIL RFC:RFC792.TXT). Postel, J.B. Transmission Control Protocol. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1981 September; RFC 793. 85 p. (NIC.DDN.MIL RFC:RFC793.TXT). Postel, J.B. Address Mappings. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1981 September; RFC 796. 7 p. (NIC.DDN.MIL RFC:RFC796.TXT). Obsoletes: IEN 115 (NACC 0968-79) Postel, J.B. User Datagram Protocol. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1980 August 28; RFC 768. 3 p. (NIC.DDN.MIL RFC:RFC768.TXT). Postel, J.B. Internet Protocol. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1981 September; RFC 791. 45 p. (NIC.DDN.MIL RFC:RFC791.TXT). Reynolds, J.K.; Postel, J.B. Assigned Numbers. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1990 March; RFC 1060. 86 p. (NIC.DDN.MIL RFC:RFC1060.TXT). Reynolds, J.K.; Postel, J.B. Official Internet Protocols. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1987 May; RFC 1011. 52 p. (NIC.DDN.MIL RFC:RFC1011.TXT). Romano, S.; Stahl, M.K.; Recker, M. Internet Numbers. Menlo Park, CA: SRI International, DDN Network Information Center; 1989 August; RFC 1117. 109 p. (NIC.DDN.MIL RFC:RFC1117.TXT). [ NETINFO:ASN-TEMPLATE.TXT ] [ 6/89 ] Registering for an Autonomous System Number implies that you plan to implement one or more gateways and use them to connect networks in the DDN-Internet. Please provide us with further details about your plans, and with information about the administrative authority you have for participating in the Internet. It is strongly advised that you follow the development of inter-autonomous systems protocols in the IAB task forces. Send the completed application online to HOSTMASTER@NIC.DDN.MIL. Or, if electronic mail is not available to you, please mail paper copy to: DDN Network Information Center SRI International Room EJ217 333 Ravenswood Avenue Menlo Park, CA 94025 Questions may be addressed to the NIC Hostmaster by electronic mail at the above address, or by phone at (800) 235-3155. To obtain an Autonomous System Number the following information must be provided: 1) The name of the sponsoring organization, and the name, title, mailing address, phone number, net mailbox, and NIC Handle (if any) of the contact person at that organization. This is the contact point for administrative and policy questions about the authorization for this autonomous system to participate in the Internet. NOTE: The key people must have electronic mailboxes and NIC "Handles," unique NIC database identifiers. If you have access to WHOIS, please check to see if you are registered and if so, make sure the information is current. Include only your Handle and any changes (if any) that need to be made in your entry. If you do not have access to WHOIS, or are not registered in the NIC WHOIS database, please provide all the information requested and a NIC Handle will be assigned. Sponsor Organization NSF, SURAnet Name Wolff, Steven; Ricart, Glenn Title Head, DNCRI; V.P. SURA Mail Address National Science Foundation Washington, DC Computer Science Center College Park, MD 20742-2411 Phone Number 202-357-9717 (Wolff); 301-454-8800 (Ricart) Net Mailbox steve@note.nsf.gov (Wolff); Glenn_Ricart@umail.umd.edu (Ricart) NIC Handle gr11 (Ricart) 2) The name, title, mailing address, phone number, and organization of the administrative head of the organization. This is the contact point for administrative and policy questions about the autonomous system. In the case of a research project this should be the Principal Investigator. The online mailbox and NIC Handle (if any) of this person should also be included. Administrator Organization United Nations Development Programme Project ARG 86-026 Name Amodio, Jorge Marcelo Title ****Please fill in**** Mail Address Ministerio de Relaciones Exteriores y Culto Reconquista 1088 1er. Piso - Informatica Buenos Aires, Argentina. Phone Number +54-1-313-8082 Net Mailbox pete@atina.ar NIC Handle 3) The name, title, mailing address, phone number, and organization of the technical contact. The online mailbox and NIC Handle (if any) of the technical contact should also be included. This is the contact point for problems with the autonomous system and for updating information about the autonomous system. Also, the technical contact may be held responsible for the behavior of gateways in this autonomous system. same as above 4) The name of the autonomous system (up to 12 characters). This is the name that will be used in tables and lists associating autonomous systems and numbers. ****Please fill in**** 5) A description of the gateway that implements the inter-autonomous system protocol for interaction with other autonomous systems. Currently the exterior gateway protocol (EGP) is being used for this purpose (RFC 904). This gateway should comply with RFC 1009, Requirements for Internet Gateways. CISCO gateway to SURAnet 6) A description of the gateway hardware, including CPU and interfaces. CISCO 7) A description of the gateway software, including operating system and languages. CISCO 8) The deployment schedule for the autonomous system. (a) initially, (b) within one year, (c) two years, and (d) five years. (a) initially = 5 (b) one year = 20 (c) two years = 50 (d) five years = 1000 9) What networks will be interconnected by these gateways? What are the internet addresses of each gateway? Argentina Science Net ****Please fill in name**** RECOMMENDED READING (available from the NIC) Mills, D.L. Exterior Gateway Protocol Formal Specification. 1984 April; RFC 904. 30 p. (NIC.DDN.MIL RFC:RFC904.TXT). Braden, R.T.; Postel, J.B. Requirements for Internet Gateways. 1987 June; RFC 1009. 55 p. (NIC.DDN.MIL RFC:RFC1009.TXT).