RFC 7065 - Appendix B. Design Notes
Appendix B. Design Notes
-
One recurring comment was to stop using the suffix "s" on the URI scheme, and to move the secure option to a parameter (e.g., ";proto=tls"). We decided against this idea because the STUN URI does not have a ";proto=" parameter and we would have lost the symmetry between the TURN and STUN URIs.
-
Following the advice of Section 2.2 of RFC 4395, and because the TURN URI does not describe a hierarchical structure, the TURN URIs are opaque URIs.
-
<password>is not used in the URIs because it is deprecated [RFC3986].<username>and<auth>are not used in the URIs because they do not guide the resolution mechanism. -
As discussed at IETF 72 in Dublin, there are no generic parameters in the URI to prevent compatibility issues.