🚀 go-pugleaf

In article <1992Aug12.160937.16515@udel.edu>, stewart@ra.cis.udel.edu (John Stewart) writes:
> In article <2841@ucl-cs.uucp> J.Crowcroft@cs.ucl.ac.uk (Jon Crowcroft) writes:
> >Evolution dictates:
> >SGMP (simple gateway management protocol)
> >SNMP (simple network management protocol)
> >SMP (simple management protocol)
> >SP (simple protocol)
> >P (protocol)
> >
> >but then what?
> 
> Obviously, "Segmentation Violation (core dump)".  Get it?

Actually, at that point we will see the long-awaited arrival of a real
network  operating  system  (NOS), so no such protocol will be needed,
just a network interface  that  can  deliver  the  NOS's  (binary  for
efficiency)  packets.  Network management will then be synonymous with
system management, and we will have the joys of dealing with  the  new
world-wide management structure that will develop to deal with it.

Actually, I'm quite well aware that such things have  existed  for  at
least a decade now.  By "arrival" I mean that we will finally have the
sense to do it right and start using some NOS, rather than  continuing
to  futz  around with klutsy partial solutions like NFS and SNMP.  (So
please don't send me any flames telling me what an idiot I am for  not
knowing that it's already been done.  ;-)

But my real reason for posting this is that I've  been  reading  about
SMP,  but so far I haven't managed to actually get a copy of any specs
(or RFC or whatever the doc is called).  Lots of advertising hype, but
where's  the beef?  Everyone thinks that specs are obviously available
from somewhere, but  so  far  no  clues  sufficient  to  actually  get
anything.   How might someone without Internet access elicit a copy of
such a document?  (It'd be interesting to see what the latest  partial
solution  is,  especially  since people have been asking me if I could
implement it, and that's real hard to do without any specs.  ;-)