The MPLS WG Archive

[Joan Cucchiara x302 <jcucchiara@Artel.com>]

> -----Forwarded Message-----
> From: "M. ELK" <elkou141061@hotmail.com>
> Sent: Oct 16, 2003 10:24 AM
> To: mpls@UU.NET, mpls-ops@mplsrc.com
> Subject: LDP LSP FEC Table Index -  LDP MIB draft ver 13 
> 
> 
> Hi
> 
> 1- The index of LDP LSP FEC Table is given by :
> 
>         INDEX { mplsLdpEntityLdpId,
>                       mplsLdpEntityIndex,
>                       mplsLdpPeerLdpId,
>                       mplsLdpLspFecSegment,
>                       mplsLdpLspFecSegmentIndex,
>                       mplsLdpLspFecIndex
>                      }
> 
> Could it be :
> 
>         INDEX { mplsLdpEntityLdpId,
>                       mplsLdpEntityIndex,
>                       mplsLdpPeerLdpId,
>                       mplsLdpLspFecIndex
>                       mplsLdpLspFecSegment,
>                       mplsLdpLspFecSegmentIndex,
>                                           }
> 
> my guess the above is logical where for certain PEER Peer1 :  
> for each FEC 
> the In and out segment pointer is listed in 2 sucessive entry .

The current indexing allows an LDP LSP, with Insegment and/or Outsegment, 
to one or more FECs.

> 
> 2- actually my requirement that knowing mplsLdpLSPFecIndex 
> associated by 
> FEC1 , i need to get
> the In-Segment stat and Out-Segment stat fast enough so the ideal :
> 
>   INDEX { mplsLdpLspFecIndex
>                      mplsLdpEntityLdpId,
>                       mplsLdpEntityIndex,
>                       mplsLdpPeerLdpId,
>                       mplsLdpLspFecSegment,
>                       mplsLdpLspFecSegmentIndex,
>                                           }
> 
> From LDP LSP Table description :
>         DESCRIPTION
>            "A table which shows the relationship between  LDP 
> LSPs and FECs. 
>   Each row represents
>            a single LDP LSP to FEC association."
> 
>        Could it be :
> 
> DESCRIPTION
>            "A table which shows the relationship between  
> FECs and LDP LSPs 
> .  Each row represents
>            a single  FEC to LDP LSP association."
> 

I am unclear how the alternative indexing you propose will
help obtain the InSegment and OutSegment statistics any faster.  
That aside, the current tables are designed to allow a FEC to be
assigned to zero, one or more LDP LSP Segments (if that is so configured), 
or one LDP LSP Segment to one or more FECs (if that is so configured), so
these tables are flexible.  The change you are proposing is less
flexible, so would rather keep the flexibility.

You could create a table in an enterprise MIB with the indexing
you propose.

  -Joan

> 
> Brgds
> 
> _________________________________________________________________
> Add photos to your messages with MSN 8. Get 2 months FREE*. 
> http://join.msn.com/?page=features/featuredemail
> 
> 
> 
>