The default behavior can be "immutable", which I think would satisfy the concerns I hear. But restricting all possible (including future ones) flow setup and flow processing mechanism to "immutability" is too much.
Alex Brian E Carpenter wrote: > > Tony Hain wrote: > > > > Alex Conta wrote: > > > Furthermore, the > > > restriction has a detrimental effect on the subset of > > > applications that > > > could take advantage of a changing value. > > > > I am sorry, but those applications should be using the DSCP which is > > already mutable. If we allow the FL to be mutable, there will be no > > applications that can trust that it will immutable over any random > > network. You can't have it both ways. > > Exactly. And operators who break the immutability rule will penalise > their own customers by depriving them of e2e QOS. > > There was a reason diffserv chose to make the DSCP mutable, but the same reason > (QOS policies are ISP-specific) is why the flow label should be immutable. > > Brian
smime.p7s
Description: S/MIME Cryptographic Signature
