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

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

As far as I can tell, this has not been fixed:
> > > > -----Original Message-----
> > > > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> > > > Sent: sábado, 17 de mayo de 2003 0:14
> > > > To: C. M. Heard; Wijnen, Bert (Bert)
> > > > Cc: Mreview (E-mail); LyOng@ciena.com; mankin@psg.com;
> > > > jon.peterson@neustar.biz; shawn.routhier@windriver.com; Maria-Carmen
> > > > Belinchon-Vergara (ECE); Javier Pastor-Balbas (ECE)
> > > > Subject: RE: FW: draft-ietf-sigtran-sctp-mib-09.txt
> > > > 
> > > > 
> > > > Thanks Mike. I think those are reasonable (and also to my
> > > > undertsanding) only clarifying editorial changes. So once these
> > > > are done, I think they will address the comments that were raised
> > > > during IETF Last Call.
> > > > 
> > > > Let me also remind the authors, that we had agreed that
> > > >    sctpAssocRemHostName OBJECT-TYPE
> > > >      SYNTAX         OCTET STRING (SIZE(0..115))
> > > >      MAX-ACCESS     read-only
> > > >      STATUS         current
> > > >      DESCRIPTION
> > > >           "The peer's DNS name. This object needs to have the same
> > > >           format as the encoding in the DNS protocol. This implies that
> > > >           the domain name can be up to 255 octets long, each octet being
> > > >           0<=x<=255 as value with US-ASCII A-Z having a case insensitive
> > > >           matching.
> > > > 
> > > > Needed to be changed to allow for a size of (0..255). And I think
> > > > this raises another issue that the index in  sctpLookupRemHostNameTable
> > > > will possibly go over 128 subIDs, so there should be some text in there
> > > > that explains that users should be carefull not to use hostnames that
> > > > are longer than 115 for now (e.g. while using SNMPv1/v2c or v3).
> > > > 
.. snip ..
> > > > > ========================================================
> > > > > 
> > > > > On page 21:
> > > > > 
> > > > > - DELETE the following text from the DESCRIPTION clause
> > > > > of sctpAssocRemPrimAddr:
> > > > > 
> > > > >           Only IPv4 and IPv6 addresses are expected.
> > > > > 

It was not removed.

> > > > > ========================================================
> > > > > 
> > > > > On pages 27, 28, and 29:
> > > > > 
> > > > > - DELETE the following text from the DESCRIPTION clauses
> > > > > of sctpAssocLocalAddrType and sctpAssocRemAddrType:
> > > > > 
> > > > >           Only IPv4 and IPv6 addresses are expected.
> > > > > 
> > > > > - DELETE the following text from the DESCRIPTION clauses
> > > > > of sctpAssocLocalAddr and sctpAssocRemAddr:
> > > > > 
> > > > >            Theoretically this could result in a more than 128 subid
> > > > >           index, but that in practice it is only required to support
> > > > >           IPv4 and IPv6 addresses, so it would never be more than 20
> > > > >           octets.
> > > > > 
It was not removed from  sctpAssocLocalAddr

.. snip ..


plus some non-US ASCII character:

Bad chars at 2497
-: 1 stupid quotes/dashes characters
-: 1 lines containing non-US-ASCII characters

And anotehr starnge thing on page 33
     INDEX^M                    { sctpAssocRemHostName,