[c-nsp] MPLS DiffServ Tunneling Modes -Pipe mode

[Oliver Boehmer (oboehmer)]

Well, actually the doc refers to a feature where you can move all
IP-DSCP-based classification off the PEs. So if you classify on the CE
and mark with the exp-null label, the ingress PE can use this marking
and doesn't need to configure any customer/IP-specific policies. 
So I would argue that using exp-null on the ingress CE/PE is not a
requirement for a pipe-mode deployment, but it makes the deployment
easier.  And no, I have not yet seen this being deployed (which might or
might not mean something)

	oli

> 
> Right that's how I understood it as well
> It's just that document proposing the rather unusual way :)
> 
> adam
> 
> -----Original Message-----
> From: Arie Vayner (avayner) [mailto:avayner at cisco.com]
> Sent: Thursday, August 25, 2011 2:36 PM
> To: Vitkovsky, Adam; cisco-nsp at puck.nether.net
> Subject: RE: [c-nsp] MPLS DiffServ Tunneling Modes -Pipe mode
> 
> 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: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Vitkovsky,
Adam
> Sent: Thursday, August 25, 2011 15:13
> To: cisco-nsp at puck.nether.net
> 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  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/