Canadian Map Tutorial --------------------- [This is an older document put together by path@cs.utoronto.ca to guide those constructing a map entry for the first time or encountering a need for a more complex newer map entry. Also see the README that comes with the UUCP maps, and the much newer Canadian UUCP Map Coordinator's FAQ.] Thanks (and apologies for continued use) to those who provided some perfect examples in years gone by. Introduction The UUCP map is a database of information about hosts that communicate by UUCP, and today often by other methods. The primary purpose is to document possible routes for mail. When the "pathalias" program is run on the UUCP map data, it outputs the lowest cost path from a specified host (usually your own) to all other hosts listed in the map. Most ``smart'' mail programs on the UUCP network can use the pathalias output to route mail without the user having to specify explicit routes. The UUCP map is posted periodically to the newsgroup comp.mail.maps and now is about 14 Mb in size. The Canadian portion of the UUCP map is also cross-posted to can.uucp.maps. It's about 8 Mb in size. All Canadian sites running pathalias should try to get at least the latter. The pathalias program and mailer software that can use the pathalias database for routing are available from various archive sites. [If you're willing to distribute the UUCP map, pathalias and/or mail software to people in your area via uucp, anon. ftp or mail software, please mail path@cs.toronto.edu. I'd like to build up a list of map archive sites.] Registering your site To register a site in the UUCP map, fill out an entry in the format described below, and mail it to the following address: Canadian sites should mail their map entry to: path@cs.utoronto.ca or path@cs.toronto.edu or utcsri!path When constructing a new map entry, it is often helpful to start from an existing entry taken from the posted maps. If this is the first map entry you are writing, you may also want to ask someone who has written a map entry before to proof-read your entry. When you need to update an existing entry, start from the previous entry in the posted maps, since the map coordinators may have revised or corrected your entry. Format of a map entry --------------------- The form of a UUCP map entry is: #N uucpname[, uucpnames, domains] #F optional line, Internet Forwarder #S manufacturer machine model; [operating system & version] #O organization name #C contact person(s) name(s) (comma separated if more than one) #E contact person(s) electronic mail address(es), comma separated. #T contact person(s) telephone number(s), comma separated #P organization's paper mail address, please include your province #L latitude / longitude ["city"] #R optional line, a one line remark #U optional line, netnews neighbors separated by spaces [more than #U one #U line is ok if you have more neighbours than will fit on #U one line] #W email-address (person who last edited the entry); date last edited # # additional comments go here. As many lines as you want. # Equivalencing your site to a domain name is optional -- if # you want to register a domain name, do so with the # proper authorities running the domain BEFORE using the # domain in the maps. # # uucpname .domain(LOCAL) uucpname remote1(FREQUENCY), remote2(FREQUENCY), remote3(FREQUENCY) The lines beginning with '#' are comments to pathalias, which will ignore them. Lines beginning with '#' immediately followed by an upper case letter have specific formats and are used by other programs that process map data. Lines beginning with '#' immediately followed by a space or tab are comments that are ignored. The #[letter] must be followed by a TAB character (ASCII code 011 octal, often represented as \t in C programs and some documents) -- do *not* use spaces instead. Keep all lines to under 80 columns -- the maps have to be sent through machines that can be actively hostile to long lines. Examples of map entries: [These examples were taken from the maps in October 1990. They do not reflect the current status of those sites] The first example, for site "iceman", is a simple map entry -- it has a single UUCP connection to another site, "alberta". #N iceman #S AT&T UNIX-pc 3B1; SYSV Rel. 2 Ver. 3.51 #O private site #C Michel Adam #E iceman!michel #T +1 403 920 8792 #P 301 Ptarmigan, 42 Con Rd., Yellowknife, N.W.T., Canada X1A 1X6 #L 62 27 43 N / 114 26 04 W #R #U #W iceman!michel (Michel Adam); Wed Mar 7 00:31:25 MST 1990 # iceman alberta(DAILY) Site "tmsoft", the second example, is a slightly more complicated map entry. It has a lot of UUCP feeds for both mail and news and more than one modem, and therefore prioritizes its links. #N tmsoft #S National Semiconductor ICM3216; Unix System 5r2 #O TM Software Associates Inc., Toronto #C Dave Mason #E ryescs!mason, tmsoft!mason #T +1 416 463 7095 #P 92 Gough Ave, Toronto, Ontario, Canada M4K 3N8 #L 43 39 20 N / 79 23 15 W #R Compiler & Operating System Development #U torsqnt #U beaudin itcyyz masnet #U yrloc becker telly #W tmsoft!mason (Dave Mason); Fri Nov 09 19:18:31 EDT 1990 # # System Software development & Consulting, Teaching # # We archive comp.sources.{unix,misc,x,games} # # in the following: WP - we poll, TP - they poll, BP - bidirectional poll # LOW=1200bps, HIGH=19200bps Telebit tmsoft attcan(DIRECT+HIGH), # BP - mail aucs(WEEKLY+LOW), # WP - mail, news: atl,ns,hfx becker(DIRECT+HIGH), # BP - mail, news: inet,ut,uw,ddn,pubnet,biz beaudin(DIRECT+HIGH), # BP - mail, full news compugen(DIRECT+HIGH), # BP - mail compus(DIRECT), # BP - mail eci386(DIRECT), # BP - mail gate(DIRECT), # BP - mail grandison(POLLED), # TP - mail, some news itcyyz(DIRECT+HIGH), # BP - mail, full news lsimages(POLLED), # TP - mail, some news lsuc(DIRECT+HIGH), # BP - mail, news: ont,tor magsta(DIRECT), # WP - mail masnet(POLLED), # TP - mail, 1/2 news, CanConfMail mnetor(DIRECT+FAST-1), # BP - mail, full news bidirectional moore(DIRECT+HIGH), # WP - mail ontmoh(DIRECT+HIGH), # BP - mail, minimal news psican(DIRECT), # BP - mail roboha(DIRECT), # BP - mail, news: can,ont,tor ryescs(DIRECT), # TP - mail, most news (coming soon) stjoes(DIRECT), # WP - mail teecs(DIRECT+HIGH), # BP - mail telly(DIRECT+HIGH), # BP - mail, news: can,ont,tor torsqnt(DIRECT+HIGH), # BP - mail, full news bidirectional utcsri(DIRECT+HIGH), # WP - mail utgpu(DEAD), # retrenchment utzoo(DIRECT+HIGH), # BP - mail yrloc(DIRECT+HIGH), # TP - mail yunexus(DIRECT+HIGH), # WP - mail yzrnur(POLLED), # TP - mail ziebmef(DIRECT) # BP - mail back from the dead...?!? The third example is of a site that has associated domain names in different domains, several long distance feeds and connects via a Local Area Network to several other sites. See the pathalias manual page for details about Local Area Networks. #N watmath #S DEC VAX-11/785; 4.3 BSD UNIX #O Math Faculty Computing Facility, University of Waterloo #C Bill Ince #E watmath!postmaster #T +1 519 885 1211 x2721 #P 200 University Avenue, Waterloo, Ontario, Canada N2L 3G1 #L 43 27 20 N / 80 32 37 W #R Main U. of Waterloo mail/news/admin site #U alberta att dalcs decvax focsys isishq iuvax #U looking lsuc mks onfcanim ncrwat ria softart #U ubc-cs utgpu uunet xenitec #W watmath!gamiddleton (Guy Middleton); Fri Nov 16 15:19:12 EST 1990 # watmath .uwaterloo.ca, .waterloo.edu watmath = watmath.uwaterloo.ca, watmath.waterloo.edu watmath = math.uwaterloo.ca, math.waterloo.edu watmath = uwaterloo.ca, waterloo.edu watmath # Local phone calls arundel(WEEKLY), focsys(EVENING), isishq(EVENING), looking(HOURLY), mgvax(WEEKLY), mks(HOURLY), ncrwat(EVENING), softart(EVENING), stoga(EVENING), tslwat(EVENING), watcomsys(EVENING), watcsc(DIRECT), xenitec(EVENING), # Ontario LD lsuc(EVENING), utzoo(DEAD), # Canada LD onfcanim(EVENING), # USA LD decvax(DAILY), linus(DAILY+LOW), plus5(DAILY), # Ontario Internet ria(HOURLY), utai(HOURLY), # Canada Internet alberta(HOURLY), calgary(HOURLY), dalcs(HOURLY), (DEMAND), # USA Internet (DEAD), uunet(HOURLY/2), # Logical U of Waterloo LAN, well-known nodes only WaterlooNet = { watmath, maytag, # uucp hub wataco, # Arts computing watacs, watlager, watmad, watimp, watale, # General engineering research watbun, # Software Development watcgl, watpix, # Computer Graphics R&D watcsg, # R&D watdcs, # Academic computing watdragon, watyew, # AI water, # Research watmsg, # Research in distributed systems watrose, watshine, orchid, # Teaching watsol, # New OED watstat, # Statistics watserv1, # Computing Services watvlsi, ccng # VLSI and CCNG depts. }!(LOCAL) Note that a large site listing internal hosts like this is frowned on. In general, internal hosts should be mentioned in the UUCP map only if they don't use an organizational domain name for outgoing mail. Any host that gateways between the UUCP network at large, and your organization, should have its own UUCP map entry. Each field in the map entry is documented in detail in the README file posted periodically to comp.mail.maps and this newsgroup. The following notes are additional clarifications or suggestions. The machine name must be unique within the first six characters. It may only have lower case alphanumerics or hyphens in it. You may not use a name that someone else has already registered with their map entry. Check the present set of maps in comp.mail.maps for the current set of names in use (grep '^#N' u.* should find them all), else ask your regional map coordinator. [We hope to eventually have an automatic mail server in place for answering questions like "is name foobar taken?"] Choose a name that you would like to stay with for a long while -- changing the name of the machine people associate you with can be very inconvenient for your e-mail correspondents and for you. Remember that people will use the name in conversation. Some hints for choosing a machine name [adapted from the Internet RFC1178 by Don Libes] Don't overload other terms already in common use - it confuses people. Don't choose a name after a project unique to that machine - the machine may get used for another project. Don't use your own name. -- it confuses people. Avoid alternate spellings or hard-to-pronounce words. -- you'd be surprised how much mail bounces because of such names. Avoid names very similar to other names -- it confuses people. Don't use antagonistic or otherwise embarrassing names. Don't use digits at the beginning of the name - it confuses programs. Don't use non-alphanumeric characters in a name - it confuses programs. Use words/names that are rarely used - uniqueness is nice. Use theme names - if you're naming more than one machine. Use real words - people can remember and spell them easily. There is always room for an exception. Remember to provide a trailing semi-colon on the operating system field (#S) even if you do not provide an operating system. In the telephone field (#T) do not put spaces between the 'x' and extension number, if any. Do not put dashes, parenthesis, or any other characters in the phone number. The format is standard for international phone numbers, e.g., +1 800 555 1212, or +1 800 555 1212 x9999 Please do provide your latitude and longitude as accurately as you can. It is useful for maps of the network, especially in cities with a lot of UUCP sites. If your lat/long are not precise, then add the word "city" (not the name of the city) to the end of the line. eg. #L 43 27 N / 80 29 W city Remember to add your province in the address in the #P field. Don't put parentheses around it. The accepted two letter or three letter abbreviation is fine, or the full name. We sort map entries by province. A typical #P entry is #P building, street, town/city, province, country, postal code When you submit an updated map entry, remember to update the date on the #W field. The accepted date format is the output of the Unix date(1) command. Specifying the date in GMT is a good way to avoid ambiguity in time zone names. (You can instead put your local time zone in a comment or remark, specifying how far ahead of behind GMT it is.) The date must be within the last 30 days. Map entries with dates older than that will be rejected on submission. Pathalias can deal with mail routes specified with !, %, : and @ as routing characters. However, UUCP maps entries must only use ! as a routing character. This makes the output of pathalias unambiguous to all mailers. ---- This file is posted to can.uucp periodically. Questions or comments about this document should also be directed at path@cs.utoronto.ca (utcsri!path). Please mention the Header below when sending a question or comment. Last Minor Update: Mon Jul 22 08:02:48 EDT 1996 $Header: /homes/neat/car/path/doc/RCS/TUTORIAL,v 1.9 91/01/10 06:59:06 path Exp $