> The client echoes the complement of the last seen bit when sending packets to the server. Since neither the client or server care about this big, there doesn

> The client echoes the complement of the last seen bit when sending packets to the server. Since neither the client or server care about this big, there doesn't appear to be anything that forces the client to actually implement this behavior. The client could always set it to 0 or even set it (pseudo-)randomly on each packet. The bit shouldn't exist, but if the IETF did add it to the standard, would hostile middleware boxen actually start drooping packets if they don't see the "spin bit" change?