RE: FW: draft-ietf-sigtran-sctp-mib-09.txt - rev 10d included

["C. M. Heard" <heard@pobox.com>]

On Tue, 3 Jun 2003, Maria-Carmen Belinchon-Vergara (ECE) wrote:
> Hi, finally managed to address all these notes. Bert, if you
> don't find any other error, what is the next step? Submit the
> draft and then the IESG continues working on this or do we have
> to do something?
> 
> thanks and best regards,
> MCarmen

Hmm, the text of section 5, "Compiling Notes", is now horribly
garbled and needs to be fixed.  I recommend to something along the
following lines:

   When compiling the MIB module warnings similar to the following may
   occur:

      - warning: index of row `sctpAssocLocalAddrEntry' can exceed OID
        size limit by 141 subidentifier(s)
      - warning: index of row `sctpAssocRemAddrEntry' can exceed OID
        size limit by 141 subidentifier(s)
      - warning: index of row `sctpLookupRemHostNameEntry' can exceed
        OID size limit by 140 subidentifier(s)
      - warning: index of row `sctpLookupRemPrimIPAddrEntry' can exceed
        OID size limit by 141 subidentifier(s)
      - warning: index of row `sctpLookupRemIPAddrEntry' can exceed OID
        size limit by 141 subidentifier(s)

   These warnings are due to the fact that the row objects have index
   objects of type InetAddress or OCTET STRING whose size limit is 255
   octets, and if that size limit were reached the names of column
   instances in those rows would exceed the 128 sub-identifier limit
   imposed by current versions of the SNMP.  Actual limitations for the
   index object sizes are noted in the conceptual row DESCRIPTION
   clauses.  For the InetAddress index objects these size limits will
   not be reached with any of the address types in current use.

Note that this has both an additional warning and some changes to
the text at the end (since the affected index objects are not all
InetAddress anymore).

As long as you still have things to do another spin, how about also
fixing these micro-nits:

On page 8, 2nd paragraph from the bottom:
s/are required tobe/are required to be/

Same page, next-to-last paragraph:
s/For multihoming concept see/For the multihoming concept see/
Also, did you intend to have a paragraph
break before the sentence starting "The sctpAssocLocalAddrTable
table will have"?

On Page 42, [MIBGUIDE] reference:
the current version is draft-ietf-ops-mib-review-guidelines-01.txt

Near the end of Page 42, heading of Section 7:
s/Security Consideration/Security Considerations/

//cmh