Re: Issues remaining for atm2 MIB

Juha Heinanen <jh@lohi.dat.tele.fi> Wed, 09 July 1997 07:16 UTC

Received: from cnri by ietf.org id aa00928; 9 Jul 97 3:16 EDT
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid DAA09236 for <ietf-archive@cnri.reston.va.us>; Wed, 9 Jul 1997 03:15:21 -0400 (EDT)
Received: from lohi.dat.tele.fi (jh@lohi.dat.tele.fi [193.167.66.66]) by thumper.bellcore.com (8.8.6/8.8.5) with ESMTP id CAA27558 for <atommib@thumper.bellcore.com>; Wed, 9 Jul 1997 02:52:12 -0400 (EDT)
Received: (from jh@localhost) by lohi.dat.tele.fi (8.8.5/8.8.5) id JAA00782; Wed, 9 Jul 1997 09:51:32 +0300
Date: Wed, 9 Jul 1997 09:51:32 +0300
Message-Id: <199707090651.JAA00782@lohi.dat.tele.fi>
From: Juha Heinanen <jh@lohi.dat.tele.fi>
To: jps@mtatm.ho.lucent.com
CC: fayely@3com.com, atommib@thumper.bellcore.com
In-reply-to: <33C292BA.18CFB912@mtatm.ho.lucent.com> (jps@mtatm.ho.lucent.com)
Subject: Re: Issues remaining for atm2 MIB
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII

   Should this proposal be generalized to address the needs of a service
   provider who may offer soft PVC services?

this is a good point.  we, for example, have not used regular pvcs/pvps
for years now.  all pvcs and pvps are implemented as soft pvcs/pvps.  so
i'm not sure how useful any pvc/pvp based mib features are.

since this proposal already has generated discussion and requests for
extensions, i repeat my suggestion that the feature is postponed to atm3
mib.

-- juha