requirement
Click on the red underlined text to get to the source
... transport protocol uses the TOS
requested by the application. There is no requirement that both
ends of a transport connection use the same TOS ...
... an overview. Implementors should consult the Router Requirements
specification [3] and the the specifications of the routing
protocols ...
... bits wide rather than five bits wide.
The requirements that refer to the TOS field should refer
only to the four bits ...
... These details will presumably be corrected in the next revision of
the Host Requirements specification, at which time this appendix
can be considered obsolete.
...
... number of participants in the IETF's Router Requirements Working
Group felt it would be important to have a TOS value which would
...
... TOS values) and would be
consistent with Host Requirements, but would reduce to one the
number of reserved bits in the IP header ...
... that consistency with Host Requirements was inadequate
justification for unnecessarily increasing the size of the TOS
...
... Internet Engineering Task Force (R. Braden, Editor), "Requirements for Internet Hosts -- Communication Layers", RFC 1122std3 ...
... Internet Engineering Task Force (R. Braden, Editor), "Requirements for Internet Hosts -- Application and Support", RFC 1123std3 ...
... held by the IETF's Router Requirements Working Group. Much of the
specification of the treatment of Type of Service ...
... a restatement of the ideas of the IETF's former Host Requirements
Working Group, as captured in RFC-1122std3 ...
... Gross, Bob Hinden, Steve Huston, Jon Postel, Greg Vaudreuil, John
Wobus, and the Router Requirements Working Group.
...