Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!cbosgd!postmap From: postmap@cbosgd.ATT.COM Newsgroups: mod.map Subject: UUCP map for README Message-ID: <3188@cbosgd.ATT.COM> Date: Wed, 24-Dec-86 00:00:41 EST Article-I.D.: cbosgd.3188 Posted: Wed Dec 24 00:00:41 1986 Date-Received: Wed, 24-Dec-86 04:02:54 EST Expires: Sat, 24-Jan-87 00:00:31 EST Sender: root@cbosgd.ATT.COM Lines: 447 Approved: postmap@cbosgd.UUCP : run sh on this file to unbundle echo x - README cat >README <<'!Funky!Stuff!' # The UUCP map is posted to newsgroup mod.map. # # From rn, the map can be easily unpacked with a command such as # 43-46w | (cd ~uucp/uumap ; sh) # or you can use John Quarterman's script to automatically unpack # the files. All files intended as pathalias input being with "u.", thus # pathalias Path.* uumap/u.* # is a useful command to run. (You supply Path.* with local additions.) # # The map is also available on a demand basis at a number of hosts who # have volunteered to make their copy available to the general public ; # details of this access are posted separately in file "network". # # The files are organized by country, using the ISO 3166 3 letter country # code for each country. Each file has a name like u.iso.r1.r2.s, where # "iso" is the country code, r1, r2, etc are regions and subregions # (e.g. states in the USA, provinces in Canada, etc.) and s is a sequence # number (usually 1, but sometimes 2, 3, and up may be provided to keep # individual files down to a reasonable size, thus, u.usa.ca is separated # into two regions: [135] for southern, [246] for northern.) In a few # cases where very large companies post their maps, separate files are used. # *.a.* are AT&T, *.b.* are Bellcore. # # This map can be used to generate mail routes with pathalias. Pathalias # was posted to Usenet in January 1986 and will be posted again as needed # The map is also useful to determine the person to contact when a problem # arises, and to find someone for a new site to connect to. # # Please check the entry for your host (and any neighbors for whom you know # the information and have the time) for correctness and completeness. # Please send corrections and additional information to uucpmap@cbosgd.UUCP # or cbosgd!uucpmap or cbosgd!uucpmap@Berkeley.EDU. # # This map is maintained by a group of volunteers, making up part of the UUCP # Project. These people devote many hours of their own time to helping out # the UUCP community by keeping this map up to date. The volunteers include: # # Rick Adams - rick@seismo.UUCP # USA: Conneticut, Delaware, Maine, Massachusetts, Maryland, # New Hampshire, New Jersey, Rhode Island, Vermont, Virginia, # Washington D.C., West Virginia # # # Gordon Moffett gam@amdahl.UUCP # USA: Michigan, New York, North Dakota, South Dakota, Wisconsin # # # Rayan Zachariassen rayan@utai.UUCP # CANADA: All provinces # # # Bill Blue - bblue@crash.UUCP # USA: Arizona, California (Southern half) # # # Greg Fowler - fowler@hplabs.UUCP # USA: California (Northern half) # # # Karen Summers-Horton - ksh@cbosgd.UUCP # USA: Alaska, Idaho, Montana, Nevada, Oregon, Washington, Wyoming # # # Doug McCallum - dougm@ico.UUCP # USA: Arkansas, Colorado, Iowa, Kansas, Louisiana, Mississippi, # Nebraska, New Mexico, Oklahoma, Texas, Utah # # Piet Beertema - Europe (piet@mcvax.UUCP) # Europe: all countries (unless otherwise noted) # # # Gene Spafford - spaf@gatech.UUCP # USA: Florida, Georgia # # # Bill Welch - zaiaz32!uucpmap@zaiaz.UUCP # USA: Alabama, South Carolina # # # Tim Thompson - tgt@cbosgd.UUCP # USA: Illinois, Indiana, North Carolina, Ohio, # Pennsylvania, Tennessee # # Hokey - hokey@plus5.UUCP # USA: Missouri # # David Herron - david@ukma.UUCP # USA: Kentucky # # # Steve Miller - steve@umd-cs.UUCP # USA: Minnesota # # # Gary Murakami, Kathy Andrews, Larry Auton - ihnp4!attmap # ATT: all logical regions # # # Bob Cunningham - bob@islenet.UUCP # USA: Hawaii # # # Haesoon Cho - hscho@kaist.UUCP # Korea: all regions # # # Tohru Asami - Japan # Japan: all regions # # # Robert Elz (kre@munnari.UUCP), Dave Davey (daved@physiol.su.oz) # Australia: all regions # # # Jim Hand - hand@pyuxp.UUCP # Bell Communicates Research (Bellcore): all sections # # # Mel Pleasant - pleasant@rutgers.UUCP # Singapore: all regions # Indonesia: all regions # New Zealand: all regions # # # Please note that the purpose of this map is to make routers within # UUCP work. The eventual direction is to make the map smaller (through # the use of domains), not larger. As such, sites with lots of local # machines connected together are encouraged to create a few gateway # machines and to make arrangements that these gateways can forward # mail to your local users. We would prefer not to have information # listing the machines on your local area networks, and certainly not # your personal computers and workstations. If you need such information # for local mail delivery, create a supplement in pathalias form which # you do not publish, but which you combine with the published data # when you run pathalias. We also do not want information about machines # which are not on UUCP, that is, which are not reachable with the ! # notation from the main UUCP cluster. # # If you don't have pathalias, it has been posted to mod.sources most # recently in January 1986. If you # don't have access to a mod.sources archive, contact the mod.sources # moderator (currently Rich $alz, cbosgd!mirror!sources-request.) # # The remainder of this file describes the format of the UUCP map data. # It was written July 9, 1985 by Erik E. Fair, and # last updated July 12, 1985 by Mark Horton . # # The entire map is intended to be processed by pathalias, a program that # generates UUCP routes from this data. All lines beginning in `#' are # comment lines to pathalias, however the UUCP Project has defined a set # of these comment lines to have specific format so that a complete # database could be built. # # The generic form of these lines is # # # # # Each host has an entry in the following format. The entry should begin # with the #N line, end with a blank line after the pathalias data, and # not contain any other blank lines, since there are ed, sed, and awk # scripts that use expressions like /^#N $1/,/^$/ for the purpose of # separating the map out into files, each containing one site entry. # # #N UUCP name of site # #S manufacturer machine model; operating system & version # #O organization name # #C contact person's name # #E contact person's electronic mail address # #T contact person's telephone number # #P organization's address # #L latitude / longitude # #R remarks # #U netnews neighbors # #W who last edited the entry ; date edited # # # sitename .domain # sitename remote1(FREQUENCY), remote2(FREQUENCY), # remote3(FREQUENCY) # # Example of a completed entry: # # #N ucbvax # #S DEC VAX-11/750; 4.3 BSD UNIX # #O University of California at Berkeley # #C Robert W. Henry # #E ucbvax!postmaster # #T +1 415 642 1024 # #P 573 Evans Hall, Berkeley, CA 94720 # #L 37 52 29 N / 122 13 44 W # #R This is also UCB-VAX.BERKELEY.EDU [10.2.0.78] on the internet # #U decvax ibmpa ucsfcgl ucbtopaz ucbcad # #W ucbvax!fair (Erik E. Fair); Sat Jun 22 03:35:16 PDT 1985 # # # ucbvax .ucbvax.Berkeley.EDU # ucbvax decvax(DAILY/4), ihnp4(DAILY/2), # sun(POLLED) # # Specific Field Descriptions # # #N system name # # Your system's UUCP name should go here. Either the uname(1) command # from System III or System V UNIX; or the uuname(1) command from Version # 7 UNIX will tell you what UUCP is using for the local UUCP name. # # One of the goals of the UUCP Project is to keep duplicate UUCP host # names from appearing because there exist mailers in the world which # assume that the UUCP name space contains no duplicates (and attempts # UUCP path optimization on that basis), and it's just plain confusing to # have two different sites with the same name. # # At present, the most severe restriction on UUCP names is that the name # must be unique somewhere in the first six characters, because of a poor # software design decision made by AT&T for the System V release of UNIX. # # This does not mean that your site name has to be six characters or less # in length. Just unique within that length. # # With regard to choosing system names, HARRIS'S LAMENT: # # ``All the good ones are taken.'' # # #S machine type; operating system # # This is a quick description of your equipment. Machine type should # be manufacturer and model, and after a semi-colon(;), the operating # system name and version number (if you have it). Some examples: # # DEC PDP-11/70; 2.9 BSD UNIX # DEC PDP-11/45; ULTRIX-11 # DEC VAX-11/780; VMS 4.0 # SUN 2/150; 4.2 BSD UNIX # Pyramid 90x; OSx 2.1 # CoData 3300; Version 7 UniPlus+ # Callan Unistar 200; System V UniPlus+ # IBM PC/XT; Coherent # Intel 386; XENIX 3.0 # CRDS Universe 68; UNOS # # #O organization name # # This should be the full name of your organization, squeezed to fit # inside 80 columns as necessary. Don't be afraid to abbreviate where the # abbreviation would be clear to the entire world (say a famous # institution like MIT or CERN), but beware of duplication (In USC the C # could be either California or Carolina). # # #C contact person # # This should be the full name (or names, separated by commas) of the # person responsible for handling queries from the outside world about # your machine. # # #E contact person's electronic address # # This should be just a machine name, and a user name, like # `ucbvax!fair'. It should not be a full path, since we will be able to # generate a path to the given address from the data you're giving us. # There is no problem with the machine name not being the same as the #N # field (i.e. the contact `lives' on another machine at your site). # # Also, it's a good idea to give a generic address or alias (if your mail # system is capable of providing aliases) like `usenet' or `postmaster', # so that if the contact person leaves the institution or is re-assigned # to other duties, he doesn't keep getting mail about the system. In a # perfect world, people would send notice to the UUCP Project, but in # practice, they don't, so the data does get out of date. If you give a # generic address you can easily change it to point at the appropriate # person. # # Multiple electronic addresses should be separated by commas, and all of # them should be specified in the manner described above. # # #T contact person's telephone number # # Format: + # # Example: # # #T +1 415 642 1024 # # This is the international format for the representation of phone # numbers. The country code for the United States of America (and Canada) # is 1. Other country codes should be listed in your telephone book. # # If you must list an extension (i.e. what to ask the receptionist for, # if not the name of the contact person), list it after the main phone # number with an `x' in front of it to distinguish it from the rest of # the phone number. # # Example: # # #T +1 415 549 3854 x37 # # Multiple phone numbers should be separated by commas, and all of them # should be completely specified as described above to prevent confusion. # # #P organization's address # # This field should be one line filled with whatever else anyone would # need after the contact person's name, and your organization's name # (given in other fields above), to mail you something by paper mail. # # #L latitude and longitude # # This should be in the following format: # # #L DD MM [SS] "N"|"S" / DDD MM [SS] "E"|"W" ["city"] # # Two fields, with optional third. # # First number is Latitude in degrees (NN), minutes (MM), and seconds (SS), # and a N or S to indicate North or South of the Equator. # # A Slash Separator. # # Second number is Longitude in degrees (DDD), minutes (MM), and seconds (SS), # and a E or W to indicate East or West of the Prime Meridian in Greenwich, # England. # # Seconds are optional, but it is worth noting that the more accurate you # are, the more accurate maps we can make of the network (including # blow-ups of various high density areas, like New Jersey, or the San # Francisco Bay Area). # # If you give the coordinates for your city (i.e. without fudging for # where you are relative to that), add the word `city' at the end of the # end of the specification, to indicate that. If you know where you are # relative to a given coordinate for which you have longitude and # latitude data, then the following fudge factors can be useful: # # 1 degree = 69.2 miles = 111 kilometers # 1 minute = 1.15 miles = 1.86 kilometers # 1 second = 102 feet = 30.9 meters # # For LONGITUDE, multiply the above numbers by the cosine of your # latitude. For instance, at latitude 35 degrees, a degree of # longitude is 69.2*0.819 = 56.7 miles; at latitude 40 degrees, # it is 69.2*0.766 = 53.0 miles. If you don't see why the measure # of longitude depends on your latitude, just think of a globe, with # all those N-S meridians of longitude converging on the poles. # You don't do this cosine multiplication for LATITUDE. # # Here is a short cosine table in case you don't have a trig calculator # handy. (But you can always write a short program in C. The cosine # function in bc(1) doesn't seem to work as documented.) # deg cos deg cos deg cos deg cos deg cos deg cos # 0 1.000 5 0.996 10 0.985 15 0.966 20 0.940 25 0.906 # 30 0.866 35 0.819 40 0.766 45 0.707 50 0.643 55 0.574 # 60 0.500 65 0.423 70 0.342 75 0.259 80 0.174 85 0.087 # # The Prime Meridian is through Greenwich, England, and longitudes run # from 180 degrees West of Greenwich to 180 East. Latitudes run from # 90 degrees North of the Equator to 90 degrees South. # # #R remarks # # This is for one line of comment. As noted before, all lines beginning # with a `#' character are comment lines, so if you need more than one # line to tell us something about your site, do so between the end of the # map data (the #?\t fields) and the pathalias data. # # #U netnews neighbors # # The USENET is the network that moves netnews around, specifically, # mod.announce. If you send mod.announce to any of your UUCP neighbors, # list their names here, delimited by spaces. Example: # # #U ihnp4 decvax mcvax seismo # # Since some places have lots of USENET neighbors, continuation lines # should be just another #U and more site names. # # #W who last edited the entry and when # # This field should contain an email address, a name in parentheses, # followed by a semi-colon, and the output of the date program. # Example: # # #W ucbvax!fair (Erik E. Fair); Sat Jun 22 03:35:16 PDT 1985 # # The same rules for email address that apply in the contact's email # address apply here also. (i.e. only one system name, and user name). # It is intended that this field be used for automatic ageing of the # map entries so that we can do more automated checking and updating # of the entire map. See getdate(3) from the netnews source for other # acceptable date formats. # # PATHALIAS DATA (or, documenting your UUCP connections & frequency of use) # # The DEMAND, DAILY, etc., entries represent imaginary connect costs (see # below) used by pathalias to calculate lowest cost paths. The cost # breakdown is: # # LOCAL 25 local area network # DEDICATED 95 high speed dedicated # DIRECT 200 local call # DEMAND 300 normal call (long distance, anytime) # HOURLY 500 hourly poll # EVENING 1800 time restricted call # DAILY 5000 daily poll # WEEKLY 30000 irregular poll # DEAD a very high number - not usable path # # Additionally, HIGH and LOW (used like DAILY+HIGH) are -5 and +5 # respectively, for baud-rate or quality bonuses/penalties. Arithmetic # expressions can be used, however, you should be aware that the results # are often counter-intuitive (e.g. (DAILY*4) means every 4 days, not 4 # times a day). This is because the numbers represent "cost of connection" # rather than "frequency of connection." # # The numbers are intended to represent cost of transferring mail over # the link, measured very rougly in elapsed time, which seems to be # far more important than baud rates for this type of # traffic. There is an assumed high overhead for each hop; thus, # HOURLY is far more than DAILY/24. # # There are a few other cost names that sometimes appear in the map. # Some are synonyms for the preferred names above (e.g. POLLED is assumed # to mean overnight and is taken to be the same as DAILY), some are # obsolete (e.g. the letters A through F, which are letter grades for # connections.) It is not acceptable to make up new names or spellings # (pathalias gets very upset when people do that...). # # LOCAL AREA NETWORKS # # We do not want local area network information in the published map. # If you want to put your LAN in your local Path.* files, read about # the LAN syntax in the pathalias.1 manual page. # # WHAT TO DO WITH THIS STUFF # # Once you have finished constructing your pathalias entry, mail it off # to {ucbvax,ihnp4,akgua,seismo}!cbosgd!uucpmap, which will be sent to # the appropriate regional map coordinator. They maintain assigned geographic # sections of the map, and the entire map is posted on a rolling basis in # the USENET newsgroups mod.map.uucp over the course of a month (at the # end of the month they start over). # # Questions or comments about this specification should also be directed at # cbosgd!uucpmap. # !Funky!Stuff! : End of shell archive