Re: [Forwarded: RFC1398 on Ethernet-Like MIB]
Frank Kastenholz <kasten@ftp.com> Thu, 28 January 1993 23:03 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16020; 28 Jan 93 18:03 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa16016; 28 Jan 93 18:03 EST
Received: from babyoil.ftp.com by CNRI.Reston.VA.US id aa01179; 28 Jan 93 18:05 EST
Received: by ftp.com id AA07120; Thu, 28 Jan 93 17:46:33 -0500
Date: Thu, 28 Jan 1993 17:46:33 -0500
Message-Id: <9301282246.AA07120@ftp.com>
To: sprung@sys.smc.com
Subject: Re: [Forwarded: RFC1398 on Ethernet-Like MIB]
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Frank Kastenholz <kasten@ftp.com>
Reply-To: kasten@ftp.com
Cc: enet_mib@ftp.com
Hi Lance > I noticed that the chip was not included. Since the SMC controller > is in use on a few million of our adapters (previously Western Digital), > I thought that we could possibly get our controllers added to the list. Sorry, the RFC itself is done. Perhaps when we take a look to go to full standard. In the mean time, you should publish any of your own OIDs on your own (perhaps on the repository at venera.isi.edu). > BTW, I'm also interested in learning more about implementations of this MIB. > Can you inform me of any references? RFC1369 is a place to start. -- Frank Kastenholz
- [Forwarded: RFC1398 on Ethernet-Like MIB] Frank Kastenholz
- Re: [Forwarded: RFC1398 on Ethernet-Like MIB] Lance Sprung
- Re: [Forwarded: RFC1398 on Ethernet-Like MIB] Frank Kastenholz