A new Request for Comments is now available in online RFC libraries.


        RFC 1349:

        Title:      Type of Service in the Internet Protocol Suite
        Author:     P. Almquist
        Mailbox:    almquist@Jessica.Stanford.EDU
        Pages:      28
        Characters: 68,949
        Updates:    RFCs 1248, 1247, 1195,
                    1123, 1122, 1060, 791


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-1122 and RFC-1123) and a number of other standards concerning the
sizes of the fields in the Type of Service octet.  This memo resolves
that conflict.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@NRI.RESTON.VA.US.  Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.

RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET,
NISC.JVNC.NET, VENERA.ISI.EDU, WUARCHIVE.WUSTL.EDU, SRC.DOC.IC.AC.UK,
FTP.CONCERT.NET, or NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body 
"help: ways_to_get_rfcs".  For example:

	To: rfc-info@ISI.EDU
	Subject: getting rfcs

	help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute