Fwd: Last Call: Stream Control Transmission Protocol Management Information Base to Proposed Standard

[Harrie Hazewinkel <harrie@lisanza.net>]

Begin forwarded message:

> From: The IESG <iesg-secretary@ietf.org>
> Date: Fri Apr 11, 2003  12:55:02 AM Europe/Rome
> To: IETF-Announce: ;
> Cc: sigtran@ietf.org
> Subject: Last Call: Stream Control Transmission Protocol Management  
> Information Base to Proposed Standard
> Reply-To: iesg@ietf.org
>
>
> The IESG has received a request from the Signaling Transport Working
> Group to consider Stream Control Transmission Protocol Management
> Information Base <draft-ietf-sigtran-sctp-mib-09.txt> as a Proposed
> Standard.
From draft-ietf-sigtran-sctp-mib-09.txt I noticed this.

> 5. Compiling notes
>    When compiling the MIB the following type of warning can occur:
>
>    . index of row 'sctpLookupRemPrimIPAddrEntry' can exceed OID size
>       limit by 141 subidentifier(s)
>
>    This is due to the fact that sctpAssocRemPrimAddr has the default
>    InetAddress size of (0..255), which exceeds OID size limitations.
>    Introducing a size restriction on sctpAssocRemPrimAddr would make 
> the
>    warning go away -                   - although it would be one of 
> those arbitrary
>    restrictions.
How should this be handled, I am not sure if this is the correct
way. They specify in the description of sctpAssocRemPrimAddr that it
is 'expected' to be used only for IPv4 and IPv6, but expectation
can mean that the 'dns' type can be used.
If so, then entries in this table become ambiguous. Or am I incorrect??

Harrie