[j-nsp] Use cases for IntServ in MPLS backbones

Mark Tinka mark.tinka at seacom.mu
Tue Oct 2 06:33:23 EDT 2018



On 2/Oct/18 12:26, Saku Ytti wrote:

> I don't think so, If they use DSCP values as-is, then they MUST
> nullify them. Full and short pipe assume you use MPLS TC for internal
> decision, at which point you don't need to care or trust DSCP. If you
> use DSCP internally _AND_ trust Internet DSCP, it's broken
> configuration.

We only use MPLS EXP in the core (for IPv4). At the edge, we use DSCP.

For IPv6, we use DSCP in the core since we are not forwarding IPv6
traffic in MPLS yet.


> It is indeed possible to misconfig things. But it's not the problem of
> instance sending DSCP, it's problem of the instance having broken
> config based on DSCP.

So what is easier to fix? Agreeing on a global standard for what DSCP
values to use in our own internal networks?

Did you see how how well BCP-38 and uRPF deployment have gone globally?

Mark.


More information about the juniper-nsp mailing list