Re: Q: modifying a varible in atmTrafficDescrGroup

dxie@mtgbcs.mt.lucent.com Mon, 14 April 1997 22:49 UTC

Received: from cnri by ietf.org id aa10935; 14 Apr 97 18:49 EDT
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa22557; 14 Apr 97 18:49 EDT
Received: from algw1.lucent.com (algw1.lucent.com [205.147.213.1]) by thumper.bellcore.com (8.8.5/8.8.5) with SMTP id SAA00408 for <atommib@thumper.bellcore.com>; Mon, 14 Apr 1997 18:17:57 -0400 (EDT)
From: dxie@mtgbcs.mt.lucent.com
To: Sherry Yang <yangs@nortel.ca>, ATM bulliten <atommib@thumper.bellcore.com>
Received: from mtgbcs.mt.lucent.com by alig1.firewall.lucent.com (SMI-8.6/EMS-L sol2) id SAA02578; Mon, 14 Apr 1997 18:30:46 -0400
Received: from mtpcs52-102 by mtgbcs.mt.lucent.com (5.0/EMS-L sol2) id AA23130; Mon, 14 Apr 1997 18:19:04 -0400
Message-Id: <970414172556.ZM2839@mtpcs52-102>
Date: Mon, 14 Apr 1997 17:25:54 -0400
In-Reply-To: "Sherry Yang" <yangs@nortel.ca> "Q: modifying a varible in atmTrafficDescrGroup" (Apr 1, 6:09pm)
References: <3341BFC6.6EEA4806@nortel.ca>
X-Mailer: Z-Mail 4.0 (4.0.0 Aug 21 1995)
Original-To: "Sherry Yang" <yangs@nortel.ca>, ATM bulliten <atommib@thumper.bellcore.com>
Subject: Re: Q: modifying a varible in atmTrafficDescrGroup
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii

I think Sherry's question raised a problem or flaw in our 1695(ng) 
MIB design. In the MIB, there is a traffic profile table 
(atmTrafficDescrTable), and  multiple connections can point to the 
same traffic profile. Since the MIB structure does not provide 
aneasy way to find out whether a traffic profile is used by any 
connection or not, it puts a great burden on NMS to search and 
find the right traffic profile whenever NMS needs to 
create/modify/delete a connection, because it is not easy to know 
whether an existing profile is already existing that matches your 
need, and it is not easy to know whether you can modify or delete 
the traffic profile since it is not easy to find out whether other 
connections are also use the same traffic profile.

But I guess we have to live with it.

-- Dawn Xie
    dawnxie@lucent.com

On Apr 1,  6:09pm, Sherry Yang wrote:
> Subject: Q: modifying a varible in atmTrafficDescrGroup
> Hello:
> 
> I am new to the group. If this question has been asked before 
please 
> accept my apology. A kind point to where I can find answers 
would
> be greatly appreciated.
> 
> I have a question regarding to modifying a variable in
> atmTrafficDescrGroup.
> 
> It seems to me that rfc1695 does not put limitation on modifying
> a variable in atmTrafficDescrGroup. However, I'd like to know 
if
> that's feasible. What impact will be to the users of the 
> AtmTrafficDescrParamEntry.
> 
> In two scenarios:
> 
> 1. An AtmTrafficDescrParamEntry nobody is using:
>    It seems no impact for changing the variables.
> 2. An AtmTrafficDescrParamEntry is referred by one or more 
other
> objects:
>    What happens or should happen when the variables in the 
entry is
>    changed?
> 
> Is there a standard or acceptable way in the industry today for 
handling
> the situations?
> 
> Thanks for your help.
> 
> 
================================================
=====================
> Sherry Yang
> NORTEL                                       Tel: (408)565-7682
> 2305 Mission College Blvd,
> Santa Clara, CA 95054, U.S.A                 Email: yangs@nortel.ca
> 
================================================
=====================
> 
>-- End of excerpt from Sherry Yang