Connected: An Internet Encyclopedia
RFC 1122 - 4.2.4.2 Type-of-Service

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1122
Up: 4. TRANSPORT PROTOCOLS
Up: 4.2 TRANSMISSION CONTROL PROTOCOL -- TCP
Up: 4.2.4 TCP/APPLICATION LAYER INTERFACE
Prev: 4.2.4.1 Asynchronous Reports
Next: 4.2.4.3 Flush Call

### 4.2.4.2 Type-of-Service

The application layer MUST be able to specify the Type-of- Service (TOS) for segments that are sent on a connection. It not required, but the application SHOULD be able to change the TOS during the connection lifetime. TCP SHOULD pass the current TOS value without change to the IP layer, when it sends segments on the connection.

The TOS will be specified independently in each direction on the connection, so that the receiver application will specify the TOS used for ACK segments.

TCP MAY pass the most recently received TOS up to the application.

DISCUSSION

  Some applications (e.g., SMTP) change the nature of their communication during the lifetime of a connection, and therefore would like to change the TOS specification.

  Note also that the OPEN call specified in RFC-793 includes a parameter ("options") in which the caller can specify IP options such as source route, record route, or timestamp.

Next: 4.2.4.3 Flush Call

Connected: An Internet Encyclopedia
RFC 1122 - 4.2.4.2 Type-of-Service