Main By reference issues:
1. Some servers may not want to do it (memory overhead in prnter for
2. Security - how does the server gain access to the resources. NT can
do it with impersonation but that is not a generic solution.
1 having a type byte implies that any attribute can have any format - in
the original design an attribute had a defined format. THis made it
simple for a server. What happens if an attribute has a type that the
server does not expect? Or should we define a set of allowed types for
2. The main discussion seemed to be around allowing structured types
(address). What are these structured types?
> -----Original Message-----
> From: JK Martin [SMTP:jkm at underscore.com]
> Sent: Monday, June 09, 1997 11:12 AM
> To: Paul Moore
> Cc: ipp at pwg.org> Subject: RE: IPP>MOD PRO Comments on Microsofts IPP document
>> Thanks for responding to Bob Herriot's questions.
>> > By Reference:
> > I do not think that all the issues of print by reference have been
> > thought out yet.
>> Can you shed some light on those issues not yet thought out? Are
> other considerations/constraints that have not yet been presented on
> this list that we should discuss?
>>> > Type byte:
> > This was suggested to me already. I am neutral on the subject. I did
> > make the change becuase it was not discussed in San Diego. There are
> > few question I have on it which I would like to see discussed before
> > finalising.
>> What are the questions you have about typing as it has been proposed?
> We should start discussing those questions immediately, given the
> current date of this effort.
>> Whatever you and your colleagues at Microsoft can do to help further
> the development of this standard would be greatly appreciated by all
> the IPP participants.