Ira:
Looks good to me!
**********************************************
* Don Wright don@lexmark.com *
* Chair, Printer Working Group *
* Chair, IEEE MSC *
* *
* Director, Strategic & Technical Alliances *
* Lexmark International *
* 740 New Circle Rd *
* Lexington, Ky 40550 *
* 859-232-4808 (phone) 859-232-6740 (fax) *
**********************************************
imcdonald%sharplabs.com@interlock.lexmark.com on 02/01/2001 07:36:26 PM
To: ipp%pwg.org@interlock.lexmark.com,
imcdonald%crt.xerox.com@interlock.lexmark.com
cc: (bcc: Don Wright/Lex/Lexmark)
Subject: IPP> URL - Improved conformance for IPP URLs - 1 Feb 2001
Hi folks, Thursday (1 February 2001)
Based on feedback from Don Wright, Michael Sweet, and Carl Kugler (thank
you all), an improved conformance section for the IPP URL Scheme spec:
5. Conformance Requirements
5.1. Conformance Requirements for IPP Clients
IPP Clients that conform to this specification:
a) MUST send IPP URLs (e.g., in the "printer-uri" operation attribute
in 'Print-Job') that conform to the ABNF specified in section 4.4
of this document;
b) MUST send IPP operations via the port specified in the IPP URL (if
present) or otherwise via IANA assigned well-known port 631;
c) MUST convert IPP URLs to their corresponding HTTP URL forms
according to the rules in section 5 'IPP URL Scheme' in
[RFC-2910];
d) SHOULD interoperate with IPP/1.0 Printers according to the rules
in section 9 'Interoperability with IPP/1.0 Implementations' and
section 9.2 'Security and URL Schemes' in [RFC-2910].
5.2. Conformance Requirements for IPP Printers
IPP Printers that conform to this specification:
a) SHOULD reject received IPP URLs in "application/ipp" request
bodies (e.g., in the "printer-uri" attribute in a 'Print-Job'
request) that do not conform to the ABNF for IPP URLs specified in
section 4.4 of this document;
b) SHOULD return IPP URLs in "application/ipp" response bodies (e.g.,
in the "job-uri" attribute in a 'Print-Job' response) that do
conform to the ABNF for IPP URLs specified in section 4.4 of this
document;
c) MUST listen for IPP operations on IANA-assigned well-known port
631, unless explicitly configured by system administrators or site
policies;
d) SHOULD NOT listen for IPP operations on any other port, unless
explicitly configured by system administrators or site policies;
e) SHOULD interoperate with IPP/1.0 Clients according to the rules in
section 9 'Interoperability with IPP/1.0 Implementations' and
section 9.2 'Security and URL Schemes' in [RFC-2910].
Comments?
Cheers,
- Ira McDonald, consulting architect at Sharp and Xerox
High North Inc
PS - I've also greatly simplified the ABNF to _one_line_ taken from
HTTP/1.1 [RFC-2616] and clarified that the 'ipp:' URL scheme can only
be used for the [RFC-2910] mapping of the IPP model over HTTP.
This archive was generated by hypermail 2b29 : Mon Feb 05 2001 - 05:04:41 EST