Re: [Mpls-interop] MPLS-TP OAM requirements - Lock and notification oflock

["Adrian Farrel" <[e-mail]>]

Hi Malcolm,

> To address the comments from Adrian I suggest the following
> text for sections 2.2.7 and 2.2.8:
>
> Note that this proposal assumes that the text related to local/remote
> faults is moved from section 2.2.8 to section 2.2.2 as proposed in my
> previous email.
>
> We probably need to discuss this text on the MEAD team call next
> week.
>
> 2.2.7.  Lock
>
> The OAM toolset SHOULD provide a function enabling a network operator to
> administratively shut down a PW, LSP or Section; that is, to stop user
> traffic being sent over that PW, LSP or Section.

This is great.
Does it mean that we do not need to add the (similar) text on CV fault 
behavior in section 2.2.3?
It would seem so.

> The lock function MAY be applied to a unidirectional or a bidirectional
> PW, LSP or Section.  If the lock function is activated at the head end
> of one direction of a bidirectional PW, LSP or Section then it SHOULD be
> possible to cause the lock function to be activated at the head end of
> the other direction.
>
> This function SHOULD be performed on-demand i.e. in response to an
> operator command.

Or also in response to configured automatic behavior?

But this is not a protocol requirement.

> This function SHOULD be performed between End Points of PWs, LSPs
> and Sections.
>
> 2.2.8 Notification of Lock
>
> If the lock function is supported the MPLS-TP OAM toolset MUST
> provide a function to enable the End Point at the ingress to notify the
> End Points at the egress that the lock function is active.  This
> function SHOULD be performed pro-actively.
>
> The MPLS-TP OAM toolset MUST allow for the distinction between
> a fault condition and an administrative locking action.

Works for me.

A