IPP Mail Archive: IPP> RE: question about "ipp-implementers-guide-990212" document

IPP> RE: question about "ipp-implementers-guide-990212" document

Hastings, Tom N (hastings@cp10.es.xerox.com)
Wed, 19 May 1999 08:43:57 -0700

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Hastings, Tom N: "IPP> NOT - ISSUE 1 - can event reporting be dropped if device is too b"
Previous message: Anthony Porter: "RE: IPP> ISSUE 17 - Job Time Event attributes (AGAIN)"

yes, there are 17 occurrences of the status code with the incorrect name in
section 2.2.1:

'client-error-request-bad-request'

It should be:

'client-error-bad-request'

I'll fix them in the IPP/1.1 Implementer's Guide.

Also I'll fix it working with the RFC Editor on the IPP/1.0 IIG that has
been approved to go out as an Information RFC.

If anyone finds any other errors in the IIG, please send them to me or the
mailing list.

Thanks,
Tom

-----Original Message-----
From: brian@swc.sec.samsung.co.kr [mailto:brian@swc.sec.samsung.co.kr]
Sent: Tuesday, May 18, 1999 22:35
To: 'hastings@cp10.es.xerox.com'
Subject: question about "ipp-implementers-guide-990212" document

Hi, Tom.

I discovered one confusing status code while I have read above document.
'client-error-request-bad-request' status code but it is not included
Client Error Stauts Codes in [IPP-MOD] Section 14.1.4. There is just
'client-error-bad-request'.
Is it right?

Regards,

---------------
Sangwook Ye
Samsung Electronics Co., Ltd.
Tel) 82-331-200-3210
E-mail) brian@swc.sec.samsung.co.kr

Next message: Hastings, Tom N: "IPP> NOT - ISSUE 1 - can event reporting be dropped if device is too b"
Previous message: Anthony Porter: "RE: IPP> ISSUE 17 - Job Time Event attributes (AGAIN)"