The first obvious limitation is not with mutual authentication per However, there are some significant limitations. Torn down at will and does not rely on keeping the TLS connection This allows for TLS connections to be set up or Sending or receiving requests, the symmetrical nature of mutual TLS SIP a UA or a proxy acts both as UAC and UAS depending on if it is User agent server (UAS) takes on the role of TLS server. When establishing a TLS connection for receipt of a SIP request, a Takes on the role of TLS client in establishing a new TLS connection.
When sending a SIP request when there is notĪlready a suitable TLS connection in place, a user agent client (UAC) Proxy (or between two UAs), this implies that a UA is in possession In this model, both the TLS client and the TLS server provide aĬertificate in the TLS handshake phase. Outbound connections in a standard interoperable way. provides the mechanism for initiating and maintaining Will always be deliverable on the existing connection. This solution of having the UA always initiate and keep alive theĬonnection also solves the Network Address Translation (NAT) andįirewall problem as it ensures that responses and further requests Incoming call), the UA is expected to keep the TLS connection alive,Īnd that connection is expected to be reused for both incoming and
Since SIP allows for requests in both directions (e.g., an
URI SIP DEFINITION REGISTRATION
This directionality implies that the TLS connectionĪlways needs to be set up by the UA (e.g., during the registration If the proxy needs toĪuthenticate the UA, this can be achieved by SIP HTTP digestĪuthentication. Proxy does not use TLS to authenticate the UA. Server, and hence the UA uses TLS to authenticate the proxy but the This is applicable only between a user agent (UA) andĪ proxy, where the UA is the TLS client and the proxy is the TLS In this model, only the TLS server provides a certificate during the This section describes briefly the usage of TLS in SIP. "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisĭocument are to be interpreted as described in. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", It also makes normative changes to SIP (including both and Security (TLS) are underspecified in SIP and haveīeen a source of confusion for implementers. The meaning and usage of the SIPS URI scheme and of Transport Layer The Problems with the Meaning of SIPS in RFC 3261. Usage of the transport=tls URI Parameter and It for publication as an RFC or to translate it into languages otherġ. Not be created outside the IETF Standards Process, except to format
Outside the IETF Standards Process, and derivative works of it may The copyright in such materials, this document may not be modified
URI SIP DEFINITION LICENSE
Without obtaining an adequate license from the person(s) controlling Modifications of such material outside the IETF Standards Process. Material may not have granted the IETF Trust the right to allow The person(s) controlling the copyright in some of this This document may contain material from IETF Documents or IETFĬontributions published or made publicly available before Novemberġ0, 2008. The Trust Legal Provisions and are provided without warranty as
Include Simplified BSD License text as described in Section 4.e of
URI SIP DEFINITION CODE
Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal Distribution of this memo is unlimited.Ĭopyright (c) 2009 IETF Trust and the persons identified as the Official Protocol Standards" (STD 1) for the standardization stateĪnd status of this protocol. Please refer to the current edition of the "Internet Internet community, and requests discussion and suggestions for This document specifies an Internet standards track protocol for the Use of the SIPS URI scheme in the Session Initiation Protocol (SIP). This document provides clarifications and guidelines concerning the The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)
0 kommentar(er)
