Re: draft-ietf-magma-mgmd-mib-15.txt
Brian Haberman <[email protected]> Fri, 13 Feb 2009 16:55:12 -0500
| Newsgroups | gmane.ietf.magma |
|---|---|
| Message-ID | <[email protected]> |
Hi Paul,
Schirl, Paul wrote:
> All,
>
> All statements like the one below in this MIB text won’t compile for me.
>
>
>
> SYNTAX InetAddressType { ipv4(1), ipv6(2) }
>
>
>
> From RFC 4011 (INET-ADDRESS-MIB):
>
>
>
> To support future extensions, the InetAddressType textual
>
> convention SHOULD NOT be sub-typed in object type definitions.
>
> It MAY be sub-typed in compliance statements in order to
>
> require only a subset of these address types for a compliant
>
> implementation.
>
The key phrase here is "SHOULD NOT". In the case of the MGMD MIB, the
InetAddressType objects need to be limited to specific families based on
the protocols being supported (IGMP and MLD). The MIB Doctor performing
the review encouraged this sub-typing in conjunction with the sub-typing
of the InetAddress objects.
We have verified that this mib does compile with multiple standards
compliant MIB compilers.
Regards,
Brian