AToM MIB (atommib)

Last Modified: 2003-08-25

Chair(s):
Faye Ly <fayely98@hotmail.com>
Kam Lam <hklam@lucent.com>
Operations and Management Area Director(s):
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Operations and Management Area Advisor:
Bert Wijnen <bwijnen@lucent.com>
Technical Advisor(s):
Mike Heard <heard@pobox.com>
Mailing Lists:
General Discussion: atommib@research.telcordia.com
To Subscribe: atommib-request@research.telcordia.com
Archive: ftp://ftp.research.telcordia.com/pub/Group.archive/atommib
Description of Working Group:
The AToM MIB Working Group is currently chartered to:

1. Maintain and advance on the standards track the existing
    specifications for ATM management (RFC2512-2515).

2. Maintain and advance on the standards track other trunk-mib
    specifications (i.e., for DS0 - DS3-E3, RFC2493-2496).

The objects defined by the working group will be consistent with the
Internet-standard Management framework.
Goals and Milestones:
Done  Revised OpticalMIB Internet-Draft and make available for discussion
Done  Submit the SONET APS MIB to the IESG for consideration as a Proposed Standard
Done  Report on implementation experience on RFC 2558
Done  Submit OpticalMIB Internet-Draft to IESG for standards track elevation
Done  Submit the ATM Supplemental to the IESG for consideration as a Proposed Standard
Done  Report on implementation experience on RFC 2493
Oct 03  Report on implementation experience on RFC 2494
Oct 03  Report on implementation experience on RFC 2495-2496
Oct 03  Report on implementation experience on RFC 2512-2513
Oct 03  Report on implementation experience on RFC 2514-2515
Oct 03  Submit any needed revisions of RFC2495-2496 to the IESG for standards track advancement as appropriate
Oct 03  Submit any needed revisions of RFC2514-2515 to the IESG for consideration of standards track advancement as appropriate
Done  Submit any needed revisions of RFC2493 to the IESG for standards track advancement as appropriate
Done  Submit any needed revisions of RFC2558 to the IESG for standards track advancement as appropriate
Jan 04  Re-evaluate charter or close the WG
Jan 04  Submit any needed revisions of RFC2494 to the IESG for standards track advancement as appropriate
Jan 04  Submit any needed revisions of RFC2512-2513 to the IESG for consideration of standards track advancement as appropriate
Internet-Drafts:
  • - draft-ietf-atommib-atm2-19.txt
  • - draft-ietf-atommib-opticalmib-08.txt
  • - draft-ietf-atommib-rfc2558bis-01.txt
  • - draft-ietf-atommib-rfc2496bis-04.txt
  • - draft-ietf-atommib-rfc2495bis-04.txt
  • - draft-ietf-atommib-rfc2493bis-01.txt
  • Request For Comments:
    Definitions of Managed Objects for the SONET/SDH Interface Type (RFC 1595) (121937 bytes) obsoleted by RFC 2558
    Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2 (RFC 1695) (175461 bytes) obsoleted by RFC 2515
    Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals (RFC 2493) (18749 bytes)
    Accounting Information for ATM Networks (RFC 2512) (29119 bytes)
    Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks (RFC 2513) (60789 bytes)
    Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management (RFC 2514) (37583 bytes)
    Definitions of Managed Objects for ATM Management (RFC 2515) (179993 bytes)
    Definitions of Managed Objects for the SONET/SDH Interface Type (RFC 2558) (138550 bytes)
    Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures (RFC 3498) (78701 bytes)

    Current Meeting Report

    AToM MIB WG meeting Thursday 17/7/03 IETF Vienna
    Reported by Orly Nicklass
    
    
    Status of Current Work
    2495bis (DS1/E1/DS2/E2) -03 and 2496bis (DS3/E3) -03
    passed MIB DR review. Few editorial issues need to be resolved, 
    including
    (1) Reference should point to the forthcoming update of RFC,
    (2) Fix copyright notice,
    (3) Reference in object with citations, and
    (4) Fix long lines (72 columns).
    New drafts will be posted by August time frame.
    
    Presentation was made by Orly showing the changes made since version 01.
    
    draft-ietf-atommib-rfc2495bis-03.txt:
    ds1Compliance, ds1MibT1PriCompliance, and 
    ds1MibE1PriCompliance were deprecated.  New conformance group and new 
    compliance statements were added to reflect the addition of two new 
    objects in the MIB.
    
    draft-ietf-atommib-rfc2496-bis-03.txt:
    dsx3FarEndIntervalCESs-valid data was change to data.
    dsx3FracIfIndex -0 was added to its range for consistency with 
    description. 
    
    In both drafts, the following changes were made between version 2 and 3:
    (1) Wording in the abstract + excluding citations
    (2) Editorial issues concerning: Section titles, References, Security 
    wording, and
    Copyright
    (3) Adding MIN ACCESS to old objects (index)
    
    ATM2 (ATM Supplemental) -19 was approved by IESG with some RFC Editor 
    notes.
    
    2493bis (15-Min. Int. TCs) -01 and 2558bis (SONET) -01 and 
    optical-mib (Optical) -08 are on the RFC queue.
    
    Implementation Feedback
    RFC 2495:
    Only Two replies were received, and both do not fully implement all 
    objects. 
    Either one does not implement the following:
    ds1FarEndGroup,   ds1DS2Group, and   dsx1ChanMappedIfIndex      
    Only one implement the following:
    dsx1InvalidIntervals,    dsx1CurrentSEFSs,  dsx1CurrentPCVs,  
    dsx1IntervalSEFSs, dsx1IntervalPCVs, 
    dsx1IntervalValidData,     dsx1TotalSEFSs,     dsx1TotalPCVs, and             
    dsx1LineStatusChangeTrapEnable  
    
    Both implement the rest.
                     
    RFC 2496
    Only Two replies were received, and both do not fully implement all  
    objects.
    Either one does not implement the following:
    dsx3FarEndCurrentIndex ,   dsx3FarEndTimeElapsed, 
    dsx3FarEndValidIntervals  dsx3FarEndCurrentCESs , 
    dsx3FarEndCurrentCSESs    dsx3FarEndCurrentCCVs, 
    dsx3FarEndCurrentUASs, dsx3FarEndInvalidIntervals 
    dsx3FarEndIntervalIndex   dsx3FarEndIntervalNumber  
    dsx3FarEndIntervalCESs    dsx3FarEndIntervalCSESs   
    dsx3FarEndIntervalCCVs    dsx3FarEndIntervalUASs    
    dsx3FarEndIntervalValidData dsx3FarEndTotalIndex      
    dsx3FarEndTotalCESs       dsx3FarEndTotalCSESs      
    dsx3FarEndTotalCCVs       dsx3FarEndTotalUASs       
    
    Only one implement the following:
    dsx3CircuitIdentifier     dsx3InvalidIntervals      
    dsx3Ds1ForRemoteLoop      dsx3IntervalValidData  
    dsx3FarEndLineIndex       dsx3FarEndEquipCode       
    dsx3FarEndLocationIDCode  dsx3FarEndFrameIDCode     
    dsx3FarEndUnitCode        dsx3FarEndFacilityIDCode  
    dsx3LineStatusChangeTrapEnable  
    
    Both implement the rest.
    
    RFC 2512, RFC 2513: No reply has been received and no comments on the list
    
    RFC 2514 (TC) 
    Three replies were received.
    
    No implementation was reported for the following TC:
    AtmIlmiNetworkPrefix 	AtmInterfaceType 
    	AtmSigDescrParamIndex 
    
    Single implementation was reported for the following TC:
    AtmAddr 
    			
    RFC 2515 
    Three replies were   received.
    
    No implementation was reported for the following:
    atmTrafficFrameDiscard      atmInterfaceOCDEvents   
    atmInterfaceTCAlarmState     
    atmVplAdminStatus   
    
    Single implementation was reported for the following:
    
    AtmInterfaceSubscrAddress	atmTrafficDescrParamIndexNext
    
    atmInterfaceDs3PlcpSEFSs	atmInterfaceDs3PlcpAlarmState   
    atmInterfaceDs3PlcpUASs	atmVplOperStatus        
    atmVplLastChange
    
    atmVplCrossConnectGroup	atmVpPvcCrossConnectGroup         
                    
    
    	        
    Suggestion:
    It was decided to extend the time and request additional 
    implementation report for all of the above. RFC 2512 and RFC 2513 will go to 
    historic if no response will be given by new due date.	
    RFC 2514 and RFC 2515 will either be split for advancement or the 
    additional information will allow it to advance all together.
    RFC2495 will recycle at PS, RFC 2496 depends on the result of the 
    additional reports.
    
    Future topics
    It was decided to request implementation report for RFC 2494.
    VCAT and IMA modification will be pursue via the list first.
    The WG chair will issue a mail on VCAT trying to generate some interest in 
    the group and will contact Andy from ATMF for future work on IMA MIB.
    
    Charter dates will be updated according to the decisions in the 
    meeting.
    

    Slides

    Changes from draft 01 to 02