The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2006-May> msg00063



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

[mpls] About "MplsIndexType"

  • From: "Roby (Hu Ruoheng)" <huruoheng@huawei.com>
  • Date: Thu, 18 May 2006 09:49:14 +0800
  • X-Mailman-Approved-At: Thu, 18 May 2006 11:32:15 -0400

Hello everyone:
 
    Here comes a question about mpls mib. Please give me some advice.
    Now we are using a MIB named MPLS-LSR-STD-MIB (from rfc3813).In this MIB, there is a TC defined as follow:
 
 
 
    MplsIndexType ::= TEXTUAL-CONVENTION
        STATUS              current
        DESCRIPTION
            "This is an octet string that can be used as a table
             index in cases where a large addressable space is
             required such as on an LSR where many applications
             may be provisioning labels.
   
             Note that the string containing the single octet with
             the value 0x00 is a reserved value used to represent
             special cases. When this TEXTUAL-CONVENTION is used
             as the SYNTAX of an object, the DESCRIPTION clause
             MUST specify if this special value is valid and if so
             what the special meaning is.
   
             In systems that provide write access to the MPLS-LSR-STD
             MIB, mplsIndexType SHOULD be used as a simple multi-digit           <====  What is "multi-digit integer" ?
             integer encoded as an octet string.
             No further overloading of the meaning of an index SHOULD
             be made.
   
             In systems that do not offer write access to the MPLS-LSR-STD
             MIB, the mplsIndexType may contain implicit formatting that is
             specific to the implementation to convey additional
             information such as interface index, physical card or
             device, or application id. The interpretation of this
             additional formatting is implementation dependent and
             not covered in this document. Such formatting MUST
   
             NOT impact the basic functionality of read-only access
             to the MPLS-LSR-STD MIB by management applications that are
             not aware of the formatting rules."
        SYNTAX                OCTET STRING (SIZE(1..24))
 
 
 
 
    We don't know how to display a table index in this type . This TC is to describe an mpls label, and it should be follow the objects in the table.
We think there are two ways:
 
For example, to respond the mplsInSegmentInterface node in the mplsInSegmentTable with mplsInSegmentIndex as index, and the index value is 1025.
 
1   mplsInSegmentInterface.4.1.0.2.5 = InterFaceNo1         The value 1025 is separated into four number and add index's length para before them.
 
2   mplsInSegmentInterface.3.4.0.1 = InterFaceNo1           Convert the number 1025 into hex and each byte correspond to an oid space , then also add index's length para before them.
                                                            (decimalist 1025 = hex 401)
 
 
I'm inclined to the first solution. What is your opinion ? Both wrong or one of them is correct ?
 
Waiting for your respond. Thank you very much.
 
 
_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls