>>> Robert Herriot <robert.herriot@Eng.Sun.COM> 04/16/98 01:40PM >>>
> I agree with Scott's interpretation. I think we chartered IPP to =
solve=20
> communication among clients, servers and printers, not just between =
end=20
> users and print servers.
> I am concerned that SDP is a big mistake and will create yet another=20
> protocol, incompatible with all others including IPP. I think that it =
is=20
> reasonable to borrow ideas from other protocols, such as TIPSI, but I =
think=20
> we should continue along the IPP path we started.
SDP is a big mistake if it is not IPP with enhancements or it is
not the ALREADY STANDARD SDP: TIPSI. If neither IPP nor
TIPSI could not be enahanced to meet whatever the needs of a
server to device protocol, then what makes someone thing that they
can get a group of company reps together, start from scratch, and=20
get it right?! given that is what we have done several times now.
> If IPP is not a reasonable embedded solution, I wonder why we are just =
now=20
> hearing that, nearly a year after we decided on the encoding. If IPP =
is=20
> really such a bad embedded solution, perhaps we should fix it before we =
all=20
> commit to supporting it and end up with support for both IPP and SDP.
I feel that it is a reasonable embedded solution. Any "fixes" are just =
part of the
process now to move IPP/1.0 to 1.1 and beyond.