The MPLS WG Archive

[neil.2.harrison@bt.com]

<snipped>

> Furthermore a LSP -at least for circuit switching - doesn't have to start
> and end at the trail termination where you extract your payload.
	NH=> I fudamentally disagree *if* we are adhering to functional
arch. 
>  A LSP could be used only for a sub part of the overall connection, e.g. a
> DS1 signal starts in a user domain with tradional TMN path setup or even
> manual connections, the DS1 comes to a operator which uses GMPLS for path
> -setup (in this case a permanent connection set-up by himself as the user
> doesn't support the UNI). The LSP starts in the middleof the overall DS1
> connection and no access to the paylaod of the DS1 is requried at that
> point.
	NH=> The DSI signal is 'an LSP' in its own right......it is, after
all, a clear layer network trail entity.  The fact that it may be served (on
link connections, which are a partition of the end-end DS1 trail) by lower
layer "LSPs" (which could be a DS3, VC4, ODU, etc.......and which themselves
are trails *but* only between their points of source/sink) is
academic.....the DS1 trail is completely unaware of this, and the layering
recursion of client_links=>server_trails can recurse many times.......its
stops at the duct network.
	Your example *must*, and indeed does, fit this. 
	neil 

>