SYRACUSE UNIVERSITY INTERNET STANDARDS May 16, 1991 - JMW ========================================================================= Abstract -------- A concise listing of the standards for the Syracuse University Internet. Running an internet requires some agreement between the administrators of the individual computers. This document lists the conventions adopted for Syracuse University's internet. It includes only a small amount of explanation. ========================================================================= Direct questions about these rules to John Wobus, Computing & Network Services, Room 218, Machinery Hall, x4324, Internet: jmwobus@suvm.syr.edu, BITNET: JMWOBUS@SUVM. ========================================================================= Rules: ------ (I) Official Internet Names: (1) (preferred method): Names consist of three parts, a short name (e.g. "sugaree") followed by the string "syr.edu" (thus sugaree's Official Internet Name is "sugaree.syr.edu"). The short part of the name must be unique among all short names on campus. A short name is chosen by Computing & Network Services, but administrators of systems who want a specific name can request it. Exception: there is one computer on campus with the two-part name "syr.edu". (2) (optional method, retained so older computers need not change names): they include a department qualifier and a Syracuse University-wide set of qualifiers. For example, Academic Computing Services' computer known as "SUVM" has the internet name "SUVM.ACS.SYR.EDU" where ".ACS" is an official qualifier given to Academic Computing Services and ".SYR.EDU" are the official qualifiers for Syracuse University. Department qualifiers are chosen by negotiation between the department and Computing & Network Services (to make sure each qualifier is unique). The name of the computer must be unique within the department. Names unique within the University have the option of being accessible throughout the University without qualifiers. We suggest that if you have a multi-user system or file server, that you check the name for uniqueness with Computing & Network Services so you can do this. Each department must have a designated administrator who can apply the rules of this document. (II) Internet addresses (a.k.a. Internet Numbers): the full number (e.g. 128.230.1.49) must be unique, so the last number ("49" in the above example) must be unique within the particular subnet your computer is attached to. Thus the address must be assigned by an administrator for the subnet. This last number must be in range 1-126; all others are reserved. Each subnet must have a designated administrator who can apply the rules of this document. (III) Registration of names: Report any names you want available throughout the University or off campus to nisc@suvm.acs.syr.edu or to John Wobus at x4324. (IV) Access to name-to-address mappings: (1) Using table lookup: Computing & Network Services maintains tables of name-to-address mappings both for local computers and many computers throughout the world. These are accessible by ftp on syr.edu under the username "anonymous" (the password is anything you wish). The useful files are: networks/config/localhosts.txt table of SU computers, "SRI-NIC" format. networks/config/locahosts table of SU computers, "UNIX" format. networks/config/hosts.txt table of computers around the world, "SRI-NIC" format. This is from SRI-NIC. networks/config/unix_hosts table of SU computers plus computers around the world in "UNIX" format. Maintainers of UNIX systems can simply copy this to their own "/etc/hosts". Computing & Network Services usually updates these tables on Tuesday. Thus Monday is a good day to register names and Wednesday is a good day to get the tables. (2) Using the network's distributed database of names ("name domain service"): - If your system uses BOOTP to reach CNS's BOOTP server, then it will automatically use a list of name servers listed in the server, and kept up-to-date by CNS. - If your system runs just a resolver (i.e., does not run its own nameserver) and does not use our BOOTP-server's list of name servers then configure a list of at least three nameservers (assuming your software allows this). Pick them in the following order: (1) Pick nameservers on your own LAN. (2) Pick other nameservers in your own building. (3) Pick other nameservers on campus. Note: it is NOT necessary to include a nameserver in each category: three nameservers on your own LAN is fine if you have such. Ideally, your list will start with the nameserver that gives you the best performance, then lists nameservers which are most likely to be up and reachable even when the first nameserver is not. - If you have a caching-only server, use the current list of root domain servers (see below). If the caching-only server will allow you to configure a "hint" for hosts ending with "syr.edu", we recommend configuring such hints pointing to lurch and to syr.edu (128.230.1.49). - If you wish to run a server as a secondary for the "syr.edu" domain, contact Computing & Network Services. - Administering your own subdomain: this is possible, but is not simple: you should read RFCs 1032, 1033, 1034, and 1035 as well as the BSD Nameserver Operations Guide. Then contact Computing & Network Services. Notes on Name Servers: Name server located in the Center for Science and Technology, provided by CNS for use by resolvers: 128.230.31.2 zookeeper.cns.syr.edu Name servers located in Machinery Hall, provided by CNS for use by resolvers: 128.230.12.5 lurch.cns.syr.edu 128.230.1.55 rodan.acs.syr.edu 128.230.1.49 icarus.cns.syr.edu Do not use either of the following: 128.230.1.47 suvm.acs.syr.edu 192.35.82.2 n2ngw.nyser.net Root domain name servers (for use by caching only servers): 192.67.67.53 ns.nic.ddn.mil 26.3.0.103 a.isi.edu 128.9.0.107 a.isi.edu 192.5.25.82 aos.brl.mil 128.20.1.2 aos.brl.mil 26.1.0.13 gunter-adam.af.mil 192.33.4.12 c.nyser.net 128.8.10.90 terp.umd.edu 192.52.195.10 ns.nasa.gov (V) Trailers: we do NOT use trailers on SU Internet. Any system with trailers as an option must have them turned off. Any system with trailers as a default must have the default overridden. (Note that trailers are a great source of problems that only arise when you start shipping lots of data.) (VI) Broadcast Addresses: we use different broadcast addresses on different subnets. Contact the administrator of the subnet to find out its broadcast address. Note: this is the case because we are converting subnets from the old Berkeley Unix broadcast addresses to the Internet standard form. The Internet standard is that nodes should accept broadcast addresses of the form 128.230.255.255, 128.230.X.255 (where X is your subnet number) or 255.255.255.255. Nodes should send either 128.230.X.255 or 255.255.255.255. Nodes sending either of these can be mixed on the same subnet: all will work as long as all nodes accept both. The older version which is being phased out was 128.230.X.0. Your subnet either uses the new type broadcast addresses or the old type. (VII) Subnet masks: we have a network number for use throughout the campus of 128.230. With this number, we use a subnet mask of (hex)ffffff00 (a.k.a. 255.255.255.0). Computers attached to some of the "128.230" networks can function without a subnet mask. All Ethernets attached directly to FASTNET gateways can support such attachment. See "Routing" below for more on this. (VIII) Routing to assure connectivity. These rules assure that any node on any subnet of 128.230 can route to nodes on any other subnet of 128.230, to any network known by NYSERNet, and to any network known by the "core" of the Internet. Network 128.230 is "advertised" around NYSERNet and around the "core" so that other sites can route to 128.230: (1) Subnets of 128.230: - must have a "designated default gateway" (such a gateway must follow all the rules for gateways listed as (2)). - must either be designated a "proxy ARP subnet" or not (so that all gateways and end nodes on it can be consistently configured). Our general policy is to designate a subnet as not proxy ARP unless it is necessary. - must either be designated a "RIP subnet" or not. Our general policy is to designate a subnet as not RIP unless it is necessary. (2) Gateways between 128.230 subnets: - must use the true SU Internet subnet mask. - must use the proper SU Internet broadcast address for each attached subnet. - must process received RIP from any attached RIP subnet. - must send RIP to any attached RIP subnets. - must provide Proxy ARP service to any attached Proxy ARP subnets. - must have a static route to the designated default gateway on the subnet that connects it to the world. (3) End nodes on 128.230 subnets: - must have a default route to the subnet's designated default gateway. - if NOT on a Proxy ARP subnet, then must use the true SU Internet subnet mask; if it IS on a Proxy ARP subnet, we recommend that it use the true SU Internet subnet mask, but this is not necessary. - if on a RIP subnet and using that proper SU Internet subnet mask and using that subnet's true broadcast address, then may process received RIP. This has some advantage if and only if it is on a subnet with more than one gateway. (4) Gateways between 128.230 and other networks: - must follow the rules for end nodes (except that the NYSERNet gateway's default route points away from 128.230). - must either be on a RIP subnet and send RIP or another gateway on the subnet should have a static route to it and should send RIP for it. Notes on routing: Where there are choices above, the first choice is the choice we are eventually striving for--the other choices are available because not all systems have the necessary software for the first choice. If you have trouble with the first choice and want to try something else, make sure you change all necessary options to adhere to one of the above-listed alternates. Some system software doesn't handle all these parameters independently. For class-B networks in general, the default network mask is (hex)ffff0000 or 255.255.0.0. Most systems will use this by default. The true SU Internet subnet mask is (hex)ffffff00 or 255.255.255.0. The true SU Internet broadcast address is 128.230.x.0 where x is the subnet number. Most systems will use something else by default. The FASTNET gateways presently have default routes pointed towards NYSERGATE (for gateways that don't share a network with NYSERGATE, they have a route to the FASTNET gateway that is one step closer). Following is a list of Computing & Network Services subnets of 128.230 along with their "Proxy ARP" and "RIP" designations: 128.230.001 Mach Mail Net NoPA RIP 128.230.002 Slocum WS Net NoPA RIP 128.230.004 Mach WS Net 2 NoPA RIP 128.230.005 Camp Rptd Ethnet NoPA RIP 128.230.006 Link WS Net NoPA RIP 128.230.009 Lyman WS Net NoPA RIP 128.230.010 Camp Appletalk BB NoPA RIP 128.230.012 Camp Fiber Backbone NoPA RIP 128.230.013 Carnegie WS Net NoPA RIP 128.230.015 Bird WS/Mail Net PA RIP 128.230.016 ISR/MH Net NoPA RIP 128.230.018 Mach Mail Net 2 NoPA RIP 128.230.019 Mach WS Net NoPA RIP 128.230.020 Camp Kimmel/MH Net NoPA RIP 128.230.024 Heroy WS/Mail Net PA RIP 128.230.027 Physics Mail Net NoPA RIP 128.230.029 Kimmel Net NoPA RIP 128.230.030 CST WS Net NoPA RIP 128.230.031 CST Mail Net NoPA RIP 128.230.032 CST WS/Mail Net NoPA RIP 128.230.033 CST WS Net NoPA RIP 128.230.034 Hunt WS/Mail Net NoPA RIP 128.230.035 Camp WS Net NoPA RIP 128.230.037 Camp Rptd Ethnet NoPA RIP 128.230.038 Hinds Mail Net NoPA RIP 128.230.039 CST WS net NoPA RIP 128.230.046 Maxwell WS Net NoPA RIP 128.230.047 Archbold WS Net NoPA RIP 128.230.048 Shaffer/BRL/SIMS WS NoPA RIP 128.230.049 Schine Link NoPA RIP 128.230.050 Schine WS Net NoPA RIP 128.230.053 WS Net. NoPA RIP (IX) Trouble Reporting: report network problems to x4801, NISC@SUVM on BITNET, or nisc@suvm.acs.syr.edu on the Internet. =========================================================================