Extensions to the SIP for the IP multimedia subsystem

The Session Initiation Protocol (SIP) is the signaling protocol selected by the 3rd Generation Partnership Project (3GPP)[1][2] to create and control multimedia sessions with two or more participants in the IP Multimedia Subsystem (IMS), and therefore is a key element in the IMS framework.

SIP was developed by the Internet Engineering Task Force (IETF) to become a standard for controlling multimedia sessions in Internet Protocol (IP) networks, working in the application layer. Several SIP extensions[3][4][5] have been added to the basic protocol specification[6] in order to extend its functionality. These extensions are based on Request for Comments (RFC) protocol recommendations by the IETF.

The 3GPP, which is a collaboration between groups of telecommunications associations aimed at developing and maintaining the IMS, stated a series of requirements for SIP[1] to be successfully used in the IMS. Some of them could be addressed by using existing capabilities and extensions in SIP while, in other cases, the 3GPP had to collaborate with the IETF to standardize new SIP extensions[7] to meet the new requirements. In any case, the IETF evolves SIP in a generic basis, so that the use of its extensions is not restricted to the IMS framework.

3GPP requirements on SIP

There are some general requirements stated by the 3GPP for the IMS to work successfully. These include an efficient use of the radio interface by minimizing the exchange of signaling messages between the mobile terminal and the network, a minimum session setup time by performing tasks prior to session establishment instead of during session establishment, a minimum support required in the terminal, the support for roaming and non-roaming scenarios with terminal mobility management (supported by the access network, not SIP), and support for IPv6 addresses.

Other requirements are more specific and involve SIP modifications, such as new header fields to exchange user or server's information, and new SIP methods to support new network functionality: requirement for registration, re-registration, de-registration, subscription to events and notifications, instant messaging or call control primitives with additional capabilities such as call transference.

Some of these specific requirements[1] are:

Finally, it is also necessary that other protocols and network services such as DHCP or DNS[8] are adapted to work with SIP, for instance for outbound proxy (P-CSCF) location and SIP Uniform Resource Identifier (URI) to IP address resolution, respectively.

Extension negotiation mechanism

There is a mechanism[2] in SIP for extension negotiation between user agents (UA) or servers, consisting of three header fields: supported, require and unsupported, which UAs or servers (i.e. user terminals or call session control function (CSCF) in IMS) may use to specify the extensions they understand. When a client initiates a SIP dialog with a server, it states the extensions it requires to be used and also other extensions that are understood (supported), and the server will then send a response with a list of extensions that it requires. If these extensions are not listed in the client's message, the response from the server will be an error response. Likewise, if the server does not support any of the client's required extensions, it will send an error response with a list of its unsupported extensions. This kind of extensions are called option tags, but SIP can also be extended with new methods. In that case, user agents or servers use the Allow header to state which methods they support. To require the use of a particular method in a particular dialog, they must use an option tag associated to that method.

SIP extensions

Caller preferences and user agent capabilities

These two extensions allow users to specify their preferences about the service the IMS provides.

With the caller preferences extension,[9] the calling party is able to indicate the kind of user agent they want to reach (e.g. whether it is fixed or mobile, a voicemail or a human, personal or for business, which services it is capable to provide, or which methods it supports) and how to search for it, with three header fields: Accept-Contact to describe the desired destination user agents, Reject-Contact to state the user agents to avoid, and Request-Disposition to specify how the request should be handled by servers in the network (i.e. whether or not to redirect and how to search for the user: sequentially or in parallel).

By using the user agent capabilities extension,[10] user agents (terminals) can describe themselves when they register so that others can search for them according to their caller preferences extension headers. For this purpose, they list their capabilities in the Contact header field of the REGISTER message.

Event notification

The aim of event notification is to obtain the status of a given resource (e.g. a user, one's voicemail service) and to receive updates of that status when it changes.

Event notification is necessary in the IMS framework to inform about the presence of a user (i.e. "online" or "offline") to others that may be waiting to contact them, or to notify a user and its P-CSCF of its own registration state, so that they know if they are reachable and what public identities they have registered. Moreover, event notification can be used to provide additional services such as voicemail (i.e. to notify that they have new voice messages in their inbox).

To this end, the specific event notification extension[11] defines a framework for event notification in SIP, with two new methods: SUBSCRIBE and NOTIFY, new header fields and response codes and two roles: the subscriber and the notifier. The entity interested in the state information of a resource (the subscriber) sends a SUBSCRIBE message with the Uniform Resource Identifier (URI) of the resource in the request initial line, and the type of event in the Event header. Then the entity in charge of keeping track of the state of the resource (the notifier), receives the SUBSCRIBE request and sends back a NOTIFY message with a subscription-state header as well as the information about the status of the resource in the message body. Whenever the resource state changes, the notifier sends a new NOTIFY message to the subscriber. Each kind of event a subscriber can subscribe to is defined in a new event package. An event package describes a new value for the SUBSCRIBE Event header, as well as a MIME type to carry the event state information in the NOTIFY message.

There is also an allow-events header to indicate event notification capabilities, and the 202 accepted and 489 bad event response codes to indicate if a subscription request has been preliminary accepted or has been turned down because the notifier does not understand the kind of event requested.

In order to make an efficient use of the signaling messages, it is also possible to establish a limited notification rate (not real-time notifications) through a mechanism called event throttling. Moreover, there is also a mechanism for conditional event notification that allows the notifier to decide whether or not to send the complete NOTIFY message depending on if there is something new to notify since last subscription or there is not.

State publication

The event notification framework defines how a user agent can subscribe to events about the state of a resource, but it does not specify how that state can be published. The SIP extension for event state publication[12] was defined to allow user agents to publish the state of an event to the entity (notifier) that is responsible for composing the event state and distributing it to the subscribers.

The state publication framework defines a new method: PUBLISH, which is used to request the publication of the state of the resource specified in the request-URI, with reference to the event stated in the Event header, and with the information carried in the message body.

Instant messaging

The functionality of sending instant messages to provide a service similar to text messaging is defined in the instant messaging extension.[13] These messages are unrelated to each other (i.e. they do not originate a SIP dialog) and sent through the SIP signaling network, sharing resources with control messages.

This functionality is supported by the new MESSAGE method, that can be used to send an instant message to the resource stated in the request-URI, with the content carried in the message body. This content is defined as a MIME type, being text/plain the most common one.

In order to have an instant messaging session with related messages, the Message Session Relay Protocol (MSRP)[14] should be used.

Call transfer

The REFER method extension[15] defines a mechanism to request a user agent to contact a resource which is identified by a URI in the Refer-To header field of the request message. A typical use of this mechanism is call transfer: during a call, the participant who sends the REFER message tells the recipient to contact to the user agent identified by the URI in the corresponding header field. The REFER message also implies an event subscription to the result of the operation, so that the sender will know whether or not the recipient could contact the third person.

However, this mechanism is not restricted to call transfer, since the Refer-To header field can be any kind of URI, for instance, an HTTP URI, to require the recipient to visit a web page.

Reliability of provisional responses

In the basic SIP specification,[6] only requests and final responses (i.e. 2XX response codes) are transmitted reliably, this is, they are retransmitted by the sender until the acknowledge message arrives (i.e. the corresponding response code to a request, or the ACK request corresponding to a 2XX response code). This mechanism is necessary since SIP can run not only over reliable transport protocols (TCP) that assure that the message is delivered, but also over unreliable ones (UDP) that offer no delivery guarantees, and it is even possible that both kinds of protocols are present in different parts of the transport network.

However, in such an scenario as the IMS framework, it is necessary to extend this reliability to provisional responses to INVITE requests (for session establishment, this is, to start a call). The reliability of provisional responses extension[16] provides a mechanism to confirm that provisional responses such as the 180 Ringing response code, that lets the caller know that the callee is being alerted, are successfully received. To do so, this extension defines a new method: PRACK, which is the request message used to tell the sender of a provisional response that his or her message has been received. This message includes a RACK header field which is a sequence number that matches the RSeq header field of the provisional response that is being acknowledged, and also contains the CSeq number that identifies the corresponding INVITE request. To indicate that the user agent requests or supports reliable provisional responses, the 100rel option tag will be used.

Session description updating

The aim of the UPDATE method extension[17] is to allow user agents to provide updated session description information within a dialog, before the final response to the initial INVITE request is generated. This can be used to negotiate and allocate the call resources before the called party is alerted.

Preconditions

In the IMS framework, it is required that once the callee is alerted, the chances of a session failure are minimum. An important source of failure is the inability to reserve network resources to support the session, so these resources should be allocated before the phone rings. However, in the IMS, to reserve resources the network needs to know the callee's IP address, port and session parameters and therefore it is necessary that the initial offer/answer exchange to establish a session has started (INVITE request). In basic SIP, this exchange eventually causes the callee to be alerted. To solve this problem, the concept of preconditions[18] was introduced. In this concept the caller states a set of constraints about the session (i.e. codecs and QoS requirements) in the offer, and the callee responds to the offer without establishing the session or alerting the user. This establishment will occur if and only if both the caller and the callee agree that the preconditions are met.

The preconditions SIP extension affects both SIP, with a new option tag (precondition) and defined offer/answer exchanges, and Session Description Protocol (SDP), which is a format used to describe streaming media initialization parameters, carried in the body of SIP messages. The new SDP attributes are meant to describe the current status of the resource reservation, the desired status of the reservation to proceed with session establishment, and the confirmation status, to indicate when the reservation status should be confirmed.

The SDP offer/answer model using PRACK and UPDATE requests

In the IMS, the initial session parameter negotiation can be done by using the provisional responses and session description updating extensions, along with SDP in the body of the messages. The first offer, described by means of SDP, can be carried by the INVITE request and will deal with the caller's supported codecs. This request will be answered by the provisional reliable response code 183 Session Progress, that will carry the SDP list of supported codecs by both the caller and the callee. The corresponding PRACK to this provisional answer will be used to select a codec and initiate the QoS negotiation.

The QoS negotiation is supported by the PRACK request, that starts resource reservation in the calling party network, and it is answered by a 2XX response code. Once this response has been sent, the called party has selected the codec too, and starts resource reservation on its side. Subsequent UPDATE requests are sent to inform about the reservation progress, and they are answered by 2XX response codes. In a typical offer/answer exchange,[19] one UPDATE will be sent by the calling party when its reservation is completed, then the called party will respond and eventually finish allocating the resources. It is then, when all the resources for the call are in place, when the caller is alerted.

Identification and charging

In the IMS framework it is fundamental to handle user identities for authentication, authorization and accounting purposes. The IMS is meant to provide multimedia services over IP networks, but also needs a mechanism to charge users for it. All this functionality is supported by new special header fields.

P-headers

The Private Header Extensions to SIP,[7] also known as P-Headers, are special header fields whose applicability is limited to private networks with a certain topology and characteristics of lower layers' protocols. They were designed specifically to meet the 3GPP requirements because a more general solution was not available.

These header fields are used for a variety of purposes including charging and information about the networks a call traverses:

More private headers have been defined for user database accessing:

Asserted identity

The private extensions for asserted identity within trusted networks[23] are designed to enable a network of trusted SIP servers to assert the identity of authenticated users, only within an administrative domain with previously agreed policies for generation, transport and usage of this identification information. These extensions also allow users to request privacy so that their identities are not spread outside the trust domain. To indicate so, they must insert the privacy token id into the Privacy header field.[24]

The main functionality is supported by the P-Asserted-Identity extension header. When a proxy server receives a request from an untrusted entity and authenticates the user (i.e. verifies that the user is who he or she says that he or she is), it then inserts this header with the identity that has been authenticated, and then forwards the request as usual. This way, other proxy servers that receive this SIP request within the Trust Domain (i.e. the network of trusted entities with previously agreed security policies) can safely rely on the identity information carried in the P-Asserted-Identity header without the necessity of re-authenticating the user.

The P-Preferred-Identity extension header is also defined, so that a user with several public identities is able to tell the proxy which public identity should be included in the P-Asserted-Identity header when the user is authenticated.

Finally, when privacy is requested, proxies must withhold asserted identity information outside the trusted domain by removing P-Asserted-Identity headers before forwarding user requests to untrusted identities (outside the Trust Domain).

There exist analogous extension headers for handling the identification of services of users,[25] instead of the users themselves. In this case, Uniform Resource Names are used to identify a service (e.g. a voice call, an instant messaging session, an IPTV streaming)[26]

Security mechanisms

See also: IMS security

Access security in the IMS consists of first authenticating and authorizing the user, which is done by the S-CSCF, and then establishing secure connections between the P-CSCF and the user. There are several mechanisms to achieve this, such as:

The security mechanisms agreement extension for SIP[28] was then introduced to provide a secure mechanism for negotiating the security algorithms and parameters to be used by the P-CSCF and the terminal. This extension uses three new header fields to support the negotiation process:

Media authorization

The necessity in the IMS of reserving resources to provide quality of service (QoS) leads to another security issue: admission control and protection against denial-of-service attacks. To obtain transmission resources, the user agent must present an authorization token to the network (i.e. the policy enforcement point, or PEP) . This token will be obtained from its P-CSCF, which may be in charge of QoS policy control or have an interface with the policy control entity in the network (i.e. the policy decision function, or PDF) which originally provides the authorization token.

The private extensions for media authorization[29] link session signaling to the QoS mechanisms applied to media in the network, by defining the mechanisms for obtaining authorization tokens and the P-Media-Authorization header field to carry these tokens from the P-CSCF to the user agent. This extension is only applicable within administrative domains with trust relationships. It was particularly designed for specialized SIP networks like the IMS, and not for the general Internet.

Source-routing mechanisms

Source routing is the mechanism that allows the sender of a message to specify partially or completely the route the message traverses. In SIP, the route header field, filled by the sender, supports this functionality by listing a set of proxies the message will visit. In the IMS context, there are certain network entities (i.e. certain CSCFs) that must be traversed by requests from or to a user, so they are to be listed in the Route header field. To allow the sender to discover such entities and populate the route header field, there are mainly two extension header fields: path and service-route.

Path

The extension header field for registering non-adjacent contacts[30] provides a Path header field which accumulates and transmits the SIP URIs of the proxies that are situated between a user agent and its registrar as the REGISTER message traverses then. This way, the registrar is able to discover and record the sequence of proxies that must be transited to get back to the user agent.

In the IMS every user agent is served by its P-CSCF, which is discovered by using the Dynamic Host Configuration Protocol or an equivalent mechanism when the user enters the IMS network, and all requests and responses from or to the user agent must traverse this proxy. When the user registers to the home registrar (S-CSCF), the P-CSCF adds its own SIP URI in a Path header field in the REGISTER message, so that the S-CSCF receives and stores this information associated with the contact information of the user. This way, the S-CSCF will forward every request addressed to that user through the corresponding P-CSCF by listing its URI in the route header field.

Service Route

The extension for service route discovery during registration[31] consists of a Service-Route header field that is used by the registrar in a 2XX response to a REGISTER request to inform the registering user of the entity that must forward every request originated by him or her.

In the IMS, the registrar is the home network's S-CSCF and it is also required that all requests are handled by this entity, so it will include its own SIP URI in the service-route header field. The user will then include this SIP URI in the Route header field of all his or her requests, so that they are forwarded through the home S-CSCF.

Globally Routable User Agent URIs

In the IMS it is possible for a user to have multiple terminals (e.g. a mobile phone, a computer) or application instances (e.g. video telephony, instant messaging, voice mail) that are identified with the same public identity (i.e. SIP URI). Therefore, a mechanism is needed in order to route requests to the desired device or application. That is what a Globally Routable User Agent URI (GRU)[32] is: a URI that identifies a specific user agent instance (i.e. terminal or application instance) and it does it globally (i.e. it is valid to route messages to that user agent from any other user agent on the Internet).

These URIs are constructed by adding the gr parameter to a SIP URI, either to the public SIP URI with a value that identifies the user agent instance, or to a specially created URI that does not reveal the relationship between the GRUU and the user's identity, for privacy purposes. They are commonly obtained during the registration process: the registering user agent sends a Uniform Resource Name (URN) that uniquely identifies that SIP instance, and the registrar (i.e. S-CSCF) builds the GRUU, associates it to the registered identity and SIP instance and sends it back to the user agent in the response. When the S-CSCF receives a request for that GRUU, it will be able to route the request to the registered SIP instance.

Signaling compression

The efficient use of network resources, which may include a radio interface or other low-bandwidth access, is essential in the IMS in order to provide the user with an acceptable experience in terms of latency. To achieve this goal, SIP messages can be compressed using the mechanism known as SigComp[33] (signaling compression).

Compression algorithms perform this operation by substituting repeated words in the message by its position in a dictionary where all these words only appear once. In a first approach, this dictionary may be built for each message by the compressor and sent to the decompressor along with the message itself. However, as many words are repeated in different messages, the extended operations for SigComp[34] define a way to use a shared dictionary among subsequent messages. Moreover, in order to speed up the process of building a dictionary along subsequent messages and provide high compression ratios since the first INVITE message, SIP provides a static SIP/SDP dictionary [35] which is already built with common SIP and SDP terms.

There is a mechanism[36] to indicate that a SIP message is desired to be compressed. This mechanism defines the comp=sigcomp parameter for SIP URIs, which signals that the SIP entity identified by the URI supports SigComp and is willing to receive compressed messages. When used in request-URIs, it indicates that the request is to be compressed, while in Via header fields it signals that the subsequent response is to be compressed.

Content Indirection

In order to obtain even shorter SIP messages and make a very efficient use of the resources, the content indirection extension[37] makes it possible to replace a MIME body part of the message with an external reference, typically an HTTP URI. This way the recipient of the message can decide whether or not to follow the reference to fetch the resource, depending on the bandwidth available.

NAT Traversal

Network Address Translation (NAT) makes it impossible for a terminal to be reached from outside its private network, since it uses a private address that is mapped to a public one when packets originated by the terminal cross the NAT. Therefore, NAT traversal mechanisms are needed for both the signaling plane and the media plane.

Internet Engineering Task Force's RFC 6314[38] summarizes and unifies different methods to achieve this, such as symmetric response routing and client-initiated connections for SIP signaling, and the use of STUN, TURN and ICE, which combines both previous ones, for media streams

Internet Protocol version 6 compatibility

Internet Engineering Task Force's RFC 6157[39] describes the necessary mechanisms to guarantee that SIP works successfully between both Internet Protocol versions during the transition to IPv6. While SIP signaling messages can be transmitted through heterogeneous IPv4/IPv6 networks as long as proxy servers and DNS entries are properly configured to relay messages across both networks according to these recommendations, user agents will need to implement extensions so that they can directly exchange media streams. These extensions are related to the Session Description Protocol offer/answer initial exchange, that will be used to gather the IPv4 and IPv6 addresses of both ends so that they can establish a direct communication.

Interworking with other technologies

Apart from all the explained extensions to SIP that make it possible for the IMS to work successfully, it is also necessary that the IMS framework interworks and exchanges services with existing network infrastructures, mainly the Public switched telephone network (PSTN).

There are several standards that address this requirements, such as the following two for services interworking between the PSTN and the Internet (i.e. the IMS network):

And also for PSTN-SIP gateways to support calls with one end in each network:

Moreover, the SIP INFO method extension[44] is designed to carry user information between terminals without affecting the signaling dialog and can be used to transport the dual-tone multi-frequency signaling in order to provide classic telephone keypad services to users.

See also

References

  1. 1 2 3 Garcia-Martin, M. (May 2005). Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP). IETF. RFC 4083. https://tools.ietf.org/html/rfc4083. Retrieved November 29, 2014.
  2. 1 2 Camarillo, Gonzalo; García-Martín, Miguel A. (November 4, 2008). The 3G IP Multimedia Subsystem (IMS): Merging the Internet and the Cellular Worlds (3 ed.). John Wiley & Sons. pp. 55–336. ISBN 978-0-470-51662-1. Retrieved 15 November 2014.
  3. ↑ Poikselkä, Miikka; Mayer, Georg; Khartabil, Hisham; Niemi, Aki (March 10, 2006). The IMS: IP multimedia concepts and services (2 ed.). John Wiley & Sons. pp. 320–331. ISBN 978-0-470-01906-1. Retrieved 15 November 2014.
  4. ↑ Red Hat. "8.6. SIP AND IMS EXTENSIONS". https://access.redhat.com. Retrieved 15 November 2014. External link in |website= (help)
  5. ↑ Systems & Networks Training. "SIP in IMS". http://www.snt.co.uk. Retrieved 15 November 2014. External link in |website= (help)
  6. 1 2 3 Rosenberg, J. et al. (June 2002). SIP: Session Initiation Protocol. IETF. RFC 3261. https://tools.ietf.org/html/rfc3261. Retrieved November 15, 2014.
  7. 1 2 Jesske, R.; Drage, K.; Holmberg, C. (July 2014). Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3GPP. IETF. RFC 7315. https://tools.ietf.org/html/rfc7315. Retrieved November 15, 2014.
  8. ↑ Rosenberg, J.; Schulzrinne, H. (June 2002). Session Initiation Protocol (SIP): Locating SIP Servers. IETF. RFC 3263. https://tools.ietf.org/html/rfc3263. Retrieved December 1, 2014.
  9. ↑ Rosenberg, J.; Schulzrinne, H.; Kyzivat, P. (August 2004). Caller Preferences for the Session Initiation Protocol (SIP). IETF. RFC 3841. https://tools.ietf.org/html/rfc3841. Retrieved December 1, 2014.
  10. ↑ Rosenberg, J.; Schulzrinne, H.; Kyzivat, P. (August 2004). Indicating User Agent Capabilities in the Session Initiation Protocol (SIP). IETF. RFC 3840. https://tools.ietf.org/html/rfc3840. Retrieved December 1, 2014.
  11. ↑ Roach, A. (June 2002). Session Initiation Protocol (SIP)-Specific Event Notification. IETF. RFC 3265. https://tools.ietf.org/html/rfc3265. Retrieved December 1, 2014.
  12. ↑ Niemi, A. (October 2004). Session Initiation Protocol (SIP) Extension for Event State Publication. IETF. RFC 3903. https://tools.ietf.org/html/rfc3903. Retrieved December 2, 2014.
  13. ↑ Campbell, B.; Ed., Rosenberg; J., Schulzrinne; H., Huitema; C., and; D., Gurle (December 2002). Session Initiation Protocol (SIP) Extension for Instant Messaging. IETF. RFC 3428. https://tools.ietf.org/html/rfc3428. Retrieved December 2, 2014.
  14. ↑ Campbell, B.; Ed., Mahy; R., Ed.; Jennings, C. (September 2007). The Message Session Relay Protocol (MSRP). IETF. RFC 4975. https://tools.ietf.org/html/rfc4975. Retrieved December 2, 2014.
  15. ↑ Sparks, R. (April 2003). The Session Initiation Protocol (SIP) Refer Method. IETF. RFC 3515. https://tools.ietf.org/html/rfc3515. Retrieved December 2, 2014.
  16. ↑ Rosenberg, J.; Schulzrinne, H. (June 2002). Reliability of Provisional Responses in Session Initiation Protocol (SIP). IETF. RFC 3262. https://tools.ietf.org/html/rfc3262. Retrieved December 2, 2014.
  17. ↑ Rosenberg, J. (October 2002). The Session Initiation Protocol (SIP) UPDATE Method. IETF. RFC 3311. https://tools.ietf.org/html/rfc3311. Retrieved December 2, 2014.
  18. ↑ Camarillo, G.; Ed., Marshall; W., Ed.; Rosenberg, J. (October 2002). Integration of Resource Management and Session Initiation Protocol (SIP). IETF. RFC 3312. https://tools.ietf.org/html/rfc3312. Retrieved December 3, 2014.
  19. ↑ EvenHelix. "IMS to IMS call" (PDF). http://www.eventhelix.com/. Retrieved 3 December 2014. External link in |website= (help)
  20. ↑ Camarillo, G.; Blanco, G. (April 2006). The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-Header). IETF. RFC 4457. https://tools.ietf.org/html/rfc4457. Retrieved December 5, 2014.
  21. ↑ EvenHelix. "IMS registration" (PDF). http://www.eventhelix.com/. Retrieved 5 December 2014. External link in |website= (help)
  22. ↑ Camarillo, G.; Blanco, G. (August 2007). The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header). IETF. RFC 5002. https://tools.ietf.org/html/rfc5002. Retrieved December 5, 2014.
  23. ↑ Jennings, C.; Peterson, J.; Watson, M. (November 2002). Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks. IETF. RFC 3325. https://tools.ietf.org/html/rfc3325. Retrieved December 3, 2014.
  24. ↑ Peterson, J. (November 2002). A Privacy Mechanism for the Session Initiation Protocol (SIP). IETF. RFC 3323. https://tools.ietf.org/html/rfc3323. Retrieved December 3, 2014.
  25. ↑ Drage, K. (November 2010). A Session Initiation Protocol (SIP) Extension for the Identification of Services. IETF. RFC 6050. https://tools.ietf.org/html/rfc6050. Retrieved December 5, 2014.
  26. ↑ Rosenberg, J. (June 2010). Identification of Communications Services in the Session Initiation Protocol (SIP). IETF. RFC 5897. https://tools.ietf.org/html/rfc5897. Retrieved December 5, 2014.
  27. ↑ Niemi, A.; Arkko, J.; Torvinen, V. (September 2002). Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA). IETF. RFC 3310. https://tools.ietf.org/html/rfc3310. Retrieved December 5, 2014.
  28. ↑ Arkko, J.; Torvinen, V.; Camarillo, G.; Niemi, A.; Haukka, T. (January 2003). Security Mechanism Agreement for the Session Initiation Protocol (SIP). IETF. RFC 3329. https://tools.ietf.org/html/rfc3329. Retrieved December 5, 2014.
  29. ↑ Marshall, W. (January 2003). Private Session Initiation Protocol (SIP) Extensions for Media Authorization. IETF. RFC 3313. https://tools.ietf.org/html/rfc3313. Retrieved December 5, 2014.
  30. ↑ Willis, D.; Hoeneisen, B. (December 2002). Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts. IETF. RFC 3327. https://tools.ietf.org/html/rfc3327. Retrieved December 5, 2014.
  31. ↑ Willis, D.; Hoeneisen, B. (October 2003). Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration. IETF. RFC 3608. https://tools.ietf.org/html/rfc3608. Retrieved December 5, 2014.
  32. ↑ Rosenberg, J. (October 2009). Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP). IETF. RFC 5627. https://tools.ietf.org/html/rfc5627. Retrieved December 5, 2014.
  33. ↑ Price, R.; Bormann, C.; Christoffersson, J.; Hannu, H.; Liu, Z.; Rosenberg, J. (January 2003). Signaling Compression (SigComp). IETF. RFC 3320. https://tools.ietf.org/html/rfc3320. Retrieved December 4, 2014.
  34. ↑ Hannu, H.; Christoffersson, J.; Forsgren, S.; Leung, K.-C.; Liu, Z.; Price, R. (January 2003). Signaling Compression (SigComp) - Extended Operations. IETF. RFC 3321. https://tools.ietf.org/html/rfc3321. Retrieved December 4, 2014.
  35. ↑ Garcia-Martin, M.; Bormann, C.; Ott, J.; Price, R.; Roach, A. (February 2003). The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp). IETF. RFC 3485. https://tools.ietf.org/html/rfc3485. Retrieved December 4, 2014.
  36. ↑ Camarillo, G. (February 2003). Compressing the Session Initiation Protocol (SIP). IETF. RFC 3486. https://tools.ietf.org/html/rfc3486. Retrieved December 4, 2014.
  37. ↑ Burger, E. (May 2006). A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages. IETF. RFC 4483. https://tools.ietf.org/html/rfc4483. Retrieved December 4, 2014.
  38. ↑ Boulton, C.; Rosenberg, J.; Camarillo, G.; Audet, F. (July 2011). NAT Traversal Practices for Client-Server SIP. IETF. RFC 6314. https://tools.ietf.org/html/rfc6314. Retrieved December 5, 2014.
  39. ↑ Camarillo, G.; El, Malki; K., and; V., Gurbani (April 2011). IPv6 Transition in the Session Initiation Protocol (SIP). IETF. RFC 6157. https://tools.ietf.org/html/rfc6157. Retrieved December 5, 2014.
  40. ↑ Petrack, S.; Conroy, L. (June 2000). The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services. IETF. RFC 2848. https://tools.ietf.org/html/rfc2848. Retrieved December 5, 2014.
  41. ↑ Gurbani, V.; Ed., Brusilovsky; A., Faynberg; I., Gato; J., Lu; H., and; M., Unmehopa (October 2004). The SPIRITS (Services in PSTN requesting Internet Services) Protocol. IETF. RFC 3910. https://tools.ietf.org/html/rfc3910. Retrieved December 5, 2014.
  42. ↑ Vemuri, A.; Peterson, J. (RFC 3372). Session Initiation Protocol for Telephones (SIP-T): Context and Architectures. IETF. RFC 3372. https://tools.ietf.org/html/rfc3372. Retrieved December 5, 2014.
  43. ↑ Camarillo, G.; Roach, A.; Peterson, J.; Ong, L. (December 2002). Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping. IETF. RFC 3398. https://tools.ietf.org/html/rfc3398. Retrieved December 5, 2014.
  44. ↑ Holmberg, C.; Burger, E.; Kaplan, H. (January 2011). Session Initiation Protocol (SIP) INFO Method and Package Framework. IETF. RFC 6086. https://tools.ietf.org/html/rfc6086. Retrieved December 5, 2014.

Books

External links

This article is issued from Wikipedia - version of the 11/17/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.