The following text at Section 6 is too restrictive in a manner that is both
unnecessary and not consistent with other text (e.g. at Section 5)
The following textual conventions are defined to support unsigned 64-bit
data types for HC-RMON [HC-RMON].
I suggest replacing this text by the following:
The following textual conventions are defined to support unsigned 64-bit
data types for MIBs such as the HC-RMON MIB [HC-RMON].
The reason is that other MIB documents should feel free to use the Textual
Conventions described by this document freely, until a permanent solution is
standardized as part of some evolution of the SNMP SMI.
Regards,
Dan
> -----Original Message-----
> From: Wijnen, Bert (Bert) [SMTP:[EMAIL PROTECTED]]
> Sent: Mon March 20 2000 20:26
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: FW: Last Call: Textual Conventions for Additional High
> Capacity D ata Types to Proposed Standard
>
> Just in case someone missed it.
>
> Bert
>
> > ----------
> > From: The IESG[SMTP:[EMAIL PROTECTED]]
> > Reply To: [EMAIL PROTECTED]
> > Sent: Monday, March 20, 2000 4:43 PM
> > Cc: [EMAIL PROTECTED]
> > Subject: Last Call: Textual Conventions for Additional High Capacity
> > Data Types to Proposed Standard
> >
> >
> > The IESG has received a request to consider Textual Conventions for
> > Additional High Capacity Data Types <draft-kzm-hcdata-types-05.txt> as
> > a Proposed Standard. This has been reviewed in the IETF but is not the
> > product of an IETF Working Group.
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send any comments to the
> > [EMAIL PROTECTED] or [EMAIL PROTECTED] mailing lists by April 18, 2000.
> >
> > Files can be obtained via
> > http://www.ietf.org/internet-drafts/draft-kzm-hcdata-types-05.txt
> >
> >
