| Revision as of 17:01, 30 August 2005 editBarberio (talk | contribs)Extended confirmed users4,269 edits Path map from 1984← Previous edit | Revision as of 23:00, 30 August 2005 edit undo65.171.97.57 (talk)No edit summaryNext edit → | ||
| Line 10: | Line 10: | ||
| The UUCP protocol was used to forward material between sites on a hop-by-hop basis. Addressing on UUCPNET was achieved by specifying a route as a list of intermediate host names separated by ]s, or '']s'', hence the term '''bang path'''. Thus, for example, the path ...!bigsite!foovax!barbox!me directs people to route their mail to machine ''bigsite'' (presumably a well-known location accessible to everybody) and from there through the machine ''foovax'' to the account of user ''me'' on ''barbox''. | The UUCP protocol was used to forward material between sites on a hop-by-hop basis. Addressing on UUCPNET was achieved by specifying a route as a list of intermediate host names separated by ]s, or '']s'', hence the term '''bang path'''. Thus, for example, the path ...!bigsite!foovax!barbox!me directs people to route their mail to machine ''bigsite'' (presumably a well-known location accessible to everybody) and from there through the machine ''foovax'' to the account of user ''me'' on ''barbox''. | ||
| People often published compound bang addresses using the { } convention (see ]) to give paths from several big machines, in the hopes that one's correspondent might be able to get mail to one of them reliably (example: ...!{seismo, ut-sally, ihnp4}!rice!beta!gamma!me). Bang paths of 8 to 10 hops were not uncommon in 1981. Late-night dial-up UUCP links would cause week-long transmission times. Bang paths were often selected by both transmission time and reliability, as messages would often get lost. Occasionaly, Usenet maps would be published to show the | People often published compound bang addresses using the { } convention (see ]) to give paths from several big machines, in the hopes that one's correspondent might be able to get mail to one of them reliably (example: ...!{seismo, ut-sally, ihnp4}!rice!beta!gamma!me). Bang paths of 8 to 10 hops were not uncommon in 1981. Late-night dial-up UUCP links would cause week-long transmission times. Bang paths were often selected by both transmission time and reliability, as messages would often get lost. Occasionaly, Usenet maps would be published to show the over-all scope of the UUCPNET. | ||
| ] traffic was originally carried over the UUCPNET, and bang paths are still in use within the Usenet message format ''Path'' headers. They now have only an informational purpose, and are not used for routing, although they can be used to ensure that loops do not occur. In general, this form of ] has now been superseded by the ] "] notation". | ] traffic was originally carried over the UUCPNET, and bang paths are still in use within the Usenet message format ''Path'' headers. They now have only an informational purpose, and are not used for routing, although they can be used to ensure that loops do not occur. In general, this form of ] has now been superseded by the ] "] notation". | ||
Revision as of 23:00, 30 August 2005
| Internet protocol suite |
|---|
| Application layer |
| Transport layer |
| Internet layer |
| Link layer |
UUCP stands for Unix to Unix Copy Protocol, and is a computer program and protocol allowing remote execution of commands and transfer of files, email and netnews between Unix computers not connected to the Internet proper. The UUCP package consists of several programs including uucp, uuxqt (front ends for remote copy and execution), uucico (communication program), uustat, and uuname. Today, it is rarely used for modem communications, but is occasionally used over TCP/IP.
Before the widespread availability of universal connectivity through the Internet, computers were only connected by smaller networks, or point-to-point links. UUCP allowed message switching between machines, rather like Fidonet (which was modeled on UUCP and very common on DOS systems).
The UUCPNET was the name for the totality of the informal network of computers connected through UUCP.
The UUCP protocol was used to forward material between sites on a hop-by-hop basis. Addressing on UUCPNET was achieved by specifying a route as a list of intermediate host names separated by exclamation marks, or bangs, hence the term bang path. Thus, for example, the path ...!bigsite!foovax!barbox!me directs people to route their mail to machine bigsite (presumably a well-known location accessible to everybody) and from there through the machine foovax to the account of user me on barbox.
People often published compound bang addresses using the { } convention (see glob) to give paths from several big machines, in the hopes that one's correspondent might be able to get mail to one of them reliably (example: ...!{seismo, ut-sally, ihnp4}!rice!beta!gamma!me). Bang paths of 8 to 10 hops were not uncommon in 1981. Late-night dial-up UUCP links would cause week-long transmission times. Bang paths were often selected by both transmission time and reliability, as messages would often get lost. Occasionaly, Usenet maps would be published to show the over-all scope of the UUCPNET.
Usenet traffic was originally carried over the UUCPNET, and bang paths are still in use within the Usenet message format Path headers. They now have only an informational purpose, and are not used for routing, although they can be used to ensure that loops do not occur. In general, this form of e-mail address has now been superseded by the SMTP "@ notation".
See also
External links
- Mark Horton (1986). RFC 976: UUCP Mail Interchange Format Standard. Internet Engineering Task Force Requests for Comment.
- UUCP Internals Frequently Asked Questions
- Taylor UUCP - GPL licensed UUCP package
- Taylor UUCP Documentation - it provides useful info about general UUCP and UUCP protocols.
- Usenet Logical Map, July 24, 1984