Re: Questions re current sonetng, atm1ng and atm2TC drafts

Kaj Tesink <kaj@cc.bellcore.com> Tue, 24 March 1998 19:29 UTC

Delivery-Date: Tue, 24 Mar 1998 14:30:01 -0500
Return-Path: aileen@thumper.bellcore.com
Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id OAA08137 for <ietf-archive@ietf.org>; Tue, 24 Mar 1998 14:29:54 -0500 (EST)
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id OAA08378 for <ietf-archive@cnri.reston.va.us>; Tue, 24 Mar 1998 14:32:24 -0500 (EST)
Received: from tbird.cc.bellcore.com (tbird.cc.bellcore.com [128.96.96.114]) by thumper.bellcore.com (8.8.8/8.8.8) with SMTP id MAA02229 for <atommib@thumper.bellcore.com>; Tue, 24 Mar 1998 12:11:13 -0500 (EST)
Received: from joker (joker.bellcore.com) by tbird.cc.bellcore.com with SMTP id AA21676 (5.67b/IDA-1.5 for <atommib@thumper.bellcore.com>); Tue, 24 Mar 1998 12:17:04 -0500
Received: from kaj-1 (nv-ktesink.cc.bellcore.com) by joker (4.1/4.7) id AA06726; Tue, 24 Mar 98 12:14:15 EST
X-Station-Sent-From: joker.bellcore.com
Message-Id: <9803241714.AA06726@joker>
X-Sender: kaj@joker.bellcore.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Tue, 24 Mar 1998 12:13:28 -0500
To: peter@aus.atmospherenet.com
From: Kaj Tesink <kaj@cc.bellcore.com>
Subject: Re: Questions re current sonetng, atm1ng and atm2TC drafts
Cc: John Neil <jn@aus.atmospherenet.com>, atommib@thumper.bellcore.com
In-Reply-To: <3515DF5E.3E894AD0@atmospherenet.com>
References: <9803201343.AB05622@joker>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 12:04 PM 3/23/98 +0800, Peter Jones wrote:
>Hi Kaj,
>
>Kaj Tesink wrote:
>> 
>> hi peter,
>> 
>> thanks for your mail; good points; i'll forward some of it to the quality review
>> process folks so that we can fix any problems.
>> 
>> some observations:
>> - on your sonet mib suggestion to add a trap:
>>   i appreciate the desire of alignment but have you thought of simply
>>   sending the line status object along with linkUp/Down traps?
>>   the sonet mib is under quality review and i prefer to make minor
>>   changes only.
>> 
>
>I don't think sending extra objects along with a linkUp/LinkDown trap is
>an acceptable solution. Our experience is that this usually results in
>interworking problems with other managers and devices. I think that the 
>linkUp/linkDown traps provide a differnet service that the
>dsx1LineStatusChange
>type traps.

i thought you would say this.
any folks out there who would second this request
"to align the sonet/sdh mib with the other trunk mibs
regarding this trap"?

>
>We are trying to build a "unified" infrastructure forhandling "telco"
>type alarms notification, and want to use the facilities from the
>standard MIBs wherever possible. The dsx1LineStatusChange Notification
>is a good fit for what we want. As far as the sonetng mib goes, it
>already has the objects that contain the status bits, all that is
>missing is a standard way to notify this to a management application
>(whether local to the device or remote).
>
>
>> - on your observation that the various atm mibs seem to IMPORT from
>>   each other: i thought that was fixed a long time ago. i know
>>   i made some changes because of that. well, obviously we need to check this
>>   and fix as result of the quality review process.
>> 
>
>Regarding the importing, atm2TC does not directly import from atm1ng, it
>cheats.
>
>For instance:
>1)	The MODULE-IDENTITY clause from atm2TC really is { atmMIB 3 } which
>	is in atm1ng. The specification using { mib-2 37 3 } ducks around 
>	the problem that the  mib-2 37 is defined in atm1ng. Our MIB 
>	compiler complains that atm1ng is redefining an OID already 
>	specified in atm2TC.
>               atmTCMIB MODULE-IDENTITY
>                    ::= { mib-2 37 3 } -- atmMIB 3

i'll look into it; i thought we got it fixed but will check

>
>2)	A similar problems exists for the traffic descriptor types, 
>	with the {atmMIBObjects 1} branch being moved from atm1ng 
>	to atm2TC. The same techniques is used to get around the 
>	issue, by specifying 
>	atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1}.
>	This causes us the same problem when compiling atm1ng where our
>	compiler says that atmMIBObjects (i.e. mib-2 37 1) has already 
>	been defined in atm2TC. 

hadnt seen this one before

>
>That's the essence of what I am complaining about. Hooking the OIDs
>defined
>in atm2TC onto the subtree defining in atm1ng is not good.

will check
>
>
>> - your question on the status of the mibs:
>>   atm1ng and atmtc: have been quality reviewed - i'm waiting to hear from the
>>   area director. i'll ping him. then we do the fixes and that  should be it.
>>   atm2: you have seen the new draft (thanks for your comments).
>>   mickey wants to make one more update.
>>   accounting mibs: have been quality reviewed - i'm waiting to hear from the
>>   area director. i'll ping him.
>> 

>> hope you're up-to-date again,
>> 
>> thanks for the feedback,
>> 
>> kaj
>
>regards
>peter
>
>
>-- 
>______________________________________________________________________
>Peter Jones                           Atmosphere Networks
>Manager of Software Development       4th Floor, Balcroft Building
>                                      Garden Office Park
>                                      345 Harborne Street
>                                      Osborne Park WA 6017, Australia
>Direct: +61 (8) 9443 0105             Main: +61 (8) 9443 0100
>                                      Fax:  +61 (8) 9443 6610
>mailto:peter@atmospherenet.com        http://www.atmospherenet.com
>_______________________________________________________________________
> 

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
_/                                                                      _/
_/  Kaj Tesink                                                          _/
_/  Bellcore                                                            _/
_/  Business Internet Professional Services  vmail (732) 758-5254       _/
_/  331 Newman Springs Rd.                   email kaj@cc.bellcore.com  _/
_/  Red Bank, NJ 07701                     faxmail (732) 758-2269       _/
_/                                                                      _/
_/  * NOTE AREA CODE CHANGE (908) --> (732) EFFECTIVE JUNE 1, 1997 *    _/
_/                                                                      _/
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/