Re: resolving ambiguity in rfc1759 (standard printer MIB) [a proposal that won't require re-issuing a new rfc immediately]
"Thomas N. Hastings" <hastings@cp10.es.xerox.com> Tue, 16 May 1995 04:41 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27046; 16 May 95 0:41 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27041; 16 May 95 0:41 EDT
Received: from hp.com by CNRI.Reston.VA.US id aa19575; 16 May 95 0:41 EDT
Received: from hpdmd48.boi.hp.com by hp.com with SMTP (1.37.109.15/15.5+ECS 3.3) id AA152739322; Mon, 15 May 1995 21:42:02 -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 AA25075; Mon, 15 May 1995 22:41:55 -0600
Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA01084; Mon, 15 May 95 22:35:01 -0600
Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.15/15.5+ECS 3.3) id AA151959273; Mon, 15 May 1995 21:41:13 -0700
Received: from diana.cp10.es.xerox.com ([13.240.108.16]) by alpha.xerox.com with SMTP id <14482(6)>; Mon, 15 May 1995 21:38:34 PDT
Received: by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA05082; Mon, 15 May 95 21:38:31 PDT
Date: Mon, 15 May 1995 21:38:31 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Thomas N. Hastings" <hastings@cp10.es.xerox.com>
Message-Id: <9505160438.AA05082@diana.cp10.es.xerox.com>
To: pmi@hpbs987.boi.hp.com, don@lexmark.com
Subject: Re: resolving ambiguity in rfc1759 (standard printer MIB) [a proposal that won't require re-issuing a new rfc immediately]
Cc: dck2-iesg@mail.bellcore.com, jgyllens@hpbs3125.boi.hp.com, case@snmp.com, waldbusser@ins.com
I agree with Don that my choice of words: manual-input-enabled and manual-input-disabled would be too easily confused with manual media input. So I prefer Don's suggestion: -- operator-console-enabled(3) -- operator-console-disabled(4) rather than: -- console-controls-enabled(3) -- console-controls-disabled(4) Another possibility would be: -- console-input-enabled(3), -- console-input-disabled(4) Tom --From don@lexmark.com Mon May 15 05:17:26 1995 --Return-Path: <don@lexmark.com> --Received: from norman.cp10.es.xerox.com by diana (4.1/SMI-4.1) -- id AA02782; Mon, 15 May 95 05:17:25 PDT --Received: from alpha.xerox.com by norman.cp10.es.xerox.com (4.1/SMI-4.1) -- id AA23493; Mon, 15 May 95 05:17:50 PDT --Received: from hp.com ([15.255.152.4]) by alpha.xerox.com with SMTP id <14401(5)>; Mon, 15 May 1995 05:17:15 PDT --Received: from hpdmd48.boi.hp.com by hp.com with SMTP -- (1.37.109.15/15.5+ECS 3.3) id AA259110231; Mon, 15 May 1995 05:17:11 -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 AA16584; Mon, 15 May 1995 06:16:52 -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 --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> --From: Don Wright <don@lexmark.com> --Date: Mon, 15 May 1995 05:16:11 PDT --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