Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!AHWAHNEE.STANFORD.EDU!dcrocker
From: dcrocker@AHWAHNEE.STANFORD.EDU (Dave Crocker)
Newsgroups: comp.protocols.tcp-ip
Subject: RE: DOD ---> CMOT VERSUS SNMP
Message-ID: <8909172333.AA21455@ucbvax.Berkeley.EDU>
Date: 17 Sep 89 21:52:09 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 29

Just to add to the confusion, I should note that I am beginning to
hear increasing rumblings that some vendors might wish to suggest
moving directly to full CMIP over TCP, rather than using the 
constrained CMOT.

While I don't have anything more substantial than citing 'rumor', in
terms of hearing about vendor plans, the technical distinction is
significant:

CMOT has two differences from CMIP.  The first is that it operates over
TCP, rather than OSI transport.  This turns out to be relatively
uninteresting, from the standpoint of management protocol discussions
and it is NOT the change that I am hearing rumored.

Much more importantly, CMOT specified a subset of the ASN.1 data types
and, I believe, a subset of the management protocol operations from
'pure' CMIP (draft international standard or slightly before).  Moving
to "full" CMIP, even over TCP, therefore involves some amount of
enhancement to the application protocol.

The original subsetting was done out of the usual desire to streamline
the initial implementation effort, for the demo that was schedules and
accomplished at last year's Interop.

Privately (i.e., not burdening the tcp-ip list with the traffic) I would
be interested in hearing about vendor feelings on this topic.

Dave Crocker
Digital Equipment Corp.