The MPLS WG Archive

[Nuno Silva <NunoS@ptinovacao.pt>]

Neil et all, 

 Under the scope of G.805 (March 2000), do you think it makes sense to model
an LSP as a Network Connection, composed by a concatenation of SNCs and LCs
(if so, what would be the subnetwork connections, the link connections, the
TTPs and CTPs), or as an IP trail?

 TTPs - are the IP interfaces/ports?
 CTPs- are the labels?
 LCs - are the connections/associations between 2 labels in two different
LSRs?
 SNCs- are the forwarding tables in the LSRs and LERs? (a connection between
the TTP and CTP in the LER, or a connection between CTPs in the LSRs)?

 So the question is indeed, is the functional architecture defined in G.805
applicable to the MPLS/MPlambaS worlds?
 How does this cope with G.cls (connectionless) work?

 Thanx ahead. Nuno.
 


Nuno Carvalho Silva
PT Inovação, SGR

Phone: + 351 234 403 394
Fax: + 351 234 424 160
E-mail: nunos@ptinovacao.pt

> -----Original Message-----
> From:	neil.2.harrison@bt.com [SMTP:neil.2.harrison@bt.com]
> Sent:	Wednesday, December 06, 2000 10:07 PM
> To:	Juergen.Heiles@icn.siemens.de; jdrake@calient.net; mpls@UU.NET
> Cc:	ip-optical@lists.bell-labs.com
> Subject:	RE: [IP-Optical] GMPLS - Hierarchies
> 
> <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 
> 
> > 	
> 
> _______________________________________________
> IP-Optical mailing list
> IP-Optical@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/ip-optical