RFC - 1349
Type of Service in the Internet Protocol Suite
| Original: | ftp://ftp.isi.edu/in-notes/rfc1349.txt |
|---|---|
| Authors: | P. Almquist [Consultant] |
| Date: | July 1992 |
| Category: | Informational |
| This specification has been !!! obsoleted !!! | |
| Obsoleted by: | |
|---|---|
| RFC-2474prop | Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers (Updated by RFC-3260, RFC-3168prop) |
| Updates: | |
|---|---|
| RFC-1248 | OSPF Version 2 Management Information Base (Obsoleted by RFC-1252 -> RFC-1253 -> RFC-1850 -> RFC-4750prop) (Updated by RFC-1349) |
| RFC-1247 | OSPF Version 2 (Obsoleted by RFC-1583 -> RFC-2178 -> RFC-2328std54) (Updated by RFC-1349) |
| RFC-1195prop | Use of OSI IS-IS for routing in TCP/IP and dual environments (Updated by RFC-1349) |
| RFC-1123std3 [STD 3] |
Requirements for Internet Hosts - Application and Support (Updated by RFC-1349, RFC-2181prop) |
| RFC-1122std3 [STD 3] |
Requirements for Internet Hosts - Communication Layers (Updated by RFC-1349, RFC-4379prop) |
| RFC-1060 | Assigned numbers (Obsoleted by RFC-1340 -> RFC-1700hist -> RFC-3232) (Updated by RFC-1349) |
| RFC-791std5 [STD 5] |
Internet Protocol (Updated by RFC-1349) |
| Referred by: | 38 RFC |
| Refers to: | 14 RFC |
Status
This document specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Abstract
This memo changes and clarifies some aspects of the semantics of the Type of Service octet in the Internet Protocol (IP) header. The handling of IP Type of Service by both hosts and routers is specified in some detail.
This memo defines a new TOS value for requesting that the network minimize the monetary cost of transmitting a datagram. A number of additional new TOS values are reserved for future experimentation and standardization. The ability to request that transmission be optimized along multiple axes (previously accomplished by setting multiple TOS bits simultaneously) is removed. Thus, for example, a single datagram can no longer request that the network simultaneously minimize delay and maximize throughput.
In addition, there is a minor conflict between the Host Requirements (RFC-1122std3 and RFC-1123std3) and a number of other standards concerning the sizes of the fields in the Type of Service octet. This memo resolves that conflict.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry