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

[Martin Vigoureux <[e-mail]>]

Dear Huub,

please see in-line.

regards,
martin

Huub van Helvoort a écrit :
> Bonsoir Martin,
> 
> To continue with the othe rquestion:
> 
>> See also my e-mail:
>> MPLS-TP OAM requirements - AIS/LockNotif - Can MIPs send "usolicited" 
>> OAM messages ?
> 
> The answer was no.

[mvx] well, I am not sure about this.

> 
>> -question:
>> More generally to the comment above, who should notify and who should
>> notify whom?
>> I would tend to say:
>> the receiving node of a locked direction, informs downstream receiving
>> nodes of nested LSPs. 
> 
> To be more exact, the sink side of a locked LSP, PW, Section, has to
> inform its clients.

[mvx] Indeed but that is not precise enough, in my view.
Who are the clients? Both end points or only the one downstream?

> 
>> This is a Fowrward Indication and if we do
>> so then receiving points MUST indeed be informed of a Lock (c.f.
>> discussion at the beginning of the e-mail).
>> Should source points (locking points) do some reverse indication and
>> notify the source points of the LSPs that are nested in the locked LSP?
>> (but this maybe falls in the RDI functionality).
> 
> Isn't this notification already caused by the locking at the
> far end?
> Or is the locking only applied in one direction of a bi-directional
> path? If yes, then the notification is not required.

It appear to me that you are mixing the notification at the same
layer and notification at the impacted client layers.
My question was:
in case a Lock is performed at one point I suppose we need to inform
the other end point of that status (same layer)
But then what do these two nodes do? Which node of the locked server
layer inform which node of the impacted clients layer?
> 
> Cheers, Huub.
>