The MPLS WG Archive

[Curtis Villamizar <curtis@fictitious.org>]

In message <3DFD4C10.6D83A84C@alcatel.com>, "Cheng-Yin Lee" writes:
> Neil,
> > Now whilst the above does at least agree that the control-plane must not
> > proxy for missing data-plane functionality (and its taken a while to even
> > get this bit recognised as required), it still fudges the client/server
> > data-plane layer network relationships.  This is not a good idea for PWE3
> > applications say where the MPLS client can vary.  Ideally one wants the
> > *same* solution/behaviour for all client (or server) layer cases (and all
> > control-plane cases...inc case of 'none', ie static trails).
> Is there a requirement to test the data plane liveliness from ideally
> the input
> interface of the ingress PE to the output interface of the egress PE for
> PWE3 applications?
> 
> thanks
> cheng-yin


If the PWE3 application is non-IP then you can test up to the egress
LSR and no further.  The same would be true for an IP VPN.  For
example, you can't inject test traffic into someone's TDM leased line
without corrupting the data flow.  That part of the LSP forwarding is
not tested.  That was my point in an earlier statement I made on this
thread.

Curtis