Connected: An Internet Encyclopedia
3.4.10. NETWORK-SPECIFIC TRANSFORMATIONS

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 822
Up: 3. LEXICAL ANALYSIS OF MESSAGES
Up: 3.4. CLARIFICATIONS
Prev: 3.4.9. BACKSPACE CHARACTERS
Next: 4. MESSAGE SPECIFICATION

3.4.10. NETWORK-SPECIFIC TRANSFORMATIONS

3.4.10. NETWORK-SPECIFIC TRANSFORMATIONS

During transmission through heterogeneous networks, it may be necessary to force data to conform to a network's local conventions. For example, it may be required that a CR be followed either by LF, making a CRLF, or by <null>, if the 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-specific transformations that were necessary to permit migration through the "current" network. It then passes through the modules:


Next: 4. MESSAGE SPECIFICATION

Connected: An Internet Encyclopedia
3.4.10. NETWORK-SPECIFIC TRANSFORMATIONS