RFC 822:STANDARD FOR THE FORMAT OF ARPA INTERNET ...
RFC-Ref

network


Click on the red underlined text to get to the source

... Writers of mail-sending (i.e., header-generating) programs should realize that there is no network-wide definition of the effect of ASCII HT (horizontal-tab) characters on the appear- ...
... effect of ASCII HT (horizontal-tab) characters on the appear- ance of text at another network host; therefore, the use of tabs in message headers, though permitted, is discouraged. ...
... NETWORK-SPECIFIC TRANSFORMATIONS ...
... During transmission through heterogeneous networks, it may be necessary to force data to conform to a network's local con- ...
... During transmission through heterogeneous networks, it may be necessary to force data to conform to a network's local con- ventions. For example, it may be required that a CR be fol- ...
... CR is to stand alone). Such transformations are reversed, when the message exits that network. ...
... When crossing network boundaries, the message should be treated as passing through two modules. It will enter the first module containing whatever network ...
... network boundaries, the message should be treated as passing through two modules. It will enter the first module containing whatever network-specific transforma- tions that were necessary to permit migration through the ...
... tions that were necessary to permit migration through the "current" network. It then passes through the modules: ...
... The "current" network's idiosyncracies are removed and the message is returned to the canonical form ...
... The "next" network's local idiosyncracies are imposed on the message. ...


... The list of known "via" and "with" values are registered with the Network Information Center, SRI International, Menlo Park, California. ...
... expected to be a computer system term, and not (for example) a generalized person reference which can be used outside the network text message context. ...
... A limited number of common fields have been defined in this document. As network mail requirements dictate, addi- tional fields may be standardized. To provide user-defined ...
... Names of Extension-fields are registered with the Network Information Center, SRI International, Menlo Park, California. ...
... Individual users of network mail are free to define and use additional header fields. Such fields must have names ...


... stitute name-domains that are independent logically of specific machines. In addition, networks and machines impli- citly compose name-domains, since their membership usually is ...
... Note that "organization" is a logical entity, separate from any particular communication network. ...
... The latter, network-oriented case permits simple, direct, attachment-related address specification, such as: ...
... user@host.network ...
... Once the network is accessed, it is expected that a message will go directly to the host and that the host ...
... A domain-ref must be THE official name of a registry, network, or host. It is a symbolic reference, within a name sub- ...
... bypass standard mechan- isms for resolving such references, using more primitive information, such as a network host address rather than its associated host name ...
... under in the ARPA Internet, are registered with the Network Information Center, SRI International, Menlo Park, California. ...


... Bennett, C.J. "JNT Mail Protocol". Joint Network Team, Ruther- ford and Appleton Laboratory: Didcot, England. ...
... Bhushan, A.K., Pogran, K.T., Tomlinson, R.S., and White, J.E. "Standardizing Network Mail Headers," ARPANET Request for ...
... Mail Headers," ARPANET Request for Comments No. 561, Network Information Center No. 18516; SRI International: Menlo Park (September 1973). ...
... Crocker, D.H., Vittal, J.J., Pogran, K.T., Henderson, D.A. "Standard for the Format of ARPA Network Text Message," ARPANET ...
... Text Message," ARPANET Request for Comments No. 733, Network Information Center No. 41952. SRI International: Menlo Park (November 1977). ...
... Levin, R. and Schroeder, M. "Transport of Electronic Messages through a Network," TeleInformatics 79, pp. 29-33. North Holland (1979). Also as Xerox Palo Alto Research Center Technical Report CSL-79-4. ...
... Myer, T.H. and Henderson, D.A. "Message Transmission Protocol," ARPANET Request for Comments, No. 680, Network Information Center No. 32116. SRI International: Menlo Park (1975). ...
... NIC. Internet Protocol Transition Workbook. Network Information Center, SRI-International, Menlo Park, California (March 1982). ...


... The following summarizes the differences between this stan- dard and the one specified in Arpanet Request for Comments #733, "Standard for the Format of ARPA Network Text Messages". The differences are listed in the order of their occurrence in the ...



Google
Web
RFC-Ref