[ih] inter-network communication history

[Brian E Carpenter via Internet-history]

Marshall Rose once told me that he regretted the "S" in SNMP, because it
was anything but simple. And I think he also said that ASN/1 was chosen
mainly to build bridges with the OSI world. But SNMP was a success (about
300 related RFCs exist).

Anyway, NETCONF and YANG are currently taking over the universe. I haven't
noticed a new MIB module in the IETF world for quite a while. Only two
MIB RFCs were published in 2018, and none this year. There are also only
two MIBs in Internet Draft format, one started in 2014 and the other started
in 2016. MIBs are apparently a dying breed. There are currently 152 active
Internet Drafts related to YANG. Game over.

Regards
   Brian Carpenter

On 09-Nov-19 06:54, Craig Partridge via Internet-history wrote:
> On Fri, Nov 8, 2019 at 10:20 AM John Day <jeanjour at comcast.net> wrote:
> 
>> You told me once the implementation was smaller. Also, I also know from
>> Randy Presuhn that the CMIP implementation was smaller than SNMP as well.
>> It seemed that lexicographical order takes more code that object-oriented.
>> For me, HEMS would have been a better way forward.  A few years earlier
>> IEEE 802 had tried a protocol like SNMP and found it inferior, which is why
>> CMIP was done.  Also that HEMS used TCP for request/response and UDP for
>> events was simply sane, rather than trying to do everything over UDP. In
>> which case, GetNest is unnecessary. The inability to get a snapshot of
>> anything large-ish was a real problem.
>>
> 
> Your recollection is better than mine.  I have a vague recollection that
> the initial SNMP implementations were large because they had some ASN
> library or code generator that generated volumes of code, while HEMS had a
> much tighter handwritten ASN.1 module.  I don't know if that would have
> been true in perpetuity.
> 
> 
>>
>> A further advantage would have been had by CMIP since it could use the
>> Packed-Encoding Rules for ASN.1 rather than having to use the Basic
>> Encoding Rules wired into SNMP.  PER was sufficiently efficient that often
>> compressing a PER encoding was larger.
>>
> 
> BER was wired into HEMS to support the private MIBs.
> 
> Craig
> 
> 
> 
-- 
Internet-history mailing list
Internet-history at elists.isoc.org
https://elists.isoc.org/mailman/listinfo/internet-history