Sign in or 
Share this
SIP RFCs
| This is a big list of RFCs related to SIP - all courtesy of the IETF | ||
| RFC 3524 | Mapping of Media Streams to Resource Reservation Flows | This document defines an extension to the Session Description Protocol (SDP) grouping framework. It allows requesting a group of media streams to be mapped into a single resource reservation flow. The SDP syntax needed is defined, as well as a new "semantics" attribute called Single Reservation Flow (SRF). |
| RFC 3515 | The Session Initiation Protocol (SIP) Refer Method | Defines the REFER method. This Session Initiation Protocol (SIP) extension requests that the recipient REFER to a resource provided in the request. It provides a mechanism allowing the party sending the REFER to be notified of the outcome of the referenced request. This can be used to enable many applications, including call transfer. In addition to the REFER method, this document defines the the refer event package and the Refer-To request header. |
| RFC 3487 | Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP) | Summarizes requirements for prioritizing access to circuit-switched network, end system and proxy resources for emergency preparedness communications using the Session Initiation Protocol (SIP). |
| RFC 3486 | Compressing the Session Initiation Protocol (SIP) | Describes a mechanism to signal that compression is desired for one or more Session Initiation Protocol (SIP) messages. It also states when it is appropriate to send compressed SIP messages to a SIP entity. |
| RFC 3485 | The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp) | The Session Initiation Protocol (SIP) is a text-based protocol for initiating and managing communication sessions. The protocol can be compressed by using Signaling Compression (SigComp). Similarly, the Session Description Protocol (SDP) is a text-based protocol intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. This memo defines the SIP/SDP-specific static dictionary that SigComp may use in order to achieve higher higher efficiency. The dictionary is compression algorithm independent. |
| RFC 3428 | Session Initiation Protocol (SIP) Extension for Instant Messaging | Instant Messaging (IM) refers to the transfer of messages between users in near real-time. These messages are usually, but not required to be, short. IMs are often used in a conversational mode, that is, the transfer of messages back and forth is fast enough for participants to maintain an interactive conversation. This document proposes the MESSAGE method, an extension to the Session Initiation Protocol (SIP) that allows the transfer of Instant Messages. Since the MESSAGE request is an extension to SIP, it inherits all the request routing and security features of that protocol. MESSAGE requests carry the content in the form of MIME body parts. MESSAGE requests do not themselves initiate a SIP dialog; under normal usage each Instant Message stands alone, much like pager messages. MESSAGE requests may be sent in the context of a dialog initiated by some other SIP request. |
| RFC 3420 | Internet Media Type message/sipfrag | This document registers the message/sipfrag Multipurpose Internet Mail Extensions (MIME) media type. This type is similar to message/sip, but allows certain subsets of well formed Session Initiation Protocol (SIP) messages to be represented instead of requiring a complete SIP message. In addition to end-to-end security uses, message/sipfrag is used with the REFER method to convey information about the status of a referenced request. |
| RFC 3388 | Grouping of Media Lines in Session Description Protocol (SDP) | Extensions to SDP that allow grouping of media streams for lip synchronization and to represent the same content on different network addresses |
| RFC 3361 | Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers | Defines a DHCP option for locating the outbound SIP proxy server |
| RFC 3319 | Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers | Defines a DHCPv6 options for locating the outbound SIP proxy server |
| RFC 3327 | Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts | Defines the Path header field that registers a list of proxies between the UA and the registrar |
| RFC 3326 | The Reason Header Field for the Session Initiation Protocol (SIP) | For creating services, it is often useful to know why a Session Initiation Protocol (SIP) request was issued. This document defines a header field, Reason, that provides this information. The Reason header field is also intended to be used to encapsulate a final status code in a provisional response. This functionality is needed to resolve the "Heterogeneous Error Response Forking Problem", or HERFP. |
| RFC 3325 | Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks | Defines P-Asserted-Identity and P-Preferred-Identity header fields, allowing SIP proxies to add user identity information and callers to request privacy |
| RFC 3324 | Short Term Requirements for Network Asserted Identity | Defines requirements for caller identities established by network entities |
| RFC 3323 | A Privacy Mechanism for the Session Initiation Protocol (SIP) | Describes SIP caller privacy issues and defines the Privacy header field |
| RFC 3329 | Security Mechanism Agreement for the Session Initiation Protocol (SIP) | This document defines new functionality for negotiating the security mechanisms used between a Session Initiation Protocol (SIP) user agent and its next-hop SIP entity. This new functionality supplements the existing methods of choosing security mechanisms between SIP entities. |
| RFC 3313 | Private Session Initiation Protocol (SIP) Extensions for Media Authorization | Describes the need for Quality of Service (QoS) and media authorization and defines a Session Initiation Protocol (SIP) extension that can be used to integrate QoS admission control with call signaling and help guard against denial of service attacks. The use of this extension is only applicable in administrative domains, or among federations of administrative domains with previously agreed-upon policies, where both the SIP proxy authorizing the QoS, and the policy control of the underlying network providing the QoS, belong to that administrative domain or federation of domains. |
| RFC 3312 | Integration of Resource Management and SIP | Framework for preconditions |
| RFC 3311 | The Session Initiation Protocol (SIP) UPDATE Method | This specification defines the new UPDATE method for the Session Initiation Protocol (SIP). UPDATE allows a client to update parameters of a session (such as the set of media streams and their codecs) but has no impact on the state of a dialog. In that sense, it is like a re-INVITE, but unlike re-INVITE, it can be sent before the initial INVITE has been completed. This makes it very useful for updating session parameters within early dialogs. |
| RFC 3261 | SIP: Session Initiation Protocol | Core protocol specification; obsoletes RFC 2543. |
| RFC 3262 | Reliability of Provisional Responses in the Session Initiation Protocol (SIP) | Making 1xx responses reliable; introduces PRACK method |
| RFC 3263 | Session Initiation Protocol (SIP): Locating SIP Servers | Describes DNS mechanisms (NAPTR, SRV) for locating SIP servers |
| RFC 3264 | An Offer/Answer Model with the Session Description Protocol (SDP) | How SDP is used within SIP to negotiate sessions |
| RFC 3265 | Session Initiation Protocol (SIP)-Specific Event Notification | SIP event model; defines SUBSCRIBE and NOTIFY |
| RFC 3087 | Control of Service Context using SIP Request-URI | Defines how the SIP URI can be used to invoke services such as voicemail |
| RFC 3050 | Common Gateway Interface for SIP | sip-cgi, as scripting interface |
| RFC 2976 | The SIP INFO Method | Defines INFO method for carrying SIP-related information |
| RFC 2848 | The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services | |
vocale |
Latest page update: made by vocale
, Jul 15 2008, 10:41 AM EDT
(about this update
About This Update
Edited by vocale
view changes - complete history) |
|
Keyword tags:
None
More Info: links to this page
|
There are no threads for this page.
Be the first to start a new thread.
