RFC 1168
Intermail and Commercial Mail Relay services
Part 1 of 4 🎀
Title Block 🦋
Okay bestie, here's the lowdown on RFC 1168 💅
- RFC number and title: RFC 1168, INTERMAIL AND COMMERCIAL MAIL RELAY SERVICES
- Authors: A. Westine, A. DeSchon, J. Postel, and C.E. Ward, all at USC/ISI
- Date: July 1990
- Category: an information document, not a standard (more on that below 👀)
- Obsoletes and updates: the title block doesn't list anything for either one
STATUS OF THIS MEMO 🌸
So this RFC is basically a history of Intermail and the Commercial mail systems 📜 It also digs into the problems people ran into while operating a store-and-forward mail relay between commercial systems like Telemail, MCI Mail, and Dialcom 😭 It's giving "here's what happened" energy, not "here's a rule you have to follow." This RFC provides information for the Internet community, and it does not specify any standard 🫶 Distribution of this memo is unlimited ✨
INTRODUCTION 🧚
Okay so electronic mail has gotten sooo important 💌 Big mail systems have become a huge part of how people in the scientific research community communicate and coordinate with each other. Literally everyone's in their inbox 🙈
This paper is a summary of how an experiment in protocol interoperation went, plus a status report on where it's at now 🔥 The experiment connects mail systems that were designed differently from each other. USC/Information Sciences Institute (ISI) started this experiment in 1981 💖 Over the years it's grown into a demo service that lets users swap mail between the Internet and a few commercial mail systems. Iconic behavior from ISI 👑
Other organizations have started offering similar services lately 🌈 That tells you there's an ongoing need for the Internet and the commercial mail systems to work together. We believe ISI's pioneering work in this area helped push that expansion along 🦋
So which systems are we even talking about? 🤔 There's the Internet mail system, the US Sprint Telemail system, the MCI Mail system, and the Dialcom systems. Every single one was built to run on its own, with no easy way for a user on one system to email a user on another 💀
The Intermail and Commercial Mail Relay (CMR) services in this paper exist to fix that gap 🎀 They were built so you can send mail between the Internet and these commercial systems, no cap.
Here's the Internet in a nutshell 🌍 It's an interconnected system of networks that uses the SMTP mail protocol. That includes the ARPANET, MILNET, NSFNET, and about 700 other networks. Mail relays let it swap mail with BITNET, CSNET, and the UUCP networks too 🍓 To users, the whole Internet looks like one big mail system with at least 100,000 computers and at least 400,000 users 🤯 Figure 1 shows the path a message takes when a user on one Internet host sends mail to a user on another Internet host. For more details on the Internet and connected networks, see Appendix A 📚
Once commercial mail systems got popular, it became super clear that the Internet and those systems needed a mail link between them 💜 See Appendix B for that story. More and more commercial and research entities needed to talk with the Internet research community. A lot of those organizations (for one reason or another) weren't really a good fit to become Internet sites 🙈 Intermail and CMR let those groups reach Internet users by buying electronic mail services from commercial companies. It's the glow-up nobody saw coming ✨
COMMERCIAL SYSTEMS SERVED ✨
okay so the CMR gives mail relay between the Internet and two commercial email systems: the US Sprint Telemail system and the Dialcom system 💌. a CMR connection to MCI Mail is under development. MCI Mail is currently served by the TOPS-20 Intermail system. see Appendix C for recent traffic data 📊.
Telemail is an international commercial service 🌍. some of the Telemail systems the CMR serves are MAIL/USA, NASAMAIL/USA, and GSFC/USA. some government agencies, like NASA and the Environmental Protection Agency, have dedicated Telemail systems. companies also exist that buy bulk services from Telemail and resell them to individuals, and Omnet's Sciencenet is a super popular example of that 🧚.
Dialcom is a commercial service that's kinda like Telemail, since it also has facilities for groups to buy tailored services 🎀. some government agencies (like the National Science Foundation and the U.S. Department of Agriculture) have special group-access plans. the IEEE Computer Society also has a dedicated group service called IEEE Compmail, which is open to members of the IEEE Computer Society 💜.
MCI Mail is operated by MCI and is marketed to large companies as well as individual users 🦋.
Specific examples of the users of Intermail and the CMR are as follows:
- Scientists in Oceanography, Astronomy, Geology, and Agriculture use Intermail and the CMR to communicate with colleagues 🔬. many of these scientists have accounts on "Sciencenet", which is actually part of a Telemail system administered by Omnet.
- The IEEE Computer Society's publication editors use the Dialcom system "Compmail" to manage the papers being prepared for their numerous publications 📚. many of the authors are in university departments with access to the Internet. Intermail and the CMR support a significant exchange of large messages containing manuscripts.
- NASA uses Telemail systems for its own work and has extensive exchanges through its own relay service, as well as Intermail and the CMR, for communicating with university scientists on the Internet 🚀.
Other developments to interoperate between the Internet and commercial mail systems are:
- The Merit gateway to Sprintmail and IEEE Compmail
- The CNRI gateway to MCI Mail
- The Ohio State University gateway to Compuserve, and,
- NASA-Ames gateway to Telemail
ACCEPTABLE USE POLICY FOR INTERMAIL AND THE CMR 🌸
the Internet is made of loads of networks, sponsored by loads of organizations 🌐. however, all the Internet's long-haul networks are provided by U.S. government agencies. each of these agencies limits the use of the facilities it provides in some way. in general, an agency's statement about how its facilities may be used is called an "Acceptable Use Policy" 📜.
the various agencies involved in the Internet are currently preparing their Acceptable Use Policy statements. most of these are still drafts and haven't been released as official agency statements yet. none of these policies are currently available as online documents 🙈.
in the least restrictive case, all bona fide researchers and scholars, public and private, from the United States and foreign countries (unless denied access by national policy) are allowed access 🎓.
the Intermail and Commercial Mail Relay (CMR) systems at ISI are resources provided by the Defense Advanced Research Projects Agency (DARPA) for computing and communication. use of these resources must be limited to DARPA-sponsored work or other approved government business (or must otherwise meet the acceptable use policy of DARPA), only.
however, DARPA, as a member of the Federal Research Internet Coordinating Committee (FRICC), has agreed to the FRICC draft policy for communication networks, which provides in part that: "The member agencies of the FRICC agree to carry all traffic that meets the Acceptable Use Policy of the originating member agency".
thus, e-mail messages (i.e., "traffic") that meet the Acceptable Use Policy of an agency and pass through some facility of that agency (i.e., "the originating member") on the way to Intermail or CMR are allowed 💖.
the current member agencies of the FRICC are DARPA, NSF, DOE, NASA, and NIH.
BITNET and UUCP (and other) networks are interconnected to the Internet via mail relays. it is the responsibility of the managers of these mail relays to ensure that the e-mail messages ("traffic") that enter the Internet via their mail relays meet the Acceptable Use Policy of the member agency providing the Internet access.
in addition, we cannot allow CMR or Intermail to be used simply as a bridge between two commercial systems, even though CMR has this technical capability. at least one end of the communication must be related to FRICC acceptable use 🚫.
DETAILS OF CMR SYSTEM USE 🎀
the CMR host computer is Internet host INTERMAIL.ISI.EDU (128.9.2.203). users of the commercial system are required to know the proper gateways between the Internet and other networks, such as BITNET, CSNET, or UUCP. users on networks interconnected to the Internet likewise need to know how to reach the Internet to send mail through INTERMAIL.ISI.EDU to a commercial system 🗺️.
the relay connection to Telemail is through their host TELEMAIL/USA. the general syntax for Telemail addresses is [USER/ORGANIZATION]HOST/COUNTRY, which makes the full address for the relay mailbox:
[INTERMAIL/USCISI]TELEMAIL/USAusers across the entire Telemail service can send mail to this address. users on the TELEMAIL host only need to send to INTERMAIL 📬.
Internet users can use the basic Telemail format, append a "%TELEMAIL" to it, and mail to the resulting address as if it really existed on INTERMAIL.ISI.EDU, e.g.:
[CWARD/USCISI]TELEMAIL/USA%TELEMAIL@INTERMAIL.ISI.EDUnote that the CMR system will accept anything before the "%TELEMAIL". that is, the CMR does not validate Telemail addresses before transmitting them to Telemail 👀.
the CMR handles Dialcom mail delivery in a similar way, but this system has what might be called "virtual hosts" 🦄. groups can be set up with an alias system to allow easier intra-group access. for example, both NSF and USDA share the same Dialcom host (157); but, while both groups send relay messages to Intermail, their actual fully qualified Dialcom mailboxes are different. for example, NSF's mailbox is NSF153, and USDA's mailbox is AGS9999.
mail going in either direction may use an embedded Simple Forwarding Header. an SFH must be the first part of the message text. it starts with a "Forward:" field followed by a "To:" field. "Cc:", "Subject:", and other fields may follow the "To:" fields. the SFH is terminated by a blank line 💅.
this is a template of an SFH:
Forward: Destination-Network
To: User@host1, User@host2,
User2@host2
Cc: User@host1
Subject: This subject supercedes the subject in the host net header
<Blank-Line>Dialcom syntax is "Host-ID:User-ID", for example, 134:ABC1234. this format will work from any Dialcom host, but users in the same group as ABC would be able to use the user name, for example, JSMITH 🌈.
using the SFH format, mail to a Dialcom system could be sent as follows:
To: Intermail@ISI.EDU
Subject: Test Message
Forward: Compmail
To: 134:ABC1234
Here is the text of the message.proper destination network names include ARPA, Telemail, Compmail, NSF-Mail, and USDA-Mail 🧾.
it is possible for a user to make mistakes at many points in the process 🙈. errors are handled as automatically as possible by the CMR. many errors are caught in the standard Internet mail traffic, and users receive the usual error messages from the system. messages with incorrect commercial system addresses or faulty SFHs are also automatically returned to sender. messages that the software cannot handle are sent to the CMR's user-service mailbox, Intermail-Request@ISI.EDU. this mailbox has been set up to take care of user problems and to be a central distribution point for user instructions 🫶.
PROBLEMS 🎀
Okay so the CMR has some real problems 😭 Its store-and-forward design causes a bunch of them. The biggest one is that almost all of the commercial systems have no machine-to-machine interface, so the CMR software has to pretend to be a human user 🤖💅 The Internet and commercial systems also use different syntax for electronic mail addresses. A major goal of the CMR project is to make the link between networks as transparent as possible, so Internet users can use off-the-shelf mail programs ✨ Making commercial address formats fit the Internet standard is a major task [2].
Compatibility with Internet addressing standards is a concern too 🌸 The commercial accounts can't use the transparency features of the Domain Name System (DNS) (see Appendix D), and some commercial addresses clash with Internet syntax. That means Internet users have to keep using the older methods 🙈
Reducing the time needed to maintain the system is another general problem to solve 🛠️ Since most commercial systems force our software to mimic a human user, automatic error detection and handling get really complicated. The Intermail system needs a human to step in and process failed mail. The CMR's goal is to fully automate all of this 🦋
The CMR and its predecessor, Intermail, both have to deal with how often commercial systems change their software 🔄 The changes are usually minor and don't bother most human users. The CMR, though, depends on recognizing certain strings. To avoid rebuilding the whole CMR every time those strings change, most of the string markers are stored in ASCII files that get read at run time 📂
Translating commercial system addresses has created its own set of problems, and most of them come from "special" characters used by the commercial systems 💀
Telemail puts square brackets ("[" and "]") around user names. These characters aren't special by Internet standards when they show up in the local part of an address. But many (maybe most) Internet mailers refuse to accept them unless they're quoted. MMDF was modified locally to fix this 🧚
The square bracket problem is even worse for users of IBM mainframe machines, many of which are on BITNET. On lots of BITNET IBM hosts, the square bracket isn't a printable character, so all kinds of strange addresses can result from using it 😭
The colon is another example 💜 Dialcom uses it as the delimiter between host and mailbox. But the colon is a special character in the Internet mail standard [2]. Users can dodge this by using the SFH and putting the Dialcom address at the beginning of the message text. The CMR can accept addresses with colons, but many Internet hosts and relays can't accept addresses that contain them. Mail with colons in the address fields often gets rejected by Internet hosts and returned to the Intermail-Request mailbox for error processing, which can cause big delays 🐢
There have also been problems from confusion over which hosts are mail relays between the Internet and other systems that are compatible with the Internet mail standard [2] (e.g., BITNET, UUCP, and CSNET). When the CMR was implemented, it was decided that the CMR would not keep track of these mail relays. When a relay changes, like the BITNET mail relays did in 1988, mail may get rejected because the host either no longer exists or refuses the mail 💀
The mail relay problem is part of a bigger one: getting info about new features and changes to the user community. Almost none of the CMR's users are local. Many are hidden behind the veil of the commercial system. (Dealing with commercial system customer support people has been really frustrating, since few of them seem to understand the concept of machine-to-machine exchanges 🙃) Enhancements to commercial software that require minor changes can disrupt some CMR users for days 😩
Another problem that hasn't been adequately solved is validating commercial system addresses and processing failed commercial system mail 🫠 Telemail won't validate a user/host combination until after the full text of the message has been transmitted. If a long message goes to an invalid address, it can be very expensive in wasted time and connect charges 💸
Telemail also gives inadequate info when the host is correct but the user name isn't. The failed mail notice from Telemail is of little use to either a human reader or the CMR software. The only thing Telemail returns is the message ID number. It gives no subject and no text to tell the message apart from the many others that pass through the mailbox 📭
Dialcom does a better job validating addresses ✨ If an address isn't recognized, the system immediately prompts for a correction. A simple <RETURN> deletes the invalid address from the list.
The commercial systems are built for paying customers sending and receiving mail to other paying customers. They can't handle reverse billing, or "collect calls." ISI is currently charged for the connect time needed to send and receive mail to and from other Internet sites 💸 One possible fix would be to extend the CMR to include accounting and billing procedures that pass the costs of the CMR on to its users.
What had been GTE Telemail became Sprint SprintMail, Telenet became Sprintnet, and the host TELEMAIL/USA became SM66/USA 🔁
In April 1990, Sprint installed its X.400 implementation 🎉 For the time being, the old-style Interconnect syntax still works. The CMR telemail channel and the Simple Forwarding Header (SFH) processor were both modified to accept either format in the SprintMail "From" field.
Sprint uses the following syntax for X.400:
(O:USCISI,UN:INTERMAIL,TS:SM66)The SFH processor will "translate" this into:
/O=USCISI/UN=INTERMAIL/TS=SM66/%TELEMAILThe channel program reverses the process. In the translation, parentheses become slashes, colons become equal signs, and commas become slashes, and vice versa 🔀
Unfortunately, the translation algorithm isn't foolproof 😬 A Sprint/Internet relay didn't use the same field names and values as SprintMail did. So a CMR translated address can't be sent unmodified to Sprint's relay, Sprint.COM, and addresses processed by Sprint.COM can't be sent unmodified to the CMR.
From experimenting, the changes needed to make a CMR processed address acceptable to Sprint.COM are: (1) take the "non-standard" X.400 fields of "UN" and "TS" and prepend "DD." to them, (2) add the country field and code (C:US), and (3) add the Telemail administrative domain name (ADMD:Telemail). The example above would become:
/O=USCISI/DD.UN=INTERMAIL/DD.TS=SM66/ADMD=TELEMAIL/C=US/@Sprint.COMThe country code has to change from "US" to "USA." The CMR queue name also has to be appended: "%TELEMAIL."
It gets more complicated 🙃 Sprint decided to only relay mail to and from its own administrative domain. Other X.400 ADMDs may be added in the future if payment problems can be sorted out.
SprintMail-encoded Internet addresses aren't parsed correctly by the SFH processor. But that shouldn't be a major problem, since who on the Internet is going to send to the commercial side of the relay? 🤷♀️
When the NSF decided to terminate NSFMAIL, it became clear that the CMR Project needed a way to get news out to the commercial users 📰 The CMR channel programs can now append a news file to the end of messages going into the commercial networks. After transmitting a message, each channel checks for a news file with the channel name and, if one is present, sends it.
The biggest costs of the CMR are the connect times to the Sprintnet X.25 network and the commercial machines 💸 Making the CMR transmit faster is the current number one problem 🏃♀️
Three strategies are being pursued:
- Improve the implementation of the current method
- Change the method to take advantage of changes in the commercial software
- Upgrade the modems and increase the number of phone lines
For a list of known problems or bugs in the CMR software, see the Appendix of the program logic manual [6] 🐛
FUTURE DIRECTIONS 🚀
No software project is ever really finished, and the CMR is no exception 🌈 There are lots of possible extensions, some harder than others.
One addition that will be made to the CMR is a channel for interacting with MCI Mail 💌 MCI Mail is one of the original TOPS-20 commercial systems that Intermail serviced. The CMR will need to replace this function before all of the TOPS-20 machines are removed from service on the Internet 👑
The CMR is adaptable enough that adding new commercial systems shouldn't be a big problem. Additional commercial systems under consideration include General Electric's GENIE, Western Union's EasyLink, and Compuserve 🧚
One possible addition to the CMR system could be maintaining a list of gateways 🌉 This would let commercial system users work the native address formats of other networks into the SFHs. The upside is that users could simply tell the CMR to forward a message to BITNET, for example, and the CMR would find the gateway and format the address properly for that gateway 🫶
To make things easier for Internet users, the system might treat each commercial system as an Internet host and create DNS database records for them ✨ That would let users send mail to a non-Internet user at an Internet-style domain name 🦋
Another improvement would be accepting X.400-style addressing. The current system rejects them 🙅♀️
To further reduce the hazards of string changes in the commercial system software, an AI component could be added to the commercial system interfaces 🤖 Such a component might be able to "figure out" what marker a new prompt represents and remember it 🧠
ACCESS INFORMATION 📬
For instructions on how to use Intermail and the CMR, contact Intermail-Request@ISI.EDU 💖
REFERENCES 📚
[1] Cohen, D., "A Suggestion for Internet Message Forwarding for MOSIS", IEN-180, USC/Information Sciences Institute, March 1981.
[2] Crocker, D., "Standard for the Format of ARPA Internet Text Messages", RFC-822, University of Delaware, August 1982.
[3] DeSchon, A. L., "MCI Mail/ARPA Mail Forwarding", USC/Information Sciences Institute, ISI Research Report, RR-84-141, August 1984.
[4] DeSchon, A. L., "INTERMAIL, An Experimental Mail Forwarding System", USC/Information Sciences Institute, ISI Research Report, RR-85-158, September 1985.
[5] Kingston, D., "MMDF II: A Technical Review", Usenix Conference, Salt Lake City, August 1984.
[6] Ward, C. E., "The Commercial Mail Relay Project: Intermail on UNIX", USC/Information Sciences Institute, 1988.
APPENDIX A ✨
The Internet and Connected Networks
okay bestie, the Internet is a network of networks linked together by gateways or routers 🌐 the common element holding it all together is the TCP/IP protocol suite 💜 it now has approximately 800 networks and 100,000 host computers 🤯 It's made up of local area networks at research institutes and university campuses, regional networks, and long-haul networks 🦋 those resources are backed by the using organizations and several US government agencies (including DARPA, NSF, NASA, DOE, and NIH) 🇺🇸 the long-haul networks in the Internet are the ARPANET, the MILNET, the NSFNET Backbone, the NASA Science Internet (NSI), and the DOE Energy Science Network (ESNET) 💅
Other systems using TCP/IP or other protocols might be networks of networks too, but they're "internets" with a lowercase "i" 🙈 the capital "I" Internet is specifically the one we just described, so don't mix them up 😭
there are also other networks with (semi-)compatible email systems: BITNET (and EARN and NETNORTH), UUCP (and EUNET), CSNET, ACSNET, and JANET 📬 users might not even notice where they're crossing between these systems and the Internet 🫠
The Domain Name System (DNS) is the Internet mechanism for translating host computer names into addresses 🔍 it also lets host computers that aren't directly on the Internet have registered names in the same style 🧚
BITNET (Because It's Time NETwork)
BITNET has about 2,500 host computers, mostly at universities in lots of countries 🎓 EDUCOM manages it and provides administrative support and information services 💼 there are three main constituents: BITNET in the United States and Mexico, NETNORTH in Canada, and EARN in Europe 🇪🇺 there's also AsiaNet in Japan and connections in South America 🌏 gateways exist between BITNET and the Internet, and the most common one is CUNYVM.CUNY.EDU 🚪
CSNET (The Computer + Science Network)
CSNET has 180 member organizations, mainly computer science research labs at universities and research institutes, with international affiliates in more than a dozen countries 🧠 they've adopted DNS-style names for all their host computers 💖 it's administered by the University Corporation for Atmospheric Research (UCAR) and gets its admin support and info services through the CSNET Information Center (CIC) at Bolt Beranek and Newman (BBN) 🏢 the gateway between CSNET and the Internet is RELAY.CS.NET 🌈
Note: CSNET and BITNET have officially merged into a single organization as of October 1, 1989. 👀
UUCP (UNIX to UNIX Copy)
UUCP is a protocol, a set of files, and a set of commands for copying data files from one UNIX machine to another 🐧 these procedures are widely used to build a hop-by-hop email system 📨 the best part is that any UNIX host can join by setting up a connection (dial-up or permanent) with any UNIX host already in the system 🔌 in the basic UUCP system, the sending user source routes mail through a path of connected hosts to the destination 🗺️ there are databases of connection information (UUCP maps) and programs (pathalias) that help figure out routes 🧭 some UUCP hosts use DNS-style names too 💫 EUNET is a UUCP-based network in Europe, and JUNET is a similar net in Japan 🌍 those international branches use DNS-style names as well 🌸 there are many hosts that can relay mail between UUCP and the Internet, and one prominent gateway is UUNET.UU.NET 💜
JANET (Joint Academic NETwork)
JANET is the primary academic network in the United Kingdom, linking about 1,000 computers at about 100 universities and research institutes 🇬🇧 its domain name system is similar to the Internet's, but the order of the domain name parts is flipped, with the top-level domain on the left 🔄 the protocols are the UK "Coloured Books" 📕 the primary gateway between JANET and the Internet is NSFNET-RELAY.AC.UK ⭐
ACSNET (Australian Computer Science Network)
ACSNET is the principal electronic mail system for the computer science and academic research community in Australia, connecting about 300 sites 🦘 it works similarly to UUCP, and it has a domain naming syntax similar to Internet domains 💕 the gateways between ACSNET and the Internet are MUNNARI.OZ.AU and UUNET.UU.NET 🫶
APPENDIX B 🗺️
the map itself didn't come through, just the placeholder, so here it is:
<<< Mail Systems Map >>>APPENDIX C 📊
okay, the mail traffic numbers from March, April, and May 1990 are next 📈 each table shows sent, read, and total messages per system, plus the messages-per-day math 💅
March 1990 sent read total
Telemail 1291 768 2059
MCI Mail 56 44 100
Compmail 634 306 940
NSF-Mail 370 243 613
CGnet 171 82 253
USDA Mail 6 1 7
BellSouth 6 10 16
Other 0 0 0
Total 2534 1454 3988
Days in Month 31
Messages per Day 128.65April 1990 sent read total
Telemail 1363 696 2059
MCI Mail 40 39 79
Compmail 771 329 1100
CGnet 361 191 552
USDA Mail 28 31 59
BellSouth 98 73 17
Other 0 0 0
Total 2661 1361 4022
Days in Month 30
Messages per Day 134.07May 1990 sent read total
Telemail 1007 561 1568
MCI Mail 23 12 35
Compmail 815 359 1174
CGnet 406 210 616
USDA Mail 12 5 17
BellSouth 167 93 260
Other 0 0 0
Total 2430 1240 3670
Days in Month 31
Messages per Day 118.39APPENDIX D 📚
The Domain Name System
DNS handles translation between host names and addresses 🔍 within the Internet, that means going from a name like "ABC.ISI.EDU" to an IP address like "128.9.0.123" ✨ the DNS is a set of protocols and databases 💖 the protocols define the syntax and semantics for a query language that asks questions about information located by DNS-style names 🗣️ the databases are distributed and replicated, so there's no dependence on a single central server, and each part of the database is provided in at least two servers 🫶
on top of translating names for Internet hosts, the DNS also lets you register DNS-style names for other hosts that you can reach via email through gateways or mail relays 📬 those records point to an Internet host (one with an IP address) that acts as a mail forwarder for the registered host 🧚 for example, the Australian host YARRA.OZ.AU is registered in the DNS with a pointer to the mail relay UUNET.UU.NET 🦘 this gives email users a uniform mail addressing syntax and means they don't have to know about the underlying network boundaries 🌈
SECURITY CONSIDERATIONS 🔐
Security issues are not discussed in this memo. Not one word, bestie. 😱 Full stop. 💀
AUTHORS' ADDRESSES 💌
and last but not least, the squad behind this one 👑 all four authors are at USC/Information Sciences Instutite (that's how the original spells it, so I've kept it exactly as-is 🙈)
Ann Westine
Ann Westine
USC/Information Sciences Instutite
4676 Admiralty Way
Marina del Rey, CA 90292-6695
Phone: (213) 822-1511
EMail: Westine@ISI.EDUAnnette DeSchon
Annette DeSchon
USC/Information Sciences Instutite
4676 Admiralty Way
Marina del Rey, CA 90292-6695
Phone: (213) 822-1511
EMail: DeSchon@ISI.EDUJon Postel
Jon Postel
USC/Information Sciences Instutite
4676 Admiralty Way
Marina del Rey, CA 90292-6695
Phone: (213) 822-1511
EMail: Postel@ISI.EDUCraig E. Ward
Craig E. Ward
USC/Information Sciences Instutite
4676 Admiralty Way
Marina del Rey, CA 90292-6695
Phone: (213) 822-1511
EMail: Ward@ISI.EDUthat's the whole RFC, bestie! 🌈🦋✨ you made it!! 🫶💖
📦 where this page comes from
- ietf: rfc1168 1990-07
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms