Adam,

Not exactly... The CE is not using any labels...
The remote PE should signal an explicit NULL label to the penultimate P
router, so that the SP EXP marking would be sent using this label from
the P to the egress PE.
The egress PE then can use the incoming EXP marking to set the egress IP
QOS policy (on cisco platforms done by matching the EXP on ingress and
setting qos-group, which is then used as the match criteria on the
egress IP QOS policy).

On ingress this is just regular operation (like in all modes) - use the
incoming packet (or configure local policy) to mark the imposed EXP
value.

Maybe this document would help:
http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRN
D/VPNQoS.html 

Arie

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Vitkovsky, Adam
Sent: Thursday, August 25, 2011 15:13
To: [email protected]
Subject: [c-nsp] MPLS DiffServ Tunneling Modes -Pipe mode

I was just checking the Cisco IOS Multiprotocol Label Switching
Configuration Guide, Release 15.0M.pdf For the IETF standards based
DS-TE -and kept reading further about the Tunneling modes and that's
where it got interesting

They are referring to Pipe mode as QOS Tunnel that goes form CE to CE
And indeed by that they mean that at ingress the managed CE should
impose an explicit null-label with the EXP set accordingly on packets
sent to PE Than PE should refer to that EXP marking from CE to set the
EXP marking towards the P-core

-just would like to ask the community whether this is now understood as
the part of the pipe-mode setup -cause I've always understood the pipe
mode as PE-to-CE egress scheduling based on the mpls-exp values stored
in the qos-group rather than the accrual ip dscp values


adam

_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to