RFC Errata
Found 2 records.
Status: Verified (1)
RFC 2325, "Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2", April 1998
Source of RFC: INDEPENDENT
Errata ID: 3993
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Jack Lawson
Date Reported: 2014-05-20
Verifier Name: Nevil Brownlee (ISE)
Date Verified: 2014-06-03
Section 4 says:
potType OBJECT-TYPE SYNTAX INTEGER { automatic-drip(1), percolator(2), french-press(3), espresso(4), } MAX-ACCESS read-write STATUS current DESCRIPTION "The brew type of the coffee pot." ::= { coffee 3 }
It should say:
potType OBJECT-TYPE SYNTAX INTEGER { automatic-drip(1), percolator(2), french-press(3), espresso(4), } MAX-ACCESS read-only STATUS current DESCRIPTION "The brew type of the coffee pot." ::= { coffee 3 }
Notes:
potName and potCapacity are read-only, as name and capacity will not change after instantiation; type should be as well, as potType will not change over time (reincarnation as a separate pot would constitute a new instance.) potLocation should remain read-write, as a pot may change locations.
Status: Rejected (1)
RFC 2325, "Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2", April 1998
Source of RFC: INDEPENDENT
Errata ID: 4301
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Anthony Yu
Date Reported: 2015-03-12
Rejected by: Barry Leiba
Date Rejected: 2015-03-13
Section 3 says:
The MIB contains objects that relate to physical connections, configuration, storage levels, availability, quality of service, and availability.
It should say:
The MIB contains objects that relate to physical connections, configuration, storage levels, quality of service, and availability.
Notes:
Availability is stated twice.
--VERIFIER NOTES--
Any coffee drinker will tell you that availability is absolutely critical. Its appearance twice
in the list reflects that importance, and I am rejecting this errata report on those...grounds.