[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
About LSP Stiching
In the draft draft-ietf-ccamp-lsp-stitching-00 for LSP stitching, I think one more extension may be needed for E2e LSP.
The draft suggest 2 main extensions,LSP Stitch desired bit and LSP Stitch Ready Bit.
Both these extensions are for LSP Segement LSP.
An LSP Segment will be treated like any other TE-Link.
So TE-Link type will be hidden from E2e LSP.
There is no way for LSP segment head node, to identify that a Outif selected is a LSP Segment for setting up E2e LSP.
That is Some extension will be needed to RSVP that will allow RSVP message(for E2e LSP) processing at LSP segment head node to be processed according to the Sticthing needs.
For Eg: LSP1-2 is an E2e LSP setup over an LSP segment LSPA-B.
Now if A gets the Path message for LSP1-2, and A selects LSP segment LSPA-B as outif.
Then how does RSVP(at Node A) identify that the outif selected is a LSP segment?
Also when A receives Resv for LSP1-2(from B), how can it ignore Label in it.
There should be a way to determine at node A, that a LSP segment is in use.
One possible way could be that Resv message for LSP1-2 should be sent(by B) with some special Label value.
This Label value should indicate the node A that the Resv is received for a TE-Link(of type LSP Segment).
This will help node A to ignore Label value in Resv msg for E2e Lsp LSP1-2.
Plz let me know your view.
Thanks in advance.