[Mpls-interop] Local and Remote

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

I know that Malcolm and Huub are going to work on the definition of local 
and remote.

Huub usefully typed during the meeting yesterday that "remote" might be 
better stated as "non-local."

Watching some emails this morning, I wonder whether part of the confusion 
arises from
- where the fault is detected
- where the fault exists

A node can (IMHO) only be detected locally. That is local to the point of 
detection.

A fault may be reported (to the management plane) from the node of detection 
(a local report), or may be signaled to another node (through the OAM or 
control plane) and reported (to the management plane) from that other node 
(a remote report).

The fault that is detected may be in the detecting node, or in a resource 
directly connected to that node (such as a link). This is a local fault.

But the fault may also exist in a node or resource that is not local to the 
detecting node. This is a remote fault.

If an LSP continuity check fails, the fault is detected by an end point 
(local detection), but the fault might be somewhere out in the network 
(remote fault).

When a server layer provides a connection that is used as a link in the 
client layer, a server layer fault (that is remote in the server layer) may 
be reported to the client layer as a fault in the client layer link (that is 
local in the client layer). The client layer does not know about the route 
or resources used in the server layer (we MUST assume clean layer 
separation) so the client layer does not need to know about the location of 
the server layer remote fault. If the client layer requests the server layer 
to repair the client layer link (i.e. to repair the server layer connection) 
the server layer may need to consider the location of the server layer 
fault.

Am I wrong?
Is this really so complicated?

Thanks,
Adrian