![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to adr-3 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Research Unix] / researchv10dc / doc / csnet|
Return to adr-3 CVS log | Up to [Research Unix] / researchv10dc / doc / csnet |
researchv10 Dan Cross
From research!mtune!rutgers!SH.CS.NET!cic Wed Sep 30 03:04:56 1987
Received: by mtune.ATT.COM (smail2.5)
id AA01141; 30 Sep 87 03:04:56 EDT (Wed)
Received: by RUTGERS.EDU (5.54/1.14)
id AA19189; Tue, 29 Sep 87 18:16:00 EDT
Message-Id: <[email protected]>
Received: by SH.CS.NET id ad10308; 29 Sep 87 15:25 EDT
Date: Tue, 29 Sep 87 14:24:44 EDT
Subject: adr-3 Other Networks
Reply-To: rutgers!SH.CS.NET!cic
From: CSNET INFO SERVER <rutgers!SH.CS.NET!info>
To: [email protected]
Request: info
Topic: adr-3
Document Updated: 26 May 87
Subject: Addresses for the Internet, CSNET and Other Networks
==============================================================================
CSNET Coordination and Information Center (CIC) Hotline: 617/497-2777
10 Moulton Street Email: [email protected]
Cambridge, MA 02238 Info-Server requests to: [email protected]
==============================================================================
ADDRESSES FOR THE INTERNET, CSNET AND OTHER NETWORKS Line 1
Contents
Line
INTRODUCTION............................................ 13
RFC822 ADDRESSES AND DOMAINS............................ 32
RFC733 ADDRESSES........................................ 94
SENDING MAIL ON AN "822" (DOMAIN-STYLE) HOST ........... 109
SENDING MAIL ON A "733" (NON-DOMAIN) HOST.............. 224
REFERENCES.............................................. 276
INTRODUCTION
Here is a summary of the current information at the CSNET Coordination
and Information Center (CIC) about addresses for CSNET PhoneNet users.
Networks covered are DARPA Internet (CSNET X25Net, Arpanet, Milnet,
etc.), CSNET PhoneNet, Australia, Bell Labs, BITNET, Canada, DEC ENET,
France, MAILNET, UUCP, UK, and Xerox.
Please note that the use of the DARPA Internet is restricted to
authorized individuals and is regulated by the Defense Communications
Agency. (See info-4 in REFERENCES).
Send corrections and additions to the CIC Service Host (which is on the
Internet):
[email protected] RFC822 new domain-style address
[email protected] RFC822 "arpa"-style address
cic@csnet-sh RFC733 address
RFC822 ADDRESSES AND DOMAINS
All Internet hosts use RFC822-style addresses. Broadly speaking, this
means that they can handle addresses that contain dots ("."s) to the right
of the "@".
The Internet is currently in the process of changing to a "domain"
system of mail addresses. During the transition, the Internet hosts
that have not yet adopted new domain-style names are given the temporary
top (rightmost) domain ".arpa". Almost all Internet hosts that are not
brand-new and that have registered for new domain-style names also
retain ".arpa" names as aliases.
A domain name, unlike the older forms of addresses, is a simply a name.
A domain does not include information about the route that a message
must travel in order to reach its destination. This information must be
supplied in some other way. The two methods now in use are (1) host
tables, such as the "hosts.txt" table supplied by the Internet Network
Information Center (NIC), and (2) domain servers, which can be used only
on Internet hosts because they must interact with domain servers on
other hosts.
In the domain system, the most general form of address can be
represented as:
local-part@domain Examples: [email protected]
[email protected]
[email protected]
dennis%[email protected]
The "local-part", to the left of the "@", may be simply the user-id, or
it may be any form of local address that is recognized within the
domain. The "domain", to the right of the "@", may be a second-level
domain (representing an organization) followed by a top-level domain, or
it may contain several layers of subdomains.
Top-level domains represent general classes of organizations. The top-
level domains that have been registered by the DDN NIC for use by US
organizations are:
COM (commercial) NET (network administration)
EDU (educational) ORG (nonprofit)
GOV (government) ARPA (Arpanet, to be
MIL (military) phased out)
Top-level domains for countries are:
AU Australia JP Japan
CA Canada KR Republic of Korea
CH Switzerland NL Netherlands
DE West Germany NZ New Zealand
FI Finland SE Sweden
FR France UK United Kingdom
IL Israel US United States
Not all of these domains are in use. The top-level domain, US, for
the United States has not yet its use defined by the DDN NIC. In the
future, other countries will register official top-level domains with
the DDN NIC.
Relay.cs.net recognizes the informal domain ".csnet" for PhoneNet
sites that have not yet registered for second-level domains. Some
other informal domains also recognized. Addresses with these domains
are always rewritten by relay.cs.net:
BITNET CHUNET (Switzerland) OZ (OZ.AU)
CDN (Canada) JUNET (JAPAN) UUCP
Examples:
[email protected] --> [email protected]
[email protected] --> rmxj%[email protected]
The ".csnet" informal domain is being phased out as PhoneNet hosts adopt
domain-style names. Many PhoneNet hosts allow users to send messages
with the informal ".csnet" domain, and translate it to "@relay.cs.net".
Example:
[email protected] --> cheryl%[email protected]
However, it is not correct to add ".csnet" at the end of a domain-style
address, even though the domain is a PhoneNet site. The rule is, if
the address of a PhoneNet site contains a "." to the right of the "@",
DO NOT add ".csnet".
RFC733 ADDRESSES
A few CSNET PhoneNet sites still use the RFC733 form, based on the NIC
document RFC733:
user@host Example: laura@oxbridge
For these sites, relay.cs.net does the necessary translation between
RFC733 and RFC822 style addresses. (The CIC strongly urges organizations
on CSNET PhoneNet to change to RFC822 style addresses in preparation for
applying for second-level domain names.)
==========================================================================
SENDING MAIL ON AN "822" HOST (INTERNET OR PHONENET)
...to and from hosts with domain-style names (including "host.arpa"):
Internet -> PhoneNet: user%[email protected]
Internet -> Non-US X25Net: user%[email protected]
Internet -> Internet: user@domain
PhoneNet -> PhoneNet: user@domain
PhoneNet -> Non-US X25Net: user@domain
PhoneNet -> Internet: user@domain
When the transition to the domain-style names is complete, top-level
domains will no longer indicate the physical network. Internet,
X25Net and Phonenet hosts will all be addressed as user@domain.
At the present time, not all Internet hosts are able to send messages
correctly to hosts with domain-style names that must be routed through
relay.cs.net or other gateways. For this reason, although it may seem
like a step backward, relay.cs.net rewrites domain-style PhoneNet addresses
in the same way that it rewrites non-domain-style PhoneNet addresses:
[email protected] --> joanne%[email protected]
[email protected] --> craig%[email protected]
janet@camford --> janet%[email protected]
...to and from PhoneNet hosts without domains:
Internet -> PhoneNet user%[email protected]
Phonenet -> PhoneNet [email protected]
...to and from other networks
Internet -> Australia user%[email protected]
Note: See sites-11 in REFERENCES.
Queries may be sent to postmaster@australia.
Australia -> InterNet user%[email protected]
Internet -> Bell Labs user.system%[email protected]
Note: Users sufficiently close to the btl gateway
can be reached as "user%[email protected]".
Bell Labs -> Internet user@domain
Internet -> BITNET user%[email protected]
Note: See sites-5 and -6 in REFERENCES.
BITNET -> Internet BSMTP with "[email protected]"
Note: See adr-8 in REFERENCES. WISCVM does not
yet have access to a domain server and hence
cannot handle all domain-style names.
Internet -> CDNnet user%[email protected]
CDNnet -> Internet host%[email protected]
Note: See sites-14 in REFERENCES.
Internet -> DEC ENET [email protected]
DEC ENET -> Internet RHEA::DECWRL::"[email protected]"
for domain = ARPA, ATHENA (project at MIT),
BITNET, CSNET(PhoneNet), MAILNET, and OZ
(Australia), but not UUCP.
Internet -> France user%host.cosac%[email protected]
Note: See sites-13 in REFERENCES.
Internet -> Japan user%[email protected]
Internet -> MAILNET user%[email protected]
MAILNET -> Internet user%domain@Mit-Multics
Internet -> UK [email protected]
UK -> Internet user@domain
Note: The UK uses a domain system that is
"backwards" from the Internet form. The gateway
host, cs.ucl.ac.uk (US style), also known as
uk.ac.ucl.cs (UK style), translates the headers.
Beware of addresses in the body of a message.
Internet -> UUCP [email protected] or
user%[email protected]
Note: "hosta" is the recipient's host. The
sender must specify a UUCP routing path
between "hosta" and "hostz", a host with a
direct connection to some UUCP->Internet
gateway, such as "ucbvax.edu" (berkeley) or
"harvard.harvard.edu". Harvard is uses
"pathalias" software to construct a UUCP
routing address.
UUCP -> Internet hostb!...!hostz!berkeley!user@domain or
hostb!...!hostz!harvard!user@domain
Note: "hostb" is the sender's nearest
neighbor. The sender must specify a UUCP
routing path between "hostb" and "hostz", a
host with a direct connection to some
UUCP->Internet gateway, such as "berkeley" or
"harvard". Some hosts cannot parse "hybrid"
addresses that contain both "!" and "@".
Internet -> VNET (IBM) [email protected]
Note: In the past, ibm.com accepted addresses
of the form user%[email protected], but these are
now rejected.
Internet -> XEROX [email protected]
Note: Do not use "%" between user and registry.
Some Xerox registries are "pa" and "wbst".
XEROX -> Internet user@domain
==========================================================================
SENDING MAIL FROM A "733" PHONENET HOST
...to hosts with new domain-style names:
733 PhoneNet -> PhoneNet: user%domain@csnet-relay
733 PhoneNet -> Non-US X25Net: user%domain@csnet-relay
733 PhoneNet -> Internet: user%domain@csnet-relay
...to ".arpa" hosts:
733 PhoneNet -> Internet user@host
...to Phonenet hosts without domains:
733 Phonenet -> PhoneNet user@site
...to other networks:
733 PhoneNet -> Australia user%host.oz@csnet-relay
Note: See sites-11 in REFERENCES.
Queries may be sent to postmaster@australia.
733 PhoneNet -> Bell Labs user.system%btl.csnet@csnet-relay
Note: Users sufficiently close to the btl gateway
can be reached as "user%btl.csnet@csnet-relay".
733 PhoneNet -> BITNET user%host.bitnet@wiscvm
Note: See sites-5 and -6 in REFERENCES.
733 PhoneNet -> CDNnet user%mta-name.cdn@csnet-relay
Note: See sites-14 in REFERENCES.
733 PhoneNet -> DEC ENET user%host.dec@decwrl
733 PhoneNet -> France user%host.cosac%france
733 PhoneNet -> Japan user%host.junet@csnet-relay
733 PhoneNet -> MAILNET user%host.mailnet@mit-multics
733 PhoneNet -> UK user%subdomain.AC.UK@csnet-relay
733 PhoneNet -> UUCP hostz!...!hostb!hosta!user@berkeley or
user%host.UUCP@harvard
733 PhoneNet -> VNET (IBM) user%ibm.com@csnet-relay
Note: In the past, ibm.com accepted addresses
of the form user%[email protected], but these are
now rejected.
733 PhoneNet -> XEROX user.registry@Xerox
Note: Do not use "%" between user and registry.
Some Xerox registries are "pa" and "wbst".
REFERENCES (Info Documents from the CSNET Info Server)
Note: For instructions on how to order these Info documents by electronic
mail, send a blank message to [email protected].
Topics listed under Request: rfc
rfc822 Aug 82 108K Standard for the Format of ARPA-Internet Text Messages
rfc821 Aug 82 124K Simple Mail Transfer Protocol
rfc920 Oct 84 28K Domain Requirements
Topics listed under Request: info
adr-8 13 Feb 86 8K BITNET <--> CSNET Gateway
info-4 2 Mar 86 6K Guidelines on Internet Access for CSNET Users
sites-9a 13 Mar 86 35K JANET (UK): Domains in the NRS
sites-9b 13 Mar 86 116K JANET (UK): NRS (Name Registration Scheme)
sites-9c 13 Mar 86 12K JANET (UK): Old Sites Not in the NRS Database
Note: sites-9a, -9b and -9c may be ordered as sites-9.
sites-11 6 Nar 86 19K ASCNET (Australia) Sites
sites-12 2 Apr 86 4K COSAC (France) Sites
sites-14 18 Mar 86 5K CDNnet (Canada) Message Transfer Agents (Sites)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.