Re: phiv MIB document Status

Bob Stewart <rlstewart@eng.xyplex.com> Tue, 10 November 1992 23:04 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15822; 10 Nov 92 18:04 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa15818; 10 Nov 92 18:04 EST
Received: from inet-gw-2.pa.dec.com by CNRI.Reston.VA.US id aa22474; 10 Nov 92 18:05 EST
Received: by inet-gw-2.pa.dec.com; id AA14944; Tue, 10 Nov 92 15:03:38 -0800
Received: by nsl.pa.dec.com; id AA25917; Tue, 10 Nov 92 14:32:55 -0800
Received: by nsl.pa.dec.com; id AA25913; Tue, 10 Nov 92 14:32:54 -0800
Received: by inet-gw-2.pa.dec.com; id AA13092; Tue, 10 Nov 92 14:32:50 -0800
Received: by xap.xyplex.com id <AA24314@xap.xyplex.com>; Tue, 10 Nov 92 18:29:56 -0500
Date: Tue, 10 Nov 92 18:29:56 -0500
Message-Id: <9211102329.AA24314@xap.xyplex.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bob Stewart <rlstewart@eng.xyplex.com>
To: phiv-mib@pa.dec.com
In-Reply-To: saperia@tcpjon.ogo.dec.com's message of Fri, 06 Nov 92 13:30:06 -0500 <9211061830.AA03303@tcpjon.ogo.dec.com>
Subject: Re: phiv MIB document Status

Xyplex is shipping an implementation of the DECnet Phase IV MIB.  We will
probably be able to update relatively quickly for the changes, but will have
an issue of maintaining what we've done for any customers that started using
it.  The proposal to make the existing table obsolete and retire its OID is
fine.  We're obviously ready for interoperability testing any time.

	Bob