[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Proposed "Last Call" version of draft-ietf-ops-mib-review-guidelines [ Corrected, for the 2nd time ]
- To: "Mreview (E-mail)" <mreview@ops.ietf.org>
- Subject: RE: Proposed "Last Call" version of draft-ietf-ops-mib-review-guidelines [ Corrected, for the 2nd time ]
- From: "C. M. Heard" <heard@pobox.com>
- Date: Fri, 7 Jan 2005 20:10:15 -0800 (PST)
- In-reply-to: <C9588551DE135A41AA2626CB645309370CAEE374@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
On Fri, 7 Jan 2005, Dave Thaler wrote:
> The current guidelines doc says:
>
> 4.6.1.7. IpAddress
>
> The IpAddress type described in RFC 2578 Section 7.1.5 SHOULD NOT be
> used in new MIB modules. The InetAddress/InetAddressType textual
> conventions [RFC3291bis] SHOULD be used instead.
>
> Proposed additional sentence:
>
> The IpAddress type MAY be used in cases where the object is inherently
> IPv4-specific and is either a scalar or appears in a table which is
> only applicable to IPv4.
I can live with this, if there is consensus that it is OK.
Comments please.
Thanks,
Mike