The specification for Socket.setTrafficClass includes this statement:

  "The TOS field is bitset created by bitwise-or'ing values"

but also references RFC 1349 but that RFC redefines TOS as follows:

   "Because this specification redefines TOS values to be integers rather
   than sets of bits, computing the logical OR of two TOS values is no
   longer meaningful. For example, it would be a serious error for a
   router to choose a low delay path for a packet whose requested TOS
   was 1110 simply because the router noted that the former "delay bit"
   was set."

We should correct this in the spec.