Hey, your many suggestions sound pretty good. When may we expect
you to complete the effort needed to produce such documentation?
----- Begin Included Message -----
Date: Wed, 19 Mar 1997 15:44:46 PST
To: Don Wright <firstname.lastname@example.org>
From: Tom Hastings <email@example.com>
Subject: PMP> Understanding RFC 1759 and the new enums (and the PMP web page)
Cc: peter smartt <firstname.lastname@example.org>,
There is a vital piece of information that implementors need to know
about the relationship between RFC 1759 and the enums that the PWG
has agreed to since RFC 1759.
These additional enums are intended to be used by implementations conforming
to RFC 1759. So if you want to know what additional type 2 enums have
been agreed to by the PWG, you need to access the latest version of
the Printer MIB draft that is progressing towards a draft standard.
The latest is about to become an Internet-Draft, but the current committee
draft is available in:
The textual conventions in the front of this MIB contain all of the
additional enums that an implementation conforming to RFC 1759 can
use and still be conforming to RFC 1759.
Many implementors do NOT realize this and stick only with the enums
that are in RFC 1759.
I strongly urge the PMP web page be expanded to explain that the
enums expressed as textual conventions in the current draft may be
used when implementing a device that conforms to RFC 1759 so that
implementors, such as Peter Smartt, are not mis-lead into only looking
at RFC 1759 when they implement the Printer MIB.
So the PMP web page should contain a pointer to RFC 1759 and to the
latest draft. And it should explain that implementations conforming to
RFC 1759 may use the textual conventsions in the latest draft.
Everybody agree on this?
----- End Included Message -----