The MPLS WG Archive

["Kannan S (Networking) - CTD, Chennai." <kannans@ctd.hcltech.com>]

Hi,

Can somebody tell me what I am missing here ?

I was wondering if makes sense to have 
mplsInSegmentXCIndex object in MplsInSegmentEntry as read-create and
remove the <mplsInSegmentIfIndex, mplsInSegmentLabel> from the mplsXCEntry
INDEX.

I am asking this because, 
In multiple insegment entries cross connected with one outsegment entry
case, it works fine.
if we use multiple outsegment entries, we need to create multiple cross
connect entries with all possible combinations, also provide administrative
control to enable / disable each of the combinations. 
Isnt it good enough to say - these are the InSegments that belong to the
<LSP/Crossconnect Index>, and these are the <OutLabelStack +
OutSegmentEntry> (XCEntries) entries for the <LSP / Crossconnect Index> ...
and let the LSR use whatever mechanism to choose which of the <OutLabel +
OutSegmentEntry> entries to use.

I am trying to reason out the rationale behind the current design ..

Is it because administrative control (disable / enable) is required at
various combinations / preclude certain combinations of In and Out segment
entries ?

Or is it this way because it is more readable ?

I understand we wont be able to call it XC , if we made the change.
I also understand that I could internally maintain it anyway, as long as I
am able to provide the interface.


TIA,
Kans.