|
|
1.1 ! root 1: From research!mtune!rutgers!SH.CS.NET!cic Wed Sep 30 03:04:56 1987 ! 2: Received: by mtune.ATT.COM (smail2.5) ! 3: id AA01141; 30 Sep 87 03:04:56 EDT (Wed) ! 4: Received: by RUTGERS.EDU (5.54/1.14) ! 5: id AA19189; Tue, 29 Sep 87 18:16:00 EDT ! 6: Message-Id: <[email protected]> ! 7: Received: by SH.CS.NET id ad10308; 29 Sep 87 15:25 EDT ! 8: Date: Tue, 29 Sep 87 14:24:44 EDT ! 9: Subject: adr-3 Other Networks ! 10: Reply-To: rutgers!SH.CS.NET!cic ! 11: From: CSNET INFO SERVER <rutgers!SH.CS.NET!info> ! 12: To: [email protected] ! 13: ! 14: Request: info ! 15: Topic: adr-3 ! 16: Document Updated: 26 May 87 ! 17: Subject: Addresses for the Internet, CSNET and Other Networks ! 18: ============================================================================== ! 19: CSNET Coordination and Information Center (CIC) Hotline: 617/497-2777 ! 20: 10 Moulton Street Email: [email protected] ! 21: Cambridge, MA 02238 Info-Server requests to: [email protected] ! 22: ============================================================================== ! 23: ! 24: ADDRESSES FOR THE INTERNET, CSNET AND OTHER NETWORKS Line 1 ! 25: ! 26: Contents ! 27: Line ! 28: INTRODUCTION............................................ 13 ! 29: RFC822 ADDRESSES AND DOMAINS............................ 32 ! 30: RFC733 ADDRESSES........................................ 94 ! 31: SENDING MAIL ON AN "822" (DOMAIN-STYLE) HOST ........... 109 ! 32: SENDING MAIL ON A "733" (NON-DOMAIN) HOST.............. 224 ! 33: REFERENCES.............................................. 276 ! 34: ! 35: ! 36: INTRODUCTION ! 37: ! 38: Here is a summary of the current information at the CSNET Coordination ! 39: and Information Center (CIC) about addresses for CSNET PhoneNet users. ! 40: Networks covered are DARPA Internet (CSNET X25Net, Arpanet, Milnet, ! 41: etc.), CSNET PhoneNet, Australia, Bell Labs, BITNET, Canada, DEC ENET, ! 42: France, MAILNET, UUCP, UK, and Xerox. ! 43: ! 44: Please note that the use of the DARPA Internet is restricted to ! 45: authorized individuals and is regulated by the Defense Communications ! 46: Agency. (See info-4 in REFERENCES). ! 47: ! 48: Send corrections and additions to the CIC Service Host (which is on the ! 49: Internet): ! 50: ! 51: [email protected] RFC822 new domain-style address ! 52: [email protected] RFC822 "arpa"-style address ! 53: cic@csnet-sh RFC733 address ! 54: ! 55: ! 56: RFC822 ADDRESSES AND DOMAINS ! 57: ! 58: All Internet hosts use RFC822-style addresses. Broadly speaking, this ! 59: means that they can handle addresses that contain dots ("."s) to the right ! 60: of the "@". ! 61: ! 62: The Internet is currently in the process of changing to a "domain" ! 63: system of mail addresses. During the transition, the Internet hosts ! 64: that have not yet adopted new domain-style names are given the temporary ! 65: top (rightmost) domain ".arpa". Almost all Internet hosts that are not ! 66: brand-new and that have registered for new domain-style names also ! 67: retain ".arpa" names as aliases. ! 68: ! 69: A domain name, unlike the older forms of addresses, is a simply a name. ! 70: A domain does not include information about the route that a message ! 71: must travel in order to reach its destination. This information must be ! 72: supplied in some other way. The two methods now in use are (1) host ! 73: tables, such as the "hosts.txt" table supplied by the Internet Network ! 74: Information Center (NIC), and (2) domain servers, which can be used only ! 75: on Internet hosts because they must interact with domain servers on ! 76: other hosts. ! 77: ! 78: In the domain system, the most general form of address can be ! 79: represented as: ! 80: ! 81: local-part@domain Examples: [email protected] ! 82: [email protected] ! 83: [email protected] ! 84: dennis%[email protected] ! 85: ! 86: The "local-part", to the left of the "@", may be simply the user-id, or ! 87: it may be any form of local address that is recognized within the ! 88: domain. The "domain", to the right of the "@", may be a second-level ! 89: domain (representing an organization) followed by a top-level domain, or ! 90: it may contain several layers of subdomains. ! 91: ! 92: Top-level domains represent general classes of organizations. The top- ! 93: level domains that have been registered by the DDN NIC for use by US ! 94: organizations are: ! 95: ! 96: COM (commercial) NET (network administration) ! 97: EDU (educational) ORG (nonprofit) ! 98: GOV (government) ARPA (Arpanet, to be ! 99: MIL (military) phased out) ! 100: ! 101: Top-level domains for countries are: ! 102: ! 103: AU Australia JP Japan ! 104: CA Canada KR Republic of Korea ! 105: CH Switzerland NL Netherlands ! 106: DE West Germany NZ New Zealand ! 107: FI Finland SE Sweden ! 108: FR France UK United Kingdom ! 109: IL Israel US United States ! 110: ! 111: Not all of these domains are in use. The top-level domain, US, for ! 112: the United States has not yet its use defined by the DDN NIC. In the ! 113: future, other countries will register official top-level domains with ! 114: the DDN NIC. ! 115: ! 116: Relay.cs.net recognizes the informal domain ".csnet" for PhoneNet ! 117: sites that have not yet registered for second-level domains. Some ! 118: other informal domains also recognized. Addresses with these domains ! 119: are always rewritten by relay.cs.net: ! 120: ! 121: BITNET CHUNET (Switzerland) OZ (OZ.AU) ! 122: CDN (Canada) JUNET (JAPAN) UUCP ! 123: ! 124: Examples: ! 125: [email protected] --> [email protected] ! 126: [email protected] --> rmxj%[email protected] ! 127: ! 128: The ".csnet" informal domain is being phased out as PhoneNet hosts adopt ! 129: domain-style names. Many PhoneNet hosts allow users to send messages ! 130: with the informal ".csnet" domain, and translate it to "@relay.cs.net". ! 131: ! 132: Example: ! 133: [email protected] --> cheryl%[email protected] ! 134: ! 135: However, it is not correct to add ".csnet" at the end of a domain-style ! 136: address, even though the domain is a PhoneNet site. The rule is, if ! 137: the address of a PhoneNet site contains a "." to the right of the "@", ! 138: DO NOT add ".csnet". ! 139: ! 140: ! 141: RFC733 ADDRESSES ! 142: ! 143: A few CSNET PhoneNet sites still use the RFC733 form, based on the NIC ! 144: document RFC733: ! 145: ! 146: user@host Example: laura@oxbridge ! 147: ! 148: For these sites, relay.cs.net does the necessary translation between ! 149: RFC733 and RFC822 style addresses. (The CIC strongly urges organizations ! 150: on CSNET PhoneNet to change to RFC822 style addresses in preparation for ! 151: applying for second-level domain names.) ! 152: ! 153: ! 154: ========================================================================== ! 155: ! 156: SENDING MAIL ON AN "822" HOST (INTERNET OR PHONENET) ! 157: ! 158: ...to and from hosts with domain-style names (including "host.arpa"): ! 159: ! 160: Internet -> PhoneNet: user%[email protected] ! 161: ! 162: Internet -> Non-US X25Net: user%[email protected] ! 163: ! 164: Internet -> Internet: user@domain ! 165: ! 166: PhoneNet -> PhoneNet: user@domain ! 167: ! 168: PhoneNet -> Non-US X25Net: user@domain ! 169: ! 170: PhoneNet -> Internet: user@domain ! 171: ! 172: When the transition to the domain-style names is complete, top-level ! 173: domains will no longer indicate the physical network. Internet, ! 174: X25Net and Phonenet hosts will all be addressed as user@domain. ! 175: ! 176: At the present time, not all Internet hosts are able to send messages ! 177: correctly to hosts with domain-style names that must be routed through ! 178: relay.cs.net or other gateways. For this reason, although it may seem ! 179: like a step backward, relay.cs.net rewrites domain-style PhoneNet addresses ! 180: in the same way that it rewrites non-domain-style PhoneNet addresses: ! 181: ! 182: [email protected] --> joanne%[email protected] ! 183: [email protected] --> craig%[email protected] ! 184: janet@camford --> janet%[email protected] ! 185: ! 186: ! 187: ...to and from PhoneNet hosts without domains: ! 188: ! 189: Internet -> PhoneNet user%[email protected] ! 190: ! 191: Phonenet -> PhoneNet [email protected] ! 192: ! 193: ! 194: ...to and from other networks ! 195: ! 196: Internet -> Australia user%[email protected] ! 197: Note: See sites-11 in REFERENCES. ! 198: Queries may be sent to postmaster@australia. ! 199: ! 200: Australia -> InterNet user%[email protected] ! 201: ! 202: Internet -> Bell Labs user.system%[email protected] ! 203: Note: Users sufficiently close to the btl gateway ! 204: can be reached as "user%[email protected]". ! 205: ! 206: Bell Labs -> Internet user@domain ! 207: ! 208: Internet -> BITNET user%[email protected] ! 209: Note: See sites-5 and -6 in REFERENCES. ! 210: ! 211: BITNET -> Internet BSMTP with "[email protected]" ! 212: Note: See adr-8 in REFERENCES. WISCVM does not ! 213: yet have access to a domain server and hence ! 214: cannot handle all domain-style names. ! 215: ! 216: Internet -> CDNnet user%[email protected] ! 217: ! 218: CDNnet -> Internet host%[email protected] ! 219: Note: See sites-14 in REFERENCES. ! 220: ! 221: Internet -> DEC ENET [email protected] ! 222: ! 223: DEC ENET -> Internet RHEA::DECWRL::"[email protected]" ! 224: for domain = ARPA, ATHENA (project at MIT), ! 225: BITNET, CSNET(PhoneNet), MAILNET, and OZ ! 226: (Australia), but not UUCP. ! 227: ! 228: Internet -> France user%host.cosac%[email protected] ! 229: Note: See sites-13 in REFERENCES. ! 230: ! 231: Internet -> Japan user%[email protected] ! 232: ! 233: Internet -> MAILNET user%[email protected] ! 234: ! 235: MAILNET -> Internet user%domain@Mit-Multics ! 236: ! 237: Internet -> UK [email protected] ! 238: ! 239: UK -> Internet user@domain ! 240: Note: The UK uses a domain system that is ! 241: "backwards" from the Internet form. The gateway ! 242: host, cs.ucl.ac.uk (US style), also known as ! 243: uk.ac.ucl.cs (UK style), translates the headers. ! 244: Beware of addresses in the body of a message. ! 245: ! 246: Internet -> UUCP [email protected] or ! 247: user%[email protected] ! 248: Note: "hosta" is the recipient's host. The ! 249: sender must specify a UUCP routing path ! 250: between "hosta" and "hostz", a host with a ! 251: direct connection to some UUCP->Internet ! 252: gateway, such as "ucbvax.edu" (berkeley) or ! 253: "harvard.harvard.edu". Harvard is uses ! 254: "pathalias" software to construct a UUCP ! 255: routing address. ! 256: ! 257: UUCP -> Internet hostb!...!hostz!berkeley!user@domain or ! 258: hostb!...!hostz!harvard!user@domain ! 259: Note: "hostb" is the sender's nearest ! 260: neighbor. The sender must specify a UUCP ! 261: routing path between "hostb" and "hostz", a ! 262: host with a direct connection to some ! 263: UUCP->Internet gateway, such as "berkeley" or ! 264: "harvard". Some hosts cannot parse "hybrid" ! 265: addresses that contain both "!" and "@". ! 266: ! 267: Internet -> VNET (IBM) [email protected] ! 268: Note: In the past, ibm.com accepted addresses ! 269: of the form user%[email protected], but these are ! 270: now rejected. ! 271: ! 272: Internet -> XEROX [email protected] ! 273: Note: Do not use "%" between user and registry. ! 274: Some Xerox registries are "pa" and "wbst". ! 275: ! 276: XEROX -> Internet user@domain ! 277: ! 278: ========================================================================== ! 279: ! 280: SENDING MAIL FROM A "733" PHONENET HOST ! 281: ! 282: ...to hosts with new domain-style names: ! 283: ! 284: 733 PhoneNet -> PhoneNet: user%domain@csnet-relay ! 285: ! 286: 733 PhoneNet -> Non-US X25Net: user%domain@csnet-relay ! 287: ! 288: 733 PhoneNet -> Internet: user%domain@csnet-relay ! 289: ! 290: ! 291: ...to ".arpa" hosts: ! 292: ! 293: 733 PhoneNet -> Internet user@host ! 294: ! 295: ! 296: ...to Phonenet hosts without domains: ! 297: ! 298: 733 Phonenet -> PhoneNet user@site ! 299: ! 300: ! 301: ...to other networks: ! 302: ! 303: 733 PhoneNet -> Australia user%host.oz@csnet-relay ! 304: Note: See sites-11 in REFERENCES. ! 305: Queries may be sent to postmaster@australia. ! 306: ! 307: 733 PhoneNet -> Bell Labs user.system%btl.csnet@csnet-relay ! 308: Note: Users sufficiently close to the btl gateway ! 309: can be reached as "user%btl.csnet@csnet-relay". ! 310: ! 311: 733 PhoneNet -> BITNET user%host.bitnet@wiscvm ! 312: Note: See sites-5 and -6 in REFERENCES. ! 313: ! 314: 733 PhoneNet -> CDNnet user%mta-name.cdn@csnet-relay ! 315: Note: See sites-14 in REFERENCES. ! 316: ! 317: 733 PhoneNet -> DEC ENET user%host.dec@decwrl ! 318: ! 319: 733 PhoneNet -> France user%host.cosac%france ! 320: ! 321: 733 PhoneNet -> Japan user%host.junet@csnet-relay ! 322: ! 323: 733 PhoneNet -> MAILNET user%host.mailnet@mit-multics ! 324: ! 325: 733 PhoneNet -> UK user%subdomain.AC.UK@csnet-relay ! 326: ! 327: 733 PhoneNet -> UUCP hostz!...!hostb!hosta!user@berkeley or ! 328: user%host.UUCP@harvard ! 329: ! 330: 733 PhoneNet -> VNET (IBM) user%ibm.com@csnet-relay ! 331: Note: In the past, ibm.com accepted addresses ! 332: of the form user%[email protected], but these are ! 333: now rejected. ! 334: ! 335: 733 PhoneNet -> XEROX user.registry@Xerox ! 336: Note: Do not use "%" between user and registry. ! 337: Some Xerox registries are "pa" and "wbst". ! 338: ! 339: REFERENCES (Info Documents from the CSNET Info Server) ! 340: Note: For instructions on how to order these Info documents by electronic ! 341: mail, send a blank message to [email protected]. ! 342: ! 343: Topics listed under Request: rfc ! 344: rfc822 Aug 82 108K Standard for the Format of ARPA-Internet Text Messages ! 345: rfc821 Aug 82 124K Simple Mail Transfer Protocol ! 346: rfc920 Oct 84 28K Domain Requirements ! 347: ! 348: Topics listed under Request: info ! 349: adr-8 13 Feb 86 8K BITNET <--> CSNET Gateway ! 350: info-4 2 Mar 86 6K Guidelines on Internet Access for CSNET Users ! 351: sites-9a 13 Mar 86 35K JANET (UK): Domains in the NRS ! 352: sites-9b 13 Mar 86 116K JANET (UK): NRS (Name Registration Scheme) ! 353: sites-9c 13 Mar 86 12K JANET (UK): Old Sites Not in the NRS Database ! 354: Note: sites-9a, -9b and -9c may be ordered as sites-9. ! 355: sites-11 6 Nar 86 19K ASCNET (Australia) Sites ! 356: sites-12 2 Apr 86 4K COSAC (France) Sites ! 357: sites-14 18 Mar 86 5K CDNnet (Canada) Message Transfer Agents (Sites) ! 358: ! 359:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.