IPP> MOD - 36) ISSUE: Don't require 1.0 support and add REQU IRED "version-numbers-supported" attribute

IPP> MOD - 36) ISSUE: Don't require 1.0 support and add REQU IRED "version-numbers-supported" attribute

IPP> MOD - 36) ISSUE: Don't require 1.0 support and add REQU IRED "version-numbers-supported" attribute

Hastings, Tom N hastings at cp10.es.xerox.com
Mon May 10 15:15:58 EDT 1999


In looking that the definitions of the '1.0' and '1.1' keywords for the new
REQUIRED attribute "ipp-versions-supported", we've come up with the
following detailed nits:

1. we need to include the encoding as part of the version number.

2. Rather than the vague phrase about extensions in this document that would
not compromise interoperability with IPP/1.0 clients, we need to allow any
extension in this Model document, as long as the behavior for a '1.0'
request is followed.

So far we have required that the "time-at-xxx" job attributes MUST NOT use
the dateTime choice if the request "version-number" parameter is '1.0'.

3. We need to say something about extensions that get registered

4. We have to say something about future Model and Semantics documents.

so how about the following clarified text:

4.4.n ipp-versions-supported(1setOf type2 keyword)

This REQUIRED attribute identifies the IPP protocol versions that this
Printer supports, including minor versions, i.e., the values of the
"version-number" parameter that it will accept in requests and return in
responses.  If an IPP Printer receives a request with the "version-number"
parameter set to a (two-octet binary) value that does not correspond to one
of the values of this (US-ASCII) keyword, it MUST reject the request and
return the 'server-error-version-not-supported' status code.  See Section
3.1.8.

The following standard keyword values are defined:
 
'1.0': Version 1.0 as specified in RFC 2566 [RFC2566] and RFC 2565 [RFC2565]
including any extensions registered according to Section 6 and any extension
defined in this version or any future version of this document following the
rules when the "version-number" parameter is '1.0', if any.  For an example
of such an '1.0' rule, see section 4.3.12.

'1.1': Version 1.1 as specified in this document and [IPP-PRO] including any
extensions registered according to Section 6 or defined in any future
version of this document following the rules when the "version-number"
parameter is '1.1', if any.

-----Original Message-----
From: Hastings, Tom N [mailto:hastings at cp10.es.xerox.com]
Sent: Wednesday, May 05, 1999 01:20
To: ipp
Subject: IPP> MOD - 36) ISSUE: Don't require 1.0 support and add
REQUIRED "ver sion-numbers-supported" attribute


At last week's telecon with a good number of people participating, we
relaxed the requirement that an IPP/1.1 Client and Printer MUST support
IPP/1.0 requests and responses and made it a SHOULD.  As a consequence, we
agreed also agreed that we have to add a REQUIRED
"version-numbers-supported" so that a client can determine which versions
are supported.  This attribute will also be added to the RECOMMEND list in
the directory appendix list.
36) ISSUE:  Don't require 1.0 support and add REQUIRED
"version-numbers-supported" attribute
RECOMMEND, rather than REQUIRE, conforming IPP/1.1 clients and the IPP/1.1
Printers to support IPP/1.0 requests and responses.  Therefore, add an
"ipp-versions-supported" Printer Description attribute.  Also add this
attribute as RECOMMENDED in the directory schema list in the Appendix.

Suggested text:

4.4.n ipp-versions-supported(1setOf type2 keyword)

This REQUIRED attribute identifies the IPP protocol versions that this
Printer supports, including minor versions.  If an IPP Printer receives a
request with the "version-number" parameter set to a (two-octet binary)
value that does not correspond to one of the values of this (US-ASCII)
keyword, it MUST reject the request and return the
'server-error-version-not-supported' status code.  See Section 3.1.7.

The following standard keyword values are defined: 

	'1.0': Version 1.0 as specified in [RFC 2566] including any
extension defined in this document that would not compromise
interoperability with client or Printer that conforms to RFC 2566.
	'1.1': Version 1.1 as specified in this document.

snip...



More information about the Ipp mailing list