Re: resolving ambiguity in rfc1759 (standard printer MIB) [a proposal that won't require re-issuing a new rfc immediately]
Don Wright <don@lexmark.com> Mon, 15 May 1995 12:17 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02253; 15 May 95 8:17 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa02249; 15 May 95 8:17 EDT
Received: from hp.com by CNRI.Reston.VA.US id aa04473; 15 May 95 8:17 EDT
Received: from hpdmd48.boi.hp.com by hp.com with SMTP (1.37.109.15/15.5+ECS 3.3) id AA259880287; Mon, 15 May 1995 05:18:07 -0700
Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.38.193.5/15.5+ECS 3.4 Openmail) id AA16603; Mon, 15 May 1995 06:17:57 -0600
Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA13486; Mon, 15 May 95 06:10:28 -0600
Received: from interlock.lexmark.com by hp.com with SMTP (1.37.109.15/15.5+ECS 3.3) id AA258600200; Mon, 15 May 1995 05:16:40 -0700
Received: by interlock.lexmark.com id AA06818 (InterLock SMTP Gateway 3.0 for pmi@hpbs987.boi.hp.com); Mon, 15 May 1995 08:13:28 -0400
Message-Id: <199505151213.AA06818@interlock.lexmark.com>
Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-2); Mon, 15 May 1995 08:13:28 -0400
Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-1); Mon, 15 May 1995 08:13:28 -0400
To: "pmi%hpbs987.boi.hp.com" <pmi@hpbs987.boi.hp.com>
Cc: "dck2-iesg%mail.bellcore.com" <dck2-iesg@mail.bellcore.com>, "jgyllens%hpbs3125.boi.hp.com" <jgyllens@hpbs3125.boi.hp.com>, "case%snmp.com" <case@snmp.com>, "waldbusser%ins.com" <waldbusser@ins.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Don Wright <don@lexmark.com>
Date: Mon, 15 May 1995 08:16:11 -0400
Subject: Re: resolving ambiguity in rfc1759 (standard printer MIB) [a proposal that won't require re-issuing a new rfc immediately]
Mime-Version: 1.0
Content-Type: Text/Plain
Tom Hastings said: > > > I propose that we change the enumerated INTEGER labels of the > prtConsoleInput enums to remove the ambiguity. > ... > So I propose that we clarify the ambiguity by adding words to the > enumeration labels, changing them from: > > enabled(3), > disabled(4) > >to: > > manual-input-enabled(3), > manual-input-disabled(4) > ... I like Tom's concept; however I have a little trouble with the specific words: The term "manual-input" applied to an operator panel it not really consistant with its normal usage in the printer industry. "Manual input" normally refers to the manual insertion of paper rather than the use of a tray. I suggest we use something like operator-console-enabled(3) operator-console-disabled(4) -or- console-controls-enabled(3) console-controls-disabled(4) I am afraid too many people may confuse this with paper unless we choose our words carefully. If we do make these changes, I sure want them to be the last time we have to change this object. Don
- Re: resolving ambiguity in rfc1759 (standard prin… Thomas N. Hastings
- Re: resolving ambiguity in rfc1759 (standard prin… Don Wright
- Re: resolving ambiguity in rfc1759 (standard prin… Thomas N. Hastings