TCIF (Telecommunications Industry Forum) request

1
TCIF (Telecommunications Industry Forum) request

• Needs MIB support for several objects in order to
  make their info accessible to management stations
• see TCIF-02-004 (09/11/2002), ANSI T1.213-2001
  and T1.213a-2001, T1M1.3
• mailing list discussion initially on atommib and
  later on entmib
• determined that entmib is the most appropriate
  and natural mib module for this support

2
TCIF request

• TCIF Required MIB objects
• Object Suggested mapping
• CLEI Code new object
• Unique Serial Id. (USI) entPhysicalSerialNum
• Software Version entPhysicalSoftwareRev
• Manufacture Date new object
• Manufacturer Id. entPhysicalMfgName
• Manufacturer Product Id. entPhysicalModelName

3
initial straw objects

• entPhysicalCLEICode OBJECT-TYPE        
• SYNTAX OCTET STRING (SIZE (0 10))        
• MAX-ACCESS read-write        
• STATUS current        
• DESCRIPTION 
• "The CLEI (Common Language Equipment
  Identifier)  Code for the physical entity.  If
  the CLEI Code  is unknown, or if no CLEI code
  exists, then this  object will contain a
  zero-length string."        
• REFERENCE   ... refs ...         
• entPhysicalEntry xx
• entPhysicalMfgDate OBJECT-TYPE
• SYNTAX DateAndTime
• MAX-ACCESS read-only
• STATUS current
• DESCRIPTION
• "The manufacturing date for the physical
  entity.
• entPhysicalEntry yy

4
discussion status

• New objects could jeopardize Draft status of
  Entity MIB, but new I-D, AUGMENTING existing
  entmib for just 2 objects, seems overkill
• a) fold into the existing document this may
  jeopardize the entmib going to Draft  
• b) create a supplemental entmib
• c) create a supplemental entmib that will be
  folded into the main document once the specs
  reach the same standardization status
• Zero length string treatment (both objects)
• as proposed, or
• just dont instantiate if value is unknown

5
discussion status (contd)

• Alternative structures of CLEI object
• Dave Perkins suggested use of entPhysicalVendorTyp
  e (or separate object) define a standard OID
  prefix, and encoding of the suffix of the OID.
• Example assume an OID value is assigned with
  descriptor clei", and the encoding is a
  sub-identifier of the decimal value of per
  character in the CLIE code, e.g.,
  entPhysicalVendorType.2 clei.A.B.C.D.F.G.H.I.J.
  K
• Juergen Schoenwalder/Bert Wijnen suggested that
  use of an opaque object just to avoid calling it
  a CLEI object is too complex use simple
  structure instead
• Compliance
• Should not require use of CLEIs for all entities
  rather, if CLEIs are used then use this object

6
appendix - CLEI and USI

• CLEI (Common Language Equipment Identifier) Code 
• Formatted 10 octet string widely used in various
  equipment, line cards, etc.  
• References TCIF-02-004 (09/11/2002), ANSI
  T1.213-2001 and T1.213a-2001, T1M1.3
• Telcordia Technologies is currently the
  designated Maintenance Agent for CLEI Codes
• USI
• Reference TCIF-98-005 and ANSI T1.220