attachment-0001
Hi Pete,<br><br>Given RFC 2911 and RFC 3510 examples, I'd say that<br>2 or more printer-uri-supported values can legally differ <br>only by the URI scheme - I've seen printers that list both<br>"http:" (for IPP/1.0 compatibility) and "ipp:" (for IPP/1.1)<br>
to the same target.<br><br>I think it's *unwise*.<br><br>But I don't think we can actually prohibit using both "ipp:"<br>(unsecured) and "ipps:" (TLS always) for the same IPP<br>Printer.<br><br>
I do think we should RECOMMEND against the practice,<br>because it supplies ambiguous security to the IPP Printer<br>object.<br><br>I've urged all of my printer vendor clients to NOT allow<br>both unauthenticated (guest) and authenticated (with at<br>
least HTTP Basic/Digest) access to the same instance <br>of IPP Printer object, because denial-of-service attacks<br>become much easier in this case.<br><br>All - your opinions?<br><br>Cheers,<br>- Ira<br><br clear="all">
Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Co-Chair - TCG Hardcopy WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a href="http://sites.google.com/site/blueroofmusic">http://sites.google.com/site/blueroofmusic</a><br>
<a href="http://sites.google.com/site/highnorthinc">http://sites.google.com/site/highnorthinc</a><br>mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><br>winter:<br> 579 Park Place Saline, MI 48176<br>
734-944-0094<br>summer:<br> PO Box 221 Grand Marais, MI 49839<br> 906-494-2434<br>
<br><br><div class="gmail_quote">On Mon, Aug 30, 2010 at 8:35 AM, Zehler, Peter <span dir="ltr"><<a href="mailto:Peter.Zehler@xerox.com">Peter.Zehler@xerox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Is it legal for two or more printer-uri-supported to differ only in the<br>
URI scheme?<br>
<br>
<br>
Peter Zehler<br>
<br>
Xerox Research Center Webster<br>
Email: Peter.Zehler@Xerox.com<br>
Voice: (585) 265-8755<br>
FAX: (585) 265-7441<br>
US Mail: Peter Zehler<br>
Xerox Corp.<br>
800 Phillips Rd.<br>
M/S 128-25E<br>
Webster NY, 14580-9701<br>
<div><div></div><div class="h5"><br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ipp-bounces@pwg.org">ipp-bounces@pwg.org</a> [mailto:<a href="mailto:ipp-bounces@pwg.org">ipp-bounces@pwg.org</a>] On Behalf Of Ira<br>
McDonald<br>
Sent: Wednesday, August 25, 2010 2:53 PM<br>
To: <a href="mailto:ipp@pwg.org">ipp@pwg.org</a>; Michael R Sweet; Ira McDonald<br>
Subject: [IPP] Initial draft of IPPS URI Scheme (25 August 2010)<br>
<br>
Hi,<br>
<br>
I've just posted an Initial draft of IPPS URI Scheme:<br>
<br>
<br>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100%0A825.txt" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100<br>
825.txt</a><br>
- plaintext Internet-Draft format (w/ explicit formfeeds)<br>
<br>
<br>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100%0A825.htm" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100<br>
825.htm</a><br>
- HTML w/ live table of contents<br>
<br>
Hint: You can view and print the plaintext file easily with<br>
MS WordPad.<br>
<br>
We agreed to do an IPP WG review first before submitting<br>
this document to the IETF Internet-Drafts Editor.<br>
<br>
This document was created by rewriting IPP URI Scheme<br>
[RFC3510].<br>
<br>
Comments?<br>
<br>
Cheers,<br>
- Ira (IPPS URI Scheme co-editor)<br>
<br>
-----------------------------------------------------<br>
Change Log<br>
<br>
25 August 2010 - draft-mcdonald-ipps-uri-scheme-00.txt<br>
- Editorial - complete rewrite of RFC 3510 for new transport binding<br>
- Technical - added section 3.2 IPP over HTTP Transport Binding<br>
- Technical - added section 3.3 IPP over HTTPS Transport Binding<br>
- Editorial - updated Appendix A w/ registration template from RFC 4395<br>
<br>
</div></div>--<br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner, and is<br>
believed to be clean.<br>
<br>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div><br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.