Compression
rfc3261
rfc3264
rfc3263
rfc2327
rfc3262
rfc3266
draft-ietf-sip-sipfrag
rfc3326
draft-ietf-sipping-connect-reuse-reqs
draft-ietf-mmusic-fid
draft-kutscher-mmusic-sdpng-req
draft-ietf-sip-update
rfc2976
draft-ietf-sip-session-timer
draft-ietf-sip-183-00
draft-rosenberg-sip-reconstitute
draft-ietf-sip-sctp
draft-oran-sip-visited-00
draft-willis-sip-cookies
draft-pis-00
rfc3261.txt  | SIP: Session Initiation Protocol |
| Author(s) | J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, E. Schooler |
| Organization | ietf |
| State | proposed standard |
| Size | 647976 bytes |
| obsoletes | rfc2543.txt |
| updated by | rfc3265.txt rfc3853.txt |
| Abstract | This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. SIP invitations used to create sessions carry session descriptions that allow participants to agree on a set of compatible media types. SIP makes use of elements called proxy servers to help route requests to the user's current location, authenticate and authorize users for services, implement provider call-routing policies, and provide features to users. SIP also provides a registration function that allows users to upload their current locations for use by proxy servers. SIP runs on top of several different transport protocols. |
| rfc3264.txt | An Offer/Answer Model with Session Description Protocol (SDP) |
| Author(s) | J. Rosenberg, H. Schulzrinne |
| Organization | ietf |
| State | proposed standard |
| Size | 60854 bytes |
| obsoletes | rfc2543.txt |
| Abstract | This document defines a mechanism by which two entities can make use of the Session Description Protocol (SDP) to arrive at a common view of a multimedia session between them. In the model, one participant offers the other a description of the desired session from their perspective, and the other participant answers with the desired session from their perspective. This offer/answer model is most useful in unicast sessions where information from both participants is needed for the complete view of the session. The offer/answer model is used by protocols like the Session Initiation Protocol (SIP). |
| rfc3263.txt | Session Initiation Protocol (SIP): Locating SIP Servers |
| Author(s) | J. Rosenberg, H. Schulzrinne |
| Organization | ietf |
| State | proposed standard |
| Size | 42310 bytes |
| obsoletes | rfc2543.txt |
| Abstract | The Session Initiation Protocol (SIP) uses DNS procedures to allow a client to resolve a SIP Uniform Resource Identifier (URI) into the IP address, port, and transport protocol of the next hop to contact. It also uses DNS to allow a server to send a response to a backup client if the primary client has failed. This document describes those DNS procedures in detail. |
| rfc2327.txt | SDP: Session Description Protocol |
| Author(s) | M. Handley, V. Jacobson |
| Organization | ietf |
| State | proposed standard |
| Size | 87096 bytes |
| updated by | rfc3266.txt |
| Abstract | This document defines the Session Description Protocol, SDP. SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. This document is a product of the Multiparty Multimedia Session Control (MMUSIC) working group of the Internet Engineering Task Force. Comments are solicited and should be addressed to the working group's mailing list at confctrl@isi.edu and/or the authors. |
| rfc3262.txt | Reliability of Provisional Responses in Session Initiation Protocol (SIP) |
| Author(s) | J. Rosenberg, H. Schulzrinne |
| Organization | ietf |
| State | proposed standard |
| Size | 29643 bytes |
| obsoletes | rfc2543.txt |
| Abstract | This document specifies an extension to the Session Initiation Protocol (SIP) providing reliable provisional response messages. This extension uses the option tag 100rel and defines the Provisional Response ACKnowledgement (PRACK) method. |
| rfc3266.txt | Support for IPv6 in Session Description Protocol (SDP) |
| Author(s) | S. Olson, G. Camarillo, A. B. Roach |
| Organization | ietf |
| State | proposed standard |
| Size | 8693 bytes |
| updates | rfc2327.txt |
| Abstract | This document describes the use of Internet Protocol Version 6 (IPv6) addresses in conjunction with the Session Description Protocol (SDP). Specifically, this document clarifies existing text in SDP with regards to the syntax of IPv6 addresses. |
| draft-ietf-sip-sipfrag-00.txt | Internet Media Type message/sipfrag |
| Author(s) | R. Sparks |
| Organization | ietf |
| Working group | sip |
| State | unknown |
| Date | 2002-09-13 |
| Size | 15121 bytes |
| Abstract | This document registers the message/sipfrag MIME media type. This type is similar to message/sip , but allows certain subsets of well formed 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. |
| rfc3326.txt | The Reason Header Field for the Session Initiation Protocol (SIP) |
| Author(s) | H. Schulzrinne, D. Oran, G. Camarillo |
| Organization | ietf |
| State | proposed standard |
| Size | 15695 bytes |
| Abstract | 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. |
| draft-ietf-sipping-connect-reuse-reqs-00.txt | Requirements for Connection Reuse in the Session Initiation Protocol (SIP) |
| Author(s) | Rohan Mahy |
| Organization | ietf |
| Working group | sipping |
| State | unknown |
| Date | 2002-10-28 |
| Size | 21730 bytes |
| Abstract | When SIP entities use a connection oriented protocol to send a request, they typically originate their connections from an ephemeral port. The SIP protocol includes mechanisms which insure that responses to a request, and new requests sent in the original direction reuse an existing connection. However, new requests sent in the opposite direction are unlikely to reuse the existing connection. This frequently causes a pair of SIP entities to use one connection for requests sent in each direction, and can result in potential scaling and performance problems. This document presents requirements for addressing this shortcoming, and separately proposes an example mechanism which addresses this deficiency. |
| draft-ietf-mmusic-fid-06.txt | Grouping of m lines in SDP |
| Author(s) | H. Schulzrinne, Goran Eriksson, Gonzalo Camarillo, Jan Holler |
| Organization | ietf |
| Working group | mmusic |
| State | unknown |
| Date | 2002-02-28 |
| Size | 38831 bytes |
| Abstract | This document defines two SDP attributes: "group" and "mid". They allow to group together several "m" lines for two different purposes: for lip synchronization and for receiving media from a single flow (several media streams), encoded in different formats during a particular session, in different ports and host interfaces. |
draft-kutscher-mmusic-sdpng-req-02.txt
 |
| draft-ietf-sip-update-02.txt | The Session Initiation Protocol UPDATE Method |
| Author(s) | J. Rosenberg |
| Organization | ietf |
| Working group | sip |
| State | unknown |
| Date | 2002-05-01 |
| Size | 26903 bytes |
| Abstract | 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 can be sent before the initial INVITE has completed. This makes it very useful for updating session parameters within early dialogs. Table of Contents 1 Introduction ........................................ 3 2 Terminology ......................................... 3 3 Overview of Operation ............................... 3 4 Determining Support for this Extension .............. 4 5 UPDATE Handling ..................................... 4 5.1 Sending an UPDATE ................................... 4 5.2 Receiving an UPDATE ................................. 6 5.3 Processing the UPDATE Response ...................... 6 6 Proxy Behavior ...................................... 7 7 Definition of the UPDATE method ..................... 7 8 Example Call Flow ................................... 7 9 Security Considerations ............................. 11 10 IANA Considerations ................................. 11 11 Acknowledgements .................................... 11 12 Author's Addresses .................................. 11 13 Normative References ................................ 11 14 Informative References .............................. 12 |
| rfc2976.txt | The SIP INFO Method |
| Author(s) | S. Donovan |
| Organization | ietf |
| State | proposed standard |
| Size | 17736 bytes |
| Abstract | This document proposes an extension to the Session Initiation Protocol (SIP). This extension adds the INFO method to the SIP protocol. The intent of the INFO method is to allow for the carrying of session related control information that is generated during a session. One example of such session control information is ISUP and ISDN signaling messages used to control telephony call services. This and other example uses of the INFO method may be standardized in the future. |
| draft-ietf-sip-session-timer-10.txt | Session Initiation Protocol Extension for Session Timer |
| Author(s) | Jonathan Rosenberg, Steve Donovan |
| Organization | ietf |
| Working group | sip |
| State | unknown |
| Date | 2002-11-08 |
| Size | 61571 bytes |
| Abstract | This document defines an extension to the Session Initiation Protocol (SIP). This extension allows for a periodic refresh of SIP sessions through a re-INVITE or UPDATE request. The refresh allows both user agents and proxies to determine if the SIP session is still active. The extension defines two new header fields, Session-Expires, which conveys the lifetime of the session, and Min-SE, which conveys the minimum allowed value for the session timer. Table of Contents |
| draft-ietf-sip-183-00.txt
|
| draft-rosenberg-sip-reconstitute-01.txt
|
| draft-ietf-sip-sctp-03.txt | The Stream Control Transmission Protocol as a Transport for for the Session Initiation Protocol |
| Author(s) | Jonathan Rosenberg, Henning Schulzrinne, Gonzalo Camarillo |
| Organization | ietf |
| Working group | sip |
| State | unknown |
| Date | 2002-07-01 |
| Size | 17350 bytes |
| Abstract | This document specifies a mechanism for usage of SCTP (the Stream Control Transmission Protocol) as the transport between SIP entities. SCTP is a new protocol which provides several features that may prove beneficial for transport between SIP entities which exchange a large amount of messages, including gateways and proxies. As SIP is transport independent, support of SCTP is a relatively straightforward process, nearly identical to support for TCP. |
| draft-oran-sip-visited-00.txt
|
| draft-willis-sip-cookies-01.txt
|
| draft-pis-00.txt
|