Hi Michael,
I'm pretty sure they _meant_ m68000 (Motorola 68k family).
Also, what about 'mips5' since the R5 generation has been
shipping for several years?
Also, 'sparc-32' and 'sparc-64', since UltraSPARC native code
is NOT compatible with SPARC.
I've been saying for several months that the IPP WG members
are NOT qualified to populate an IANA registry of "cpu-type"
keywords - I STRONGLY urge that this field be changed to
descriptive text (human-consumable but NOT machine-consumable).
Lastly, what the heck is 'itantium' supposed to be? Is this
an Intel/HP IA-64 family CPU?
Cheers,
- Ira McDonald
-----Original Message-----
From: Michael Sweet [mailto:mike at easysw.com]
Sent: Wednesday, November 08, 2000 7:40 AM
To: Hastings, Tom N
Cc: ipp (E-mail)
Subject: Re: IPP> DRV - Client Print Support Files Internet-Draft
down-loaded
"Hastings, Tom N" wrote:
> ...
> 6. and the following cpu-type description:
>> One or more REQUIRED comma-separated LOWER-CASE strings identifying
> the CPU types supported by this set of Client Print Support Files.
> Values (or compatible): 'unknown', 'x86-16', 'x86-32', 'x86-64',
> 'dec-vax', 'alpha', 'power-pc', 'm-6800', 'sparc', 'itantium',
> 'mips', 'arm'.
This list definitely isn't complete ("mips" should be "mips1",
"mips2", "mips3", and "mips4" at least), and I'm not sure where the
M6800 processor (an old 8-bit CPU) fits into the picture... ;)
I'm also confused about the use of a MIME type for the
document-format value and a keyword for the file-type value...
The policy stuff doesn't belong in the driver info - policy is
something an administrator will set, not the driver, and without
any means of authenticating that policy you're just opening yourself
for security risks.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw.com
Printing Software for UNIX http://www.easysw.com