IPP> conflicting "attributes-charset"
Van Dang <dangv@ecs.csus.edu> Tue, 04 August 1998 21:39 UTC
Delivery-Date: Tue, 04 Aug 1998 17:39:51 -0400
Return-Path: ipp-owner@pwg.org
Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA17483 for <ietf-archive@ietf.org>; Tue, 4 Aug 1998 17:39:47 -0400 (EDT)
Received: from lists.underscore.com (uscore-1.mv.com [199.125.85.30]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id RAA12123 for <ietf-archive@cnri.reston.va.us>; Tue, 4 Aug 1998 17:39:28 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id RAA00782 for <ietf-archive@cnri.reston.va.us>; Tue, 4 Aug 1998 17:39:46 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Tue, 4 Aug 1998 17:30:07 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id RAA00202 for ipp-outgoing; Tue, 4 Aug 1998 17:26:45 -0400 (EDT)
From: Van Dang <dangv@ecs.csus.edu>
Message-Id: <199808042126.OAA12738@gaia.ecs.csus.edu>
Subject: IPP> conflicting "attributes-charset"
To: ipp@pwg.org
Date: Tue, 04 Aug 1998 14:26:20 -0700
Mailer: Elm [revision: 70.85]
Sender: owner-ipp@pwg.org
How should the server handle the situation where the "attributes-charset" of the response itself is "us-ascii", but one or more attributes in that response is in the "utf-8" format? Consider a case where a client sends a Print-Job request with "utf-8" as the value of "attributes-charset" and with the "job-name" attribute supplied. Later another client sends a Get-Job-Attribute or Get-Jobs request. This second request contains the "attributes-charset" with value "us-ascii" and "requested-attributes" attribute with exactly one value "job-name". According to the IPP-Mod document (section 3.1.4.2), the value of the "attributes-charset" for the response of the second request must be "us-ascii" since that is the charset specified in the request. The "job-name" value, however, is in "utf-8" format. Should the request be rejected even though both "utf-8" and "us-ascii" charsets are supported by the server? or should the "job-name" value be converted to "us-ascii" and return "successful-ok-conflicting-attributes" (0x0002) as the status code?