The MPLS WG Archive

["Cucchiara, Joan" <JCucchiara@Brixnet.com>]

Bill,

This issue was raised during the last call
of the LSR MIB by yours truly.  

I agree with you that the OutSegment Table should 
ifIndex and OutLabel as indices.   Also, this would
mean that the XC Table would change to include these
as indices also. 

Was this change to the OutSegment and XC Tables 
overlooked?  

   Thanks, Joan


> -----Original Message-----
> From: Friedeborn, William [mailto:billf@netplane.com]
> Sent: Friday, November 17, 2000 2:23 PM
> To: 'mpls@uu.net'
> Subject: re: LSR MIB, OutSegment Index
> 
> 
> I've been working with the LSR and TE MIBs for a while and 
> have run into
> some implementation problems with the OutSegment objects. In 
> a monolithic
> environment it is pretty straight forward to implement the 
> OutSegment table.
> However, in a distributed environment, this is quite challenging.
> 
> What is the reasoning behind using an IndexNext object to get 
> the OutSegment
> Index? The InSegment table is indexed by IfIndex and Label, 
> which makes it
> very easy to distribute. I can look at the ifIndex and know 
> what line card
> has the InSegment object. On the other hand the OutSegment 
> table only has
> the abtract OutSegmentIndex. I would have to go to each line 
> card to find
> out which one has that index, or maintain lists of indexes to 
> ifIndexes on
> each line card.
> 
> It just seems like an added indirection that creates more 
> complexity. Am I
> missing something here?
> 
> Thanks,
> Bill
>