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

[Huub van Helvoort <[e-mail]>]

Hello Martin,

You wrote:

> Malcolm,
> 
> I fully agree that the lock is performed locally.
> I also agree that the other end point must be aware of this lock.
> This is exactly what I have written below.
> 
> On bidir LSP the notification may be used to request the lock
> at the far end but this is for me an implementation decision.
> We should, as agreed during the call, stick to elementary
> functionalities.
> Therefore we need two distinct functionalities:
> inform the far end that lock has been performed
> request the far end to perform lock
> 
> do we agree on that?

Not replying for Malcolm, but sharing my own opinion:
Yes, I agree.

> one functionality I believe we also need is to inform client
> layers of the lock condition of a server, but I'll discuss
> this in the other e-mail you sent.

Is it necessary to be so  specific?
It should be sufficient to notify the client layer that
the path/trail is not usable, without telling the reason.
The only purpose of the notification is that the client
layer need not to take any fault locating actions.

(This is the same as my answer to Malcolm some minutes ago)

Best reagrds, Huub.

-- 
================================================================
Always remember that you are unique...just like everyone else...