Re: Network Printing Requirements
Brad Clements <bkc@omnigate.clarkson.edu> Fri, 24 July 1992 20:07 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa08924; 24 Jul 92 16:07 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa08911; 24 Jul 92 16:07 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa02214; 24 Jul 92 16:07 EDT
Received: by inet-gw-2.pa.dec.com; id AA03359; Fri, 24 Jul 92 13:07:30 -0700
Received: by nsl.pa.dec.com; id AA16248; Fri, 24 Jul 92 12:33:41 -0700
Received: by nsl.pa.dec.com; id AA16244; Fri, 24 Jul 92 12:33:40 -0700
Received: by inet-gw-1.pa.dec.com; id AA23362; Fri, 24 Jul 92 12:33:34 -0700
Message-Id: <9207241933.AA23362@inet-gw-1.pa.dec.com>
Date: Fri, 24 Jul 1992 15:29:45 -0400
From: Brad Clements <bkc@omnigate.clarkson.edu>
To: Charles Bazaar <cbazaar@emulex.com>
Cc: print-wg@pa.dec.com
Subject: Re: Network Printing Requirements
Is your Tri-Protocol release 3.0 unit going to do anything with the NPA spec? perhaps an SNMP queriable kinda thing? -- What would a general client want to know about the physical device? I can see a management station wanting to query it, but the dumb PC probably not.. | Brad Clements, CCP bkc@omnigate.clarkson.edu bkc@clutx.bitnet | Sr. Network Engineer Clarkson University (315)268-2292
- Network Printing Requirements Charles Bazaar
- Re: Network Printing Requirements Brad Clements