Re: [CCAMP] draft-ali-ccamp-lsp-inquiry-00

[Khuzema Pithewan <[e-mail]>]

Another point I spoke about in the meeting ..

Why can't we extend Admin Status object to signal resource locking, checking for re-optimization. Since this operation is typically done in maintenance window by Admin, it may make sense to use Admin Status Object. Moreover, we have lots of bits available/undefined in Admin Status object.

This will save network element to manage life of additional LSP and control plane failure related issues attached to the additional LSP.

Khuzema

From: [e-mail] [mailto:[e-mail]] On Behalf Of Khuzema Pithewan
Sent: Tuesday, July 30, 2013 4:25 PM
To: CCAMP ([e-mail])
Subject: [CCAMP] draft-ali-ccamp-lsp-inquiry-00

Authors,

The draft relies on ability to setup GMPLS lsp without committing resources in dataplane.

Only reference I found to setup pre-planned GMPLS is in RFC 6001.

The green highlighted part says it is not possible to support 0 bandwidth lsp for TDM/LSC network. While red part alludes that it can be done.

Also I couldn' locate the text in any RFC that describes the NULL label behavior in GMPLS context.


RFC6001 5.2.2 says

................snip...................

However, mechanisms for provisioning (pre-planned or not) a TDM or
   LSC LSP with 0 bandwidth is currently not possible because the
   exchanged label value is tightly coupled with resource allocation
   during LSP signaling (e.g., see [RFC4606] for a SONET/SDH LSP).  For
   TDM and LSC LSP, a NULL Label value is used to prevent resource
   allocation at the data plane level.  In these cases, upon LSP
   resource commitment, actual label value exchange is performed to
   commit allocation of timeslots/ wavelengths.

.......................snip....................


Khuzema