DEC NET IV (RFC 1559) MIB Q

Bhushan Kanekar <bkanekar@micom.com> Sat, 11 June 1994 00:09 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10490; 10 Jun 94 20:09 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10486; 10 Jun 94 20:09 EDT
Received: from inet-gw-2.pa.dec.com by CNRI.Reston.VA.US id aa24101; 10 Jun 94 20:09 EDT
Received: from nsl.pa.dec.com by inet-gw-2.pa.dec.com (5.65/27May94) id AA02848; Fri, 10 Jun 94 17:04:20 -0700
Received: by nsl.pa.dec.com; id AA23810; Fri, 10 Jun 94 16:36:04 -0700
Received: by nsl.pa.dec.com; id AA23806; Fri, 10 Jun 94 16:36:03 -0700
Received: by pobox1.pa.dec.com; id AA18912; Fri, 10 Jun 94 16:36:01 -0700
Received: from gordius.gordian.com by inet-gw-1.pa.dec.com (5.65/27May94) id AA07073; Fri, 10 Jun 94 16:33:21 -0700
Received: from micom.com ([192.53.139.7]) by gordius.gordian.com (8.6.5/8.6.5) with SMTP id QAA24731; Fri, 10 Jun 1994 16:30:41 -0700
Received: from yosemite.micom.com by micom.com (4.1/SMI-4.0) id AA00173; Fri, 10 Jun 94 16:30:34 PDT
Received: by yosemite.micom.com (4.1/SMI-4.1) id AA14574; Fri, 10 Jun 94 16:30:35 PDT
Date: Fri, 10 Jun 1994 16:30:35 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bhushan Kanekar <bkanekar@micom.com>
Message-Id: <9406102330.AA14574@yosemite.micom.com>
To: snmp@psi.com
Subject: DEC NET IV (RFC 1559) MIB Q
Cc: phiv-mib@pa.dec.com

hi,

This Q is about the RFC1559 regarding DECnet phase IV MIB.
RFC1559 obsoletes RFC1289.

I went thru the RFC 1559, and found that a bunch of objects have
their STATUS as obsolete. My Q is, may be it's a stupid novice Q,
but what should the Agent respond to a request on an object marked
Obsolete. The OID still exists, hence IMHO the Agent cannot return
a "noSuchName" error. So what does the Agent do?

Or is it that the Manager will not allow a Request on such a name.
But then what happens with managers supporting RFC1289, and not 
RFC1559?

I would prefer a direct reply as I'm not a subscriber to the
phiv-mib mailing list.

Thanks in advance,

Bhushan

bhushan@micom.com