Sips: URI scheme
From Wikipedia, the free encyclopedia
- The correct title of this article is sips: URI scheme. The initial letter is shown capitalized due to technical restrictions.
 |
This article is uncategorized.
Please help improve this article by adding it to one or more categories, so it may be associated with related articles (how?). Please remove this tag after categorizing. |
The SIPS URI scheme adheres to the syntax of the SIP URI, although the scheme string is "sips" rather than "sip".
SIPS allows resources to specify that they should be reached securely. It mandates that each hop over which the request is forwarded up to the target domain must be secured with TLS. The last hop from the proxy of the target domain to the user agent has to be secured according to local policies.
SIPS protects against attackers which try to listen on the signaling link. It does not provide real end-to-end security, since encryption is only hop-by-hop and every single intermediate proxy has to be trusted.
[edit] See also
- Session Initiation Protocol
- Security Descriptions for SDP
- Mikey key exchange method
- ZRTP end-to-end key exchange proposal
[edit] External links
- The SIPS URI scheme is described in RFC 3261
