Hi Dave and Alan, Friday (6 June 2003)
Below is one entire new section, new text for three existing sections,
and some revised examples for existing sections, for the PSI spec.
Cheers,
- Ira
----------------------------------------
[Entire new section 7.1 - please delete entirely former section 7.1.1]
7.1 'PWG Standard URI Query Parameters'
The following PWG standard URI query parameters are defined for use with
any URL scheme in specifying Target Device Identifiers (section 7.2),
Reference URI (section 7.3), or any other URI.
Conformance:
(1) A PSI Client MUST specify each parameter keyword in lowercase.
(2) A PSI Client MUST specify well-known parameter values in lowercase.
(3) A PSI Client MAY specify string parameter values in mixed case.
7.1.1 'auth'
Client authentication mechanism required to access this URI, e.g.,
ipp://bar.com/printer?auth=digest
Well-known values defined in section 4.4.2 of [RFC2911] are:
'none': no user authentication (i.e., 'anonymous').
'requesting-user-name': user specified in protocol operation.
'basic': HTTP basic authentication [RFC2617].
'digest': HTTP digest authentication [RFC2617].
'certificate': user authenticated via certificate.
7.1.2 'binary'
Binary transfer mode required to access this URI, e.g.,
blues@myhost.com:21/somefile.pdf?passive=true&binary=true">ftp://joe:blues@myhost.com:21/somefile.pdf?passive=true&binary=true
Well-known values are:
'true': Use binary transfer mode.
'false': Use text transfer mode (default, when absent).
7.1.3 'cert'
Client certificate URI required to access this URI, e.g.,
ipp://bar.com/printer?auth=certificate&sec=tls&cert=ldap://f.com/abc
7.1.4 'domain'
Domain name for any non-Internet URI scheme, e.g.,
pwg-unc://PrintServer15/*?domain=Accounting
7.1.5 'legacy'
Legacy Target Device Identifier specified as a URI for PSI proxy, e.g.,
pwg-psitd://ps.foo.com/psi/1.0?legacy=pwg-unc://server/share
7.1.6 'location'
Human-readable geographic location referenced by this URI, e.g.,
http://pwg-psitd:/foo.com/psi/1.0?location=First%20Floor
7.1.7 'name'
Human-readable friendly name referenced by this URI, e.g.,
http://pwg-psitd:/foo.com/psi/1.0?name=Dave's%20Printer
7.1.8 'passive'
Passive mode required to access this URI, e.g.,
blues@myhost.com:21/somefile.txt?passive=true">ftp://joe:blues@myhost.com:21/somefile.txt?passive=true
Well-known values are:
'true': Use passive mode.
'false': Do not use passive mode (default, when absent).
7.1.9 'pw'
Password required to access this URI, e.g.,
pop://joe;auth=login@foo.com:110?sec=ssl3&pw=bingo&msgid=123
7.1.10 'sec'
Security mechanism required to access this URI, e.g.,
ipp://bar.com/printer?auth=digest&sec=tls
Well-known values defined in section 4.4.3 of [RFC2911] are:
'none': no security mechanism (i.e., 'anonymous').
'ssl3': SSL3 [SSL] security for communications channel.
'tls': TLS [RFC2246] security for communications channel.
----------------------------------------
[ [ Dave - add examples in former TD Identifier sections. ] ]
[ [ New text for former section 7.1.6 'ipp' ] ]
A URL for an IPP print service [RFC2911].
Example:
ipp://bar.com:631/printer?auth=digest&sec=tls
Notes:
(1) REQUIRED 'host' here is 'bar.com'
(2) OPTIONAL 'port' here is '631' (default for IPP)
(3) OPTIONAL 'path' here is 'printer'
(4) PSI standard query 'auth' here is 'digest' [RFC2617]
(5) PSI standard query 'sec' here is 'tls' [RFC2246]
[ [ New text for former section 7.1.7 'ippfax' ] ]
A URL for an IPPFAX print service [IPPFAX].
Example:
ippfax://foo.com/faxprinter?auth=certificate
Notes:
(1) REQUIRED 'host' here is 'foo.com'
(2) OPTIONAL 'path' here is 'faxprinter'
(3) PSI standard query 'auth' here is 'certificate'
[ [ New text for former section 7.1.8 'lpr' ] ]
A URL for an LPR print service [RFC1179].
Example:
lpr://bar.com:515/printer?location=First%20Floor
Notes:
(1) REQUIRED 'host' here is 'bar.com'
(2) OPTIONAL 'port' here is '515' (default for LPR)
(3) OPTIONAL 'path' here is 'printer'
(4) PSI standard query 'location' here is 'First Floor'
----------------------------------------
[ [ Dave - fix broken examples in former Reference sections. ] ]
[ [ Corrected example for former section 7.2.2 'ftp' ] ]
blues@myhost.com:21/somefile.pdf?passive=true&binary=true">ftp://joe:blues@myhost.com:21/somefile.pdf?passive=true&binary=true
[ [ Corrected example for former section 7.2.4 'pop' ] ]
pop://joe;auth=login@foo.com:110?sec=ssl3&pw=bingo&msgid=123
&attid=1.doc,2.doc,etc
[ [ Corrected example for former section 7.2.5 'imap' ] ]
imap://joe;auth=login@foo.com:143?sec=ssl3&pw=bingo&msgid=123
&attid=1.doc,2.doc,etc
----------------------------------------
This archive was generated by hypermail 2b29 : Thu Jun 05 2003 - 21:04:33 EDT