Allow specifying the traffic class when using traceroute6
ClosedPublic
Actions

In the man page, do we want to refer to RFC2474 and RFC3168, so that people are at least warned when the tos / tclass bytes are using not only the DSCP field, but also the ECN codepoints in ping / ping6 / traceroute / traceroute6?

This revision is now accepted and ready to land.Sep 12 2020, 9:10 PM

In D26410#587502, @rscheff wrote:

In the man page, do we want to refer to RFC2474 and RFC3168, so that people are at least warned when the tos / tclass bytes are using not only the DSCP field, but also the ECN codepoints in ping / ping6 / traceroute / traceroute6?

In my view the Traffic Class is an 8-bit field. It can be split in 6 bit DSCP and 2 bit ECN, but that is one option of using it. That is why it is called Traffic Class. RFC RFC 8200 is clear on this, I think.

Therefore, the short answer to your question is: no.

Closed by commit rS365685: Add a -t option to traceroute6 to control the traffic class used when (authored by tuexen). · Explain WhySep 13 2020, 9:00 AM

This revision was automatically updated to reflect the committed changes.

tuexen added a commit: rS365685: Add a -t option to traceroute6 to control the traffic class used when.