IPP> IPP Bake-Off 3 Implementation specific issues (5)

IPP> IPP Bake-Off 3 Implementation specific issues (5)

IPP> IPP Bake-Off 3 Implementation specific issues (5)

Zehler, Peter Peter.Zehler at usa.xerox.com
Thu Oct 26 14:52:58 EDT 2000


All,
These are all the issues that are assumed to be isolated implementation
mistakes that will be handled by the limited number of implementations
affected.  Anyone wishing to raise these or revisit the resolutions are free
to do so.

BO3-IMP-1: Some Clients did not allow password lengths greater than 8
characters.  These clients should be corrected

BO3-IMP-2: Some Printers did not handle multiple operations across a single
connection.  IPP uses HTTP 1.1 and therefore IPP Printers must handle more
than one request across a connection.

BO4-IMP-3: Some Clients did not properly decode the attribute syntax
textwithlanguage.  The Clients recognized that it is an implementation
problem.

BO3-IMP-4: Some Printers would return all printer attributes even when only
one unsupported attribute was requested.  The Printers recognized this was
an implementation problem.

BO3-IMP-5: Some Clients had problems accepting IPP responses that did not
include the HTTP status message.  Is the HTTP status message required in the
IPP response. 
		Proposed response: IPP Client software should not parse the
reason phrase per rfc2068 section 6.1.1 
		"The Status-Code element is a 3-digit integer result code of
the
		   attempt to understand and satisfy the request. These
codes are fully defined in section 10. The Reason-Phrase is intended to give
a short textual description of the Status-Code. The Status-Code is intended
for use by automata and the Reason-Phrase is intended for the human user.
		...
		The reason phrases listed here are only recommended  -- they
may be replaced by local equivalents without affecting the protocol." 
		Also, note that the Printer should be sending a reason
phrase per rfc2068 section 6.1
		"The first line of a Response message is the Status-Line,
consisting of the protocol version followed by a numeric status code and its
associated textual phrase, with each element separated by SP characters.  No
CR or LF is allowed except in the final CRLF sequence.
		Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase
CRLF"



				Peter Zehler
				XEROX
				Xerox Architecture Center
				Email: Peter.Zehler at usa.xerox.com
				Voice:    (716) 265-8755
				FAX:      (716) 265-8792 
				US Mail: Peter Zehler
				        Xerox Corp.
				        800 Phillips Rd.
				        M/S 139-05A
				        Webster NY, 14580-9701





More information about the Ipp mailing list