On 3/8/24, 22:02, "Nnagain on behalf of David Lang via Nnagain" <[email protected] <mailto:[email protected]> on behalf of [email protected] <mailto:[email protected]>> wrote:
> In practice, priority bits are ignored on the Internet. There are no legal limits on what bits can be generated, and no reason to trust priority bits that come from a different network. > As I understand the current state of the art, best practice is to zero out priorities at organizational boundries [JL] Quite true: each network tends to use DSCP marks on a private/internal basis and so will bleach the DSCP marks on ingress from peers. This will, however, change with the upcoming IETF RFC on Non-Queue-Building (NQB) Per Hop Behavior - https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-nqb. And I can report that we at Comcast now permit DSCP-45 inbound for NQB packets, in case developers would like to experiment with this (we just finished updating router configs last week for residential users on DOCSIS; FTTP and commercial are still in process). _______________________________________________ Nnagain mailing list [email protected] https://lists.bufferbloat.net/listinfo/nnagain
