Xref: utzoo comp.protocols.tcp-ip:15827 comp.dcom.lans:7904
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!jhereg!andrew
From: andrew@jhereg.osa.com (Andrew C. Esh)
Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans
Subject: Re: Let's create comp.protocols.netmanagement
Message-ID: <1991Apr26.172841.610@jhereg.osa.com>
Date: 26 Apr 91 17:28:41 GMT
References: <1991Apr24.165425.8860@Solbourne.COM> <1991Apr26.120948.26126@jhereg.osa.com> <1991Apr26.133136.2172@bwdls61.bnr.ca>
Organization: Open Systems Architects, Inc., Mpls, MN
Lines: 22

In article <1991Apr26.133136.2172@bwdls61.bnr.ca> pww@bnr.ca (Peter Whittaker) writes:
>In article <1991Apr26.120948.26126@jhereg.osa.com> andrew@jhereg.osa.com (Andrew C. Esh) writes:
>>to protocols. How about comp.dcom.lans.management?
>                                   ^^^^
>At the risk of splitting too fine a hair, we won't be discussing LAN mgt
>exclusively, will we?  How about comp.dcom.network.management (or some
>such variance)?
>
>--
>Peter Whittaker      [~~~~~~~~~~~~~~~~~~~~~~~~~~]   Open Systems Integration
>pww@bnr.ca           [       DSA's'R'Us!        ]   Bell Northern Research 
>Ph: +1 613 765 2064  [                          ]   P.O. Box 3511, Station C
>FAX:+1 613 763 3283  [__________________________]   Ottawa, Ontario, K1Y 4H7

The only reason I suggested the lans group is because it already exists.
WANs, and anything else, if managable by SNMP or any other protocol,
should be included. What ever will get the discussion going. :-)
-- 
Andrew C. Esh			andrew@osa.com
Open Systems Architects, Inc.
Mpls, MN 55416-1528		Punch down, turn around, do a little crimpin'
(612) 525-0000			Punch down, turn around, plug it in and go ...