[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I-D ACTION:draft-ayyangar-ccamp-lsp-stitching-00.txt

arthi

Arthi Ayyangar wrote:

Igor, Dimitri,


IB>> I have a comment here. LSP-Hierarchy is not a Bible and could be
challenged in many ways. FA LSP is, generally speaking, created on a layer
boundary rather than on region boundary: nothing prevents creating a VC4 FA
LSP that starts and stops in the middle of TDM region to carry several VC12
LSPs. Furthermore, stitching FA is a special case of FA when it is used by
LSPs of the same layer as one where the FA-LSP was created. As for triggers,
there could be multiple ones for setting up/tearing down stitching FA-LSPs:
configuration, receiving setup request for inter-domain LSP, other policies.


AA>--------> I agree...in fact I also absolutely agree that LSP segment
end points do NOT have to be domain boundaries. In fact there could be
other reasons for creating LSP segments spanning a bunch of nodes...one
application that has also been refered to in the document, say P2MP, for
preventing legacy LSRs from being in the path of P2MP tunnels.

for this specific point of stitching segments to "tunnel" P2MP branches, i thought we would make use of the node capability flags to determine the head and tail-end of the segment - is that assumption still being considered ?

thanks,
- dimitri.

thanks,
-arthi


.