Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!CCV.BBN.COM!haverty
From: haverty@CCV.BBN.COM.UUCP
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Idle chatter about reference models
Message-ID: <8711200414.AA08439@ucbvax.Berkeley.EDU>
Date: Fri, 20-Nov-87 00:08:38 EST
Article-I.D.: ucbvax.8711200414.AA08439
Posted: Fri Nov 20 00:08:38 1987
Date-Received: Sat, 21-Nov-87 18:22:33 EST
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 22

To throw mny two cents in...

I think HMP isn't "in the stack" at all, in the sense that it is NOT part
of a user data communications activity.  HMP is an application top level
protocol, between an entity at one end, i.e., the monitoring/management
operation, and an entity at the other end, i.e., the piece of code down within
some computer somewhere that is watching the activity within that computer
and interacting with the management site.  IN other words, the participants
in HMP are just like any other network users such as FTP or a data query
and retrieval system; it just happens to be the case that their activity is
associated with the operational management of a communications system.  Consider
for example if an HMP-like protocol were used to monitor the CPU-load and
disk-activity of a distributed collection of Unix systems, i.e., like
a constantly running remote "dpy" or "ps". In this case it's pretty clear that
the protocol between the players is an application in itself; HMP differs only
in that it is looking at the operation of components of a data communications
system.

Jack

PS to Dave Mills -- I do "read the mail" on the list all the time, just
a little slow in diving in.