Advancing the SMI
bok@nsmdserv.cnd.hp.com Thu, 21 September 1995 01:56 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20980; 20 Sep 95 21:56 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20976; 20 Sep 95 21:56 EDT
Received: from neptune.tis.com by CNRI.Reston.VA.US id aa25046; 20 Sep 95 21:56 EDT
Received: by neptune.TIS.COM id aa23457; 20 Sep 95 21:51 EDT
Received: from neptune.tis.com by neptune.TIS.COM id aa21167; 20 Sep 95 18:22 EDT
Received: from relay.tis.com by neptune.TIS.COM id aa21162; 20 Sep 95 18:12 EDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: bok@nsmdserv.cnd.hp.com
MMDF-Warning: Parse error in original version of preceding line at neptune.TIS.COM
Received: from hp.com(15.255.152.4) by relay.tis.com via smap (g3.0.1) id xma017739; Wed, 20 Sep 95 17:54:01 -0400
Received: from nsmdserv.cnd.hp.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA236764896; Wed, 20 Sep 1995 15:08:16 -0700
Received: from localhost by nsmdserv.cnd.hp.com with SMTP (1.38.193.5/15.5+ECS 3.3) id AA18062; Wed, 20 Sep 1995 16:08:36 -0600
Message-Id: <9509202208.AA18062@nsmdserv.cnd.hp.com>
To: snmpv2@tis.com
Subject: Advancing the SMI
Date: Wed, 20 Sep 1995 16:08:35 -0600
A question about the "SNMPv2 SMI" that is being recommended
for advancement to Draft Standard...
The object syntax, UInteger32 [APPPLICATION 7] is defined
in both the May31 i-drafts as well as the more recent
*kzm*alt* i-drafts.
QUESTION: Is there any reason why this type needs to be advanced
with the rest of the SMI? Should it be removed from
the SMI (as we did for NsapAddress)?
The only mib that refernces this data type is the V2-PARTY-MIB
which I presume is being sent to "historic". Or is this bad
presumption on my part? If my presumption is bad, what is the
WG recommendation w.r.t. the current Proposed Standard SNMPv2
Admin Framework and Party MIB?
bok
- Advancing the SMI bok
- Re: Advancing the SMI Barry Byrne
- Re: Advancing the SMI Bob Stewart
- Re: Advancing the SMI Bob Stewart