Skip to content

Commit

Permalink
remove normative language from port usage sentence
Browse files Browse the repository at this point in the history
fixes #195
  • Loading branch information
mirjak committed Feb 8, 2021
1 parent 3ded00f commit f6a48f4
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions draft-ietf-quic-applicability.md
Original file line number Diff line number Diff line change
Expand Up @@ -458,11 +458,11 @@ assignments, and NATs.

As QUIC is a general purpose transport protocol, there are no requirements that
servers use a particular UDP port for QUIC. For applications with a fallback to
TCP that do not already have an alternate mapping to UDP, the registration (if
necessary) and use of the UDP port number corresponding to the TCP port already
registered for the application is RECOMMENDED. For example, the default port
for HTTP/3 {{QUIC-HTTP}} is UDP port 443, analogous to HTTP/1.1 or HTTP/2 over
TLS over TCP.
TCP that do not already have an alternate mapping to UDP, usually the
registration (if necessary) and use of the UDP port number corresponding to the
TCP port already registered for the application is approrpiate. For example,
the default port for HTTP/3 {{QUIC-HTTP}} is UDP port 443, analogous to HTTP/1.1
or HTTP/2 over TLS over TCP.

Applications could define an alternate endpoint discovery mechanism to allow
the usage of ports other than the default. For example, HTTP/3 ({{QUIC-HTTP}}
Expand Down

0 comments on commit f6a48f4

Please sign in to comment.