Subject: [httpwg/http-extensions] Advice on transport ports (#455)

From: HTTP issue updates <[email-masked]>
Date: Thu, 14 Dec 2017 01:42:16 +0000 (UTC)

> Applications that use HTTP SHOULD use the default port for the URL scheme in use. 

This isn't really necessary.  I would instead say that the port number is in the URL and cite [Initial URL Discovery](https://mnot.github.io/I-D/bcp56bis/#initial-url-discovery) for details.

Then explain that if you are bootstrapping from a bare hostname with `.well-known`, then this should assume the use of the default port for the scheme unless there are very good reasons.  In particular, when it comes to using port numbers other than the default, you can note that there are privacy implications (it makes your protocol distinguishable) and deployment implications (some middleboxes might interfere with the operation of your protocol).

(from @martinthomson)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/455