IETF Logo Mail Archive

Re: Mib questions

zur@FibHaifa.com (Yosef Zur) Sun, 13 September 1992 07:36 UTC

Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA05309; Sun, 13 Sep 92 03:36:43 -0400
Received: from netcomsv.netcom.com by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA05305; Sun, 13 Sep 92 03:36:26 -0400
Received: from spud.hyperion.com by netcomsv.netcom.com with UUCP (4.1/SMI-4.1) id AA02390; Sun, 13 Sep 92 00:35:53 PDT
Received: from imp.UUCP by spud.hyperion.com (4.1/SMI-4.0) id AA05959; Sun, 13 Sep 92 00:34:02 PDT
Received: by imp.HellNet.org (/\==/\ Smail3.1.21.1 #21.8) id <m0mToDX-0005A7C@imp.HellNet.org>; Sun, 13 Sep 92 09:17 IST
Received: from vivaldi.FibHaifa.com by FibHaifa.com (4.1/SMI-4.1) id AA11937; Sun, 13 Sep 92 09:00:50 IST
Date: Sun, 13 Sep 1992 09:00:50 -0000
From: zur@FibHaifa.com
Message-Id: <9209130700.AA11937@FibHaifa.com>
To: chassismib@cs.utk.edu
Subject: Re: Mib questions


Hi, 

> >1) What is the scope of the chassis MIB?  Is it limited
> >   the the devices covered in the Overview (section 5)?
> 
> It can include any abstract "networking device," including but not limited to
> the specific examples in the overview.  It could, for example, include a host.
> 
Can the device be a chassis ? to my understanding a chassis can be considered as an abstract "networking device".

--- Joseph Zur

Fibronics Inc. Haifa, Israel

Voice : INTL-972-4-313679
Fax   : INTL-972-4-550266
Email : zur@FibHaifa.com

v2.23.0 | Report a Bug | By Email