IPP Mail Archive: RE: IPP> MOD> Issue 1.19

IPP Mail Archive: RE: IPP> MOD> Issue 1.19

RE: IPP> MOD> Issue 1.19

Hugo Parra (HPARRA@novell.com)
Fri, 06 Nov 1998 17:27:26 -0700

I'm happy with everything Tom wrote. How does it sound to you Carl K.?


>>> "Hastings, Tom N" <hastings@cp10.es.xerox.com> 11/06/98 05:17PM >>>

A good summary.


>-----Original Message-----
>From: Hugo Parra [mailto:HPARRA@novell.com]=20
>Sent: Friday, November 06, 1998 15:04
>To: ipp@pwg.org; kugler@us.ibm.com=20
>Subject: Re: IPP> MOD> Issue 1.19
>Carl wrote:
>> Were these concerns discussed any further before Issue 1.19=20
>was moved to=20
>> the Approved Clarifications List and into the new Mod doc? =20
>If so, could
>> someone point me to the discussion (I've been out of town=20
>for a while).
>> -Carl
>I don't think we articulated a definite answer to this=20
>question. The desired behavior might not be far from what's=20
>currently documented but one or two clarifying statement may=20
>be necessary. To address the questions raised by Carl, I propose that:
>1. The "attribute-charset" attribute be required to be the=20
>first operation attribute. [Same as currently documented]
>2. A request (or response) containing more than one=20
>"attribute-character" attribute should be rejected. [As=20
>currently documented]
>3. All responses use the same 'valid' "attribute-charset"=20
>received in the corresponding request (i.e., the first=20
>operation attribute, if supported) [Might need to be=20
>clarified in the current doc]

I think that the first paragraph in "attributes-charset" in Section =
is pretty clear:

This operation attribute identifies the charset used by any 'text' and
'name' attributes that the Printer object is returning in this response.
The value in this response MUST be the same value as the
"attributes-charset" operation attribute supplied by the client in the
request. If this is not possible (i.e., the charset requested is not
supported), the request would have been rejected. See "attributes-charset"=

described in Section above.

The sentence referred to in Section is:

If the Printer object does not support the client supplied charset value,
the Printer object MUST reject the request and return the
'client-error-charset-not-supported' status code and any 'text' or 'name'
attributes using the Printer's "charset-configured" charset. =20

>4. The IPP object should always attempt to retrieve the=20
>"attribute-charset" attribute from the request (i.e., the=20
>first operation attribute) even if it has detected errors with=20
>the version, operation, or request numbers, and use it in the=20
>response informing the error condition. [Needs to be=20
>clarified in the current doc]

I think this is a good add as a SHOULD to the Model document.

>5. Whenever an IPP object cannot obtain a 'valid'=20
>"attribute-charset" attribute from the request (because it=20
>gets a request without an "attribute-charset" attribute as the=20
>first operation attribute or because it's given an attribute=20
>set is doesn't support) the response should be given in the=20
>server's default charset. [Needs to be clarified in the current doc]

I think that the sentence from 3.1.4 1 above is clear enough, don't you?

>6. Reporting a duplicate "attribute-charset" attribute error=20
>does not take any precedence over reporting any other error=20
>condition. The IPP object should not need to parse the entire=20
>request first to make sure the "attribute-charset" attribute=20
>appears once and only once in the request. [Needs to be=20
>clarified in the current doc]

There as been some debate about duplicate attributes. Its hard to detect
duplicates. Lazy or forgiving servers would just accept the first
attributes-charset that it found, since its supposed to be first.

Section says that an IPP object rejects duplicates, but there is =
SHALL or SHOULD, so this section is just a recommendation, not a

>Did I miss anything?