Xref: utzoo comp.protocols.tcp-ip:15828 comp.dcom.lans:7907
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!cbnewsc!dem
From: dem@cbnewsc.att.com (David E. Martin)
Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans
Subject: Re: Let's create comp.protocols.netmanagement
Message-ID: <1991Apr26.191612.15843@cbnewsc.att.com>
Date: 26 Apr 91 19:16:12 GMT
References: <1991Apr24.140256.23754@jhereg.osa.com> <1991Apr24.165425.8860@Solbourne.COM> <1991Apr26.120948.26126@jhereg.osa.com>
Organization: AT&T Bell Laboratories - Naperville, IL
Lines: 9

In article <1991Apr26.120948.26126@jhereg.osa.com> andrew@jhereg.osa.com (Andrew C. Esh) writes:
> How about comp.dcom.lans.management?

Many of the protocols are for WAN's, MAN's, and LAN's.  How about
comp.dcom.netmanagement?

David Martin
AT&T Bell Laboratories, Naperville, IL
dem@iexist.att.com