Christian Hopps <[email protected]> wrote: > This is a good question. We currently indicate it's a local > configuration decision, but we may want to go deeper into possible > options in the draft.
> Right now we see 3 options:
> - A static configured value for the SA
> - Inherit the "best" value from the encapsulated traffic.
The DSCP value is only meaningful within an AS.
The end points of the tunnel and the outside of the tunnel are really
different diffserv domains.
The ECN markings are in the same byte, and we do things with that, but
that's not the DSCP.
Changing the DSCP would seem to enable traffic analysis.
As TFS needs to do congestion control, I think that the ECN markings should
be used by TFS, and TFS should do ECN markings upon entry/exit of the tunnel
itself, after some processing itself. It might mark congestion seen more
often than the outside of the tunnel sees if it needs the users of the tunnel
to back down because they are exceeding the allocation.
It might also ignore congestion if the congestion is due to the extra traffic.
So I think that the DSCP needs to be configured appropriately for the AS
that is sending the packets.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
signature.asc
Description: PGP signature
_______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
