
Errors-to: owner-chassismib@CS.UTK.EDU
Date: Tue, 7 Jun 1994 10:00:32 --100
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Brenner Rolf - Ascom International <cz8bro@zelcom.ascom.ch>
Message-Id: <9406070800.AA01504@TDSUN4.zelcom.ascom.ch>
To: chassismib@cs.utk.edu
Subject: Subscribe

Please subscribe me.
Thanks in advance.
Rolf


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04377;
          9 Jun 94 10:12 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa04373;
          9 Jun 94 10:12 EDT
Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id JAA20126; Thu, 9 Jun 1994 09:48:30 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 9 Jun 1994 09:48:29 EDT
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from ctron.com by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id JAA20119; Thu, 9 Jun 1994 09:48:25 -0400
Received: from stealth.ctron.com by ctron.com (4.1/SMI-4.1)
	id AA14127; Thu, 9 Jun 94 09:48:21 EDT
Received: from yeti.ctron by stealth.ctron.com (4.1/SMI-4.1)
	id AA26357; Thu, 9 Jun 94 09:48:12 EDT
Received: by yeti.ctron (4.1/SMI-4.1)
	id AA17858; Tue, 7 Jun 94 12:59:53 EDT
Message-Id: <9406071659.AA17858@yeti.ctron>
To: chassismib@cs.utk.edu
Subject: Future
Reply-To: arneson@ctron.com
Date: Tue, 07 Jun 94 12:59:52 -0400
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "David L. Arneson" <arneson@yeti.ctron.com>

Well another IETF is comming up on us.  I guess I would like to find
out if there is interest in getting together to discuss where we are
going with the chassis MIB.

The order of business should be to talk about the old internet draft
from last year.  Pete Wilson's proposal to the group.  Discuss any
new ideas people may have had.  Then determine if we have enough
direction to define a charter and start the working group up again.

So if you are interested in seeing the group move forward at this
time respond to this message.  If I see a sufficient number of
responses I will request permission to hold a BOF.

I guess one problem we may face is conflict with SNMPv2 assuming it
starts in the fall.  However I feel that if we are all dedicated to
solving the chassis MIB problems we may be able to be pretty close to
done by the fall.


/David Arneson [arneson@ctron.com] [ (603)337-5238 ]


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05436;
          9 Jun 94 11:39 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa05430;
          9 Jun 94 11:39 EDT
Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id LAA28347; Thu, 9 Jun 1994 11:16:51 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 9 Jun 1994 11:16:50 EDT
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from uu4.psi.com by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id LAA28340; Thu, 9 Jun 1994 11:16:48 -0400
Received: from world.lannet.com by uu4.psi.com (5.65b/4.0.071791-PSI/PSINet) via SMTP;
        id AA18654 for chassismib@CS.UTK.EDU; Thu, 9 Jun 94 11:15:20 -0400
Received: from moon.lannet.com by gandalf.lannet.com (4.1/SMI-4.1)
	id AA04894; Thu, 9 Jun 94 18:15:56 IDT
Received: from gandalf.lannet.com by moon.lannet.com (4.1/SMI-4.1)
	id AA26983; Thu, 9 Jun 94 18:15:56 IDT
Date: Thu, 9 Jun 94 18:15:56 IDT
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dan Romascanu <dan@lannet.com>
Message-Id: <9406091515.AA26983@moon.lannet.com>
To: arneson@ctron.com, chassismib@cs.utk.edu
Subject: Re:  Future

We are interested in seeing the Chassis MIB WG restarted. I think
we learned the lesson from the mistakes made in the previous round
and the problems are still there. I agree that if we can agree on 
a well-focused Charter, we should be able to complete the work in
a couple of meetings.

Dan Romascanu, LANNET Data Communications Ltd., 972-3-645-8414

--------------------------------------------------------------------

Well another IETF is comming up on us.  I guess I would like to find
out if there is interest in getting together to discuss where we are
going with the chassis MIB.

The order of business should be to talk about the old internet draft
from last year.  Pete Wilson's proposal to the group.  Discuss any
new ideas people may have had.  Then determine if we have enough
direction to define a charter and start the working group up again.

So if you are interested in seeing the group move forward at this
time respond to this message.  If I see a sufficient number of
responses I will request permission to hold a BOF.

I guess one problem we may face is conflict with SNMPv2 assuming it
starts in the fall.  However I feel that if we are all dedicated to
solving the chassis MIB problems we may be able to be pretty close to
done by the fall.


/David Arneson [arneson@ctron.com] [ (603)337-5238 ]


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06522;
          9 Jun 94 12:55 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa06518;
          9 Jun 94 12:55 EDT
Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id MAA04609; Thu, 9 Jun 1994 12:24:48 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 9 Jun 1994 12:24:47 EDT
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from SynOptics.COM by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id MAA04602; Thu, 9 Jun 1994 12:24:45 -0400
Received: from donatello (donatello.synoptics.com) by SynOptics.COM (4.1/SMI-4.1)
	id AA10321; Thu, 9 Jun 94 09:22:28 PDT
Received: by donatello (4.1/2.0N)
	   id AA12416; Thu, 9 Jun 94 09:22:29 PDT
Message-Id: <9406091622.AA12416@donatello>
Date: Thu, 9 Jun 94 09:22:29 PDT
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Bierman <abierman@synoptics.com>
To: chassismib@cs.utk.edu, arneson@ctron.com
Subject: Re: Future

> Well another IETF is comming up on us.  I guess I would like to find
> out if there is interest in getting together to discuss where we are
> going with the chassis MIB.
> ...
> /David Arneson [arneson@ctron.com] [ (603)337-5238 ]
> 
I'm interested in a chassis MIB that provides:
   1) a good definition of a chassis
   2) an inventory of physical components in a chassis
   3) a fix for the "Repeater ID" problem
   4) an indication of the SNMP capabilities of each component 
      (i.e. pointers to MIBs, other agents in the chassis)
   5) a physical sub-component hierarchy

I hope you can get a BOF scheduled soon...

--andy;


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07422;
          9 Jun 94 13:50 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa07416;
          9 Jun 94 13:49 EDT
Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id NAA09251; Thu, 9 Jun 1994 13:29:22 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 9 Jun 1994 13:29:21 EDT
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from chipcom.com by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id NAA09244; Thu, 9 Jun 1994 13:29:18 -0400
Received: from teach.stealth ([151.104.20.60]) by chipcom.com (4.1/SMI-4.0)
	id AA13703; Thu, 9 Jun 94 13:27:36 EDT
Received: by teach.stealth (4.1/SMI-4.1)
	id AA01091; Thu, 9 Jun 94 13:23:35 EDT
Date: Thu, 9 Jun 94 13:23:35 EDT
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Horowitz <witz@chipcom.com>
Message-Id: <9406091723.AA01091@teach.stealth>
To: chassismib@cs.utk.edu
Subject: Re: Future


I'm curious how the chassis MIB can "fix the repeater ID problem" ?

Or better yet, I want to be able to fix the problem where I have
an agent representing 100's of repeaters, so that the user does
not have to go through configuration hell to retrieve that
information.

Same issue for bridges.

I wonder what would be the right approach to solve this.

-- Steve

> From owner-chassismib@CS.UTK.EDU Thu Jun  9 13:05:25 1994
> Return-Path: <owner-chassismib@CS.UTK.EDU>
> Received: from CS.UTK.EDU by chipcom.com (4.1/SMI-4.0)
> 	id AA12087; Thu, 9 Jun 94 13:05:20 EDT
> Errors-To: owner-chassismib@CS.UTK.EDU
> Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
> 	id MAA04609; Thu, 9 Jun 1994 12:24:48 -0400
> X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 9 Jun 1994 12:24:47 EDT
> Errors-To: owner-chassismib@CS.UTK.EDU
> Received: from SynOptics.COM by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
> 	id MAA04602; Thu, 9 Jun 1994 12:24:45 -0400
> Received: from donatello (donatello.synoptics.com) by SynOptics.COM (4.1/SMI-4.1)
> 	id AA10321; Thu, 9 Jun 94 09:22:28 PDT
> Received: by donatello (4.1/2.0N)
> 	   id AA12416; Thu, 9 Jun 94 09:22:29 PDT
> Message-Id: <9406091622.AA12416@donatello>
> Date: Thu, 9 Jun 94 09:22:29 PDT
> From: Andrew Bierman <abierman@synoptics.com>
> To: chassismib@CS.UTK.EDU, arneson@ctron.com
> Subject: Re: Future
> Content-Length: 634
> X-Lines: 17
> Status: RO
> 
> > Well another IETF is comming up on us.  I guess I would like to find
> > out if there is interest in getting together to discuss where we are
> > going with the chassis MIB.
> > ...
> > /David Arneson [arneson@ctron.com] [ (603)337-5238 ]
> > 
> I'm interested in a chassis MIB that provides:
>    1) a good definition of a chassis
>    2) an inventory of physical components in a chassis
>    3) a fix for the "Repeater ID" problem
>    4) an indication of the SNMP capabilities of each component 
>       (i.e. pointers to MIBs, other agents in the chassis)
>    5) a physical sub-component hierarchy
> 
> I hope you can get a BOF scheduled soon...
> 
> --andy;
> 


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07924;
          9 Jun 94 14:29 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa07920;
          9 Jun 94 14:29 EDT
Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id OAA12512; Thu, 9 Jun 1994 14:02:15 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 9 Jun 1994 14:02:13 EDT
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from SynOptics.COM by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id OAA12503; Thu, 9 Jun 1994 14:02:10 -0400
Received: from donatello (donatello.synoptics.com) by SynOptics.COM (4.1/SMI-4.1)
	id AA11424; Thu, 9 Jun 94 11:00:48 PDT
Received: by donatello (4.1/2.0N)
	   id AA14776; Thu, 9 Jun 94 11:00:48 PDT
Message-Id: <9406091800.AA14776@donatello>
Date: Thu, 9 Jun 94 11:00:48 PDT
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Bierman <abierman@synoptics.com>
To: chassismib@cs.utk.edu, witz@chipcom.com
Subject: Re: Future

There are two pieces to the Repeater ID problem (or the Bridge ID problem--same thing)

1) A simple to use, universally implementable, method to identify a given repeater.

2) A way to correlate the (now uniquely identified) repeater with a physical location.

Item 1 was almost solved--until the WG removed the repeater ID component from all the
repeater MIB tables. Now community string or party ID or some other proprietary method
has to be used to identify a repeater.

Item 2 would still be a problem even if the WG had left in the repeater ID. Knowing
that you are talking about "repeater 472" is more useful if you know where that repeater is...
The chassis MIB would provide a physical inventory of all devices (including repeaters)
and could also provide the community string, party ID, etc. used to address the device
in the repeater MIB.

Port-switchable hubs and other similar devices make the problem a little more tricky.
You have to identify all possible repeaters (100's or 1000's of repeaters) statically.
As ports are switched, some repeaters may come into existence and others may dissappear.
The chassis MIB would have to handle this type of hub.

--andy;

> 
> I'm curious how the chassis MIB can "fix the repeater ID problem" ?
> 
> Or better yet, I want to be able to fix the problem where I have
> an agent representing 100's of repeaters, so that the user does
> not have to go through configuration hell to retrieve that
> information.
> 
> Same issue for bridges.
> 
> I wonder what would be the right approach to solve this.
> 
> -- Steve

> > > Well another IETF is comming up on us.  I guess I would like to find
> > > out if there is interest in getting together to discuss where we are
> > > going with the chassis MIB.
> > > ...
> > > /David Arneson [arneson@ctron.com] [ (603)337-5238 ]
> > > 
> > I'm interested in a chassis MIB that provides:
> >    1) a good definition of a chassis
> >    2) an inventory of physical components in a chassis
> >    3) a fix for the "Repeater ID" problem
> >    4) an indication of the SNMP capabilities of each component 
> >       (i.e. pointers to MIBs, other agents in the chassis)
> >    5) a physical sub-component hierarchy
> > 
> > I hope you can get a BOF scheduled soon...
> > 
> > --andy;
> > 
> 


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07135;
          13 Jun 94 14:53 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa07131;
          13 Jun 94 14:53 EDT
Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id OAA15620; Mon, 13 Jun 1994 14:37:31 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Mon, 13 Jun 1994 14:37:30 EDT
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from sys30 by CS.UTK.EDU with ESMTP (cf v2.9s-UTK)
	id OAA15599; Mon, 13 Jun 1994 14:37:26 -0400
Received: from maelstrom.timeplex.com by sys30.timeplex.com (PMDF V4.2-14
 #2740) id <01HDHWJ9TMU88YDLD1@sys30.timeplex.com>; Mon,
 13 Jun 1994 14:37:18 EDT
Received: from oak.timeplex.com by maelstrom.timeplex.com (4.1/SMI-4.1) id
 AA10343; Mon, 13 Jun 94 14:36:25 EDT
Date: Mon, 13 Jun 1994 14:36:25 -0400 (EDT)
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Manu Kaycee <kaycee@maelstrom.timeplex.com>
Subject: Re: Future
To: arneson@ctron.com
Cc: chassismib@cs.utk.edu, kaycee@maelstrom.timeplex.com
Message-id: <9406131836.AA10343@maelstrom.timeplex.com>
Content-transfer-encoding: 7BIT

BBD,

You asked about interest in the(a) Chassis MIB and
an associated BOF.

Very interested in both.

Later,


+mjk