Re: WG last call: Coex draft

On Wed, 18 Dec 2002, C. M. Heard wrote:

> If I have any other comments, I'll be sure to send them in before the
> January 10th deadline.

Add this to the list:

- The DESCRIPTION clause for snmpCommunityTransportTag has an extra
double quote that prevent a clean compile.

Here's the fix:

***************
*** 2286,2292 ****
                 In either case, if the value of this object has
                 zero-length, transport endpoints are not checked when
                 authenticating messages containing this community
!                string, nor when generating notifications."
  
                 The transports identified by this object are specified
                 in the snmpTargetAddrTable.  Entries in that table
--- 2286,2292 ----
                 In either case, if the value of this object has
                 zero-length, transport endpoints are not checked when
                 authenticating messages containing this community
!                string, nor when generating notifications.
  
                 The transports identified by this object are specified
                 in the snmpTargetAddrTable.  Entries in that table


Since dbh suggested going thru the ID-nits stuff, I put in the fix above
and made the changes to the MODULE-IDENTITY DESCRIPTION and REVISION
clauses that I recommended in my previous e-mail and ran smilint -l 9 -s
and smidiff -l 9 -s on the result.  smilint had nothing to report;
smidiff said this:

./SNMP-COMMUNITY-MIB:23 [3] contact of `SNMP-COMMUNITY-MIB' changed
./SNMP-COMMUNITY-MIB:23 [5] description of `SNMP-COMMUNITY-MIB' changed
/tmp/libsmi-0.4.1/share/mibs/ietf/SNMP-COMMUNITY-MIB:76 [3] revision `1999-05-13 00:00' removed
./SNMP-COMMUNITY-MIB:88 [5] revision `2002-12-13 00:00' added
/tmp/libsmi-0.4.1/share/mibs/ietf/SNMP-COMMUNITY-MIB:23 [6] previous definition of `SNMP-COMMUNITY-MIB'
./SNMP-COMMUNITY-MIB:193 [5] description of `snmpCommunityTransportTag' changed
/tmp/libsmi-0.4.1/share/mibs/ietf/SNMP-COMMUNITY-MIB:175 [6] previous definition of `snmpCommunityTransportTag'
./SNMP-COMMUNITY-MIB:332 [5] description of `snmpTargetAddrMMS' changed
/tmp/libsmi-0.4.1/share/mibs/ietf/SNMP-COMMUNITY-MIB:304 [6] previous definition of `snmpTargetAddrMMS'
./SNMP-COMMUNITY-MIB:437 [5] name changed from `snmpCommunityGroup' to `snmpCommunityTableGroup'
/tmp/libsmi-0.4.1/share/mibs/ietf/SNMP-COMMUNITY-MIB:410 [6] previous definition of `snmpCommunityGroup'

I think this is all OK.  Changing the group name would ordinarily result
in squawking but in this case it was done to fix a name conflict with the
SNMPv2-MIB.  However, it definitely should be listed in the "changes since
RFC 2576" section and in the most recent MODULE-IDENTITY REVISION clause.

Regards,

Mike