attachment

<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Ira,<div class=""><br class=""></div><div class="">I know this is a long-stale thread, but I was just re-reading RFC 2817, and Section 1 “Motivation” says this, which is germane to this subject (and even references IPP!):</div><div class=""><br class=""></div><div class="">
                
        
        
                <div class="page" title="Page 2">
                        <div class="layoutArea">
                                <div class="column">
                                        
                
        
        
                <pre class=""><span style="font-family: Courier; font-size: 10pt;" class="">1. Motivation</span></pre><pre class=""><span style="font-size: 10.000000pt; font-family: 'Courier'" class="">   The historical practice of deploying HTTP over SSL3 [3] has
   distinguished the combination from HTTP alone by a unique URI scheme
   and the TCP port number. The scheme ’http’ meant the HTTP protocol
   alone on port 80, while ’https’ meant the HTTP protocol over SSL on
   port 443.  Parallel well-known port numbers have similarly been
   requested -- and in some cases, granted -- to distinguish between
   secured and unsecured use of other application protocols (e.g.
   snews, ftps). This approach effectively halves the number of
   available well known ports.
</span></pre>
                                        <pre class=""><span style="font-size: 10.000000pt; font-family: 'Courier'" class="">   At the Washington DC IETF meeting in December 1997, the Applications
   Area Directors and the IESG reaffirmed that the practice of issuing
   parallel "secure" port numbers should be deprecated. The HTTP/1.1
   Upgrade mechanism can apply Transport Layer Security [6] to an open
   HTTP connection.
</span></pre>
                                </div>
                        </div>
                </div></div><div class="">Just wanted to share this with the group, for whatever reason.</div><div class=""><br class=""><div class="">
<div style="orphans: auto; text-align: start; text-indent: 0px; widows: auto; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="orphans: auto; text-align: start; text-indent: 0px; widows: auto; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="orphans: 2; text-align: -webkit-auto; text-indent: 0px; widows: 2; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="orphans: 2; text-align: -webkit-auto; text-indent: 0px; widows: 2; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Smith<br class=""><br class="">/**<br class="">&nbsp; &nbsp; Smith Kennedy<br class="">&nbsp; &nbsp;&nbsp;Wireless Architect - Client&nbsp;Software - IPG-PPS<br class="">&nbsp; &nbsp; Hewlett-Packard Co.<br class="">*/<br class=""><br class=""><br class=""></div></div></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 2014-04-07, at 2:50 PM, Ira McDonald &lt;<a href="mailto:blueroofmusic@gmail.com" class="">blueroofmusic@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class="">Hi,<br class=""><br class=""></div>Found this afternoon by browsing of I-Ds from the active IETF WGs<br class=""></div>top-level list:<br class=""><br class=""><a href="https://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/" class="">https://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/</a><br class="">

</div><br class="">NOTE:&nbsp; This document does consider reuse of the same port for both<br class=""></div>ordinary and secure implementations of the same service.&nbsp; It doesn't<br class="">take a position, except that the whole document is about conservation<br class="">

</div>of the IANA-assigned port space.<br class=""><br class=""></div>Certainly our port 631 reuse in 'ipp:' and 'ipps:' URI is allowed (and <br class="">apparently encouraged) by this I-D.<br class=""><br class=""></div><div class="">Cheers,<br class=""></div><div class="">- Ira<br class="">

<br clear="all" class=""></div><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div dir="ltr" class="">Ira McDonald (Musician / Software Architect)<br class="">Co-Chair - TCG Trusted Mobility Solutions WG<br class="">Chair - Linux Foundation Open Printing WG<br class="">

Secretary - IEEE-ISTO Printer Working Group<br class="">Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br class="">IETF Designated Expert - IPP &amp; Printer MIB<br class="">Blue Roof Music / High North Inc<br class=""><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank" class="">http://sites.google.com/site/blueroofmusic</a><br class="">

<a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank" class="">http://sites.google.com/site/highnorthinc</a><br class="">mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank" class="">blueroofmusic@gmail.com</a><br class="">

Winter&nbsp; 579 Park Place&nbsp; Saline, MI&nbsp; 48176&nbsp; 734-944-0094<br class="">Summer&nbsp; PO Box 221&nbsp; Grand Marais, MI 49839&nbsp; 906-494-2434<br class=""><br class=""><div style="display:inline" class=""></div><div style="display:inline" class=""></div><div style="display:inline" class=""></div>

<div class=""></div><div class=""></div><div class=""></div><div class=""></div></div></div>
</div></div></div></div></div></div></div></div></div></div>
</div></blockquote></div><br class=""></div></body></html>