Login Form
RECENT IETF DRAFTS
SIP internet drafts statistics
- 41 SIP related internet drafts (IETF).
- 1 new and updated drafts posted in the last 14 days.
| Title | Author | Date |
| Instant Messaging and Presence Purpose for the Call-Info Header Field in the Session Initiation Protocol (SIP) | Peter Saint-Andre | 2013-05-14 |
| This document defines and registers a value of "impp" ("instant messaging and presence protocol") for the "purpose" header field parameter of the Call-Info header field in the Session Initiation Protocol (SIP). | ||
| Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Groupchat | Peter Saint-Andre, Salvatore Loreto, Saul Corretge, Fabio Forno | 2013-05-02 |
| This document defines a bidirectional protocol mapping for the exchange of instant messages in the context of a multiparty chat session among users of the Session Initiation Protocol (SIP) and users of the Extensible Messaging and Presence Protocol (XMPP). Specifically, this document defines a mapping between the XMPP Multi- User Chat (MUC) extension and the SIP-based Message Session Relay Protocol (MSRP). | ||
| CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) | Emil Ivov, Peter Saint-Andre, Enrico Marocco | 2013-05-02 |
| This document describes suggested practices for combined use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP). Such practices aim to provide a single fully featured real-time communication service by using complementary subsets of features from each of the protocols. Typically such subsets would include telephony capabilities from SIP and instant messaging and presence capabilities from XMPP. This specification does not define any new protocols or syntax for either SIP or XMPP. However, implementing it may require modifying or at least reconfiguring existing client and server-side software. Also, it is not the purpose of this document to make recommendations as to whether or not such combined use should be preferred to the mechanisms provided natively by each protocol (for example, SIP\'s SIMPLE or XMPP\'s Jingle). It merely aims to provide guidance to those who are interested in such a combined use. | ||
| A Group Text Chat Purpose for Conference and Service URIs in the Session Initiation Protocol (SIP) Event Package for Conference State | Emil Ivov | 2013-04-23 |
| This document defines and registers a value of "grouptextchat" ("Group Text Chat") value for the URI {purpose} element of SIP\'s Conference Event Package [RFC4575]. | ||
| Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to- Back User Agents (B2BUAs) | Hadriel Kaplan, Victor Pascual | 2013-04-18 |
| SIP Back-to-Back User Agents (B2BUAs) can cause unending SIP request routing loops because, as User Agent Clients, they can generate SIP requests with new Max-Forwards values. This document discusses the difficulties associated with loop detection for B2BUAs, and requirements for them to prevent infinite loops. | ||
| A Mechanism for Transporting User to User Call Control Information in SIP | Alan Johnston, James Rafferty | 2013-04-09 |
| There is a class of applications which benefit from using SIP to exchange User to User Information (UUI) data during session establishment. This information, known as call control UUI data, is a small piece of data inserted by an application initiating the session, and utilized by an application accepting the session. The rules which apply for a specific application are defined by a UUI package. This UUI data is opaque to SIP and its function is unrelated to any basic SIP function. This document defines a new SIP header field, User-to-User, to transport UUI data, along with an extension mechanism. | ||
| Session Initiation Protocol (SIP) Rate Control | Eric Noel, Philip Williams | 2013-04-08 |
| The prevalent use of Session Initiation Protocol (SIP) [RFC3261] in Next Generation Networks necessitates that SIP networks provide adequate control mechanisms to maintain transaction throughput by preventing congestion collapse during traffic overloads. Already [draft-ietf-soc-overload-control-12] proposes a loss-based solution to remedy known vulnerabilities of the [RFC3261] SIP 503 (service unavailable) overload control mechanism. This document proposes a rate-based control solution to complement the loss-based control defined in [draft-ietf-soc-overload-control-12]. | ||
| Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat | Peter Saint-Andre, Eddy Gavita, Nazin Hossain, Salvatore Loreto | 2013-04-04 |
| This document defines a bidirectional protocol mapping for the exchange of instant messages in the context of a one-to-one chat session between a user of the Session Initiation Protocol (SIP) and a user of the Extensible Messaging and Presence Protocol (XMPP). Specifically for SIP text chat, this document specifies a mapping to the Message Session Relay Protocol (MSRP). | ||
| Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant Messaging | Peter Saint-Andre, Avshalom Houri, Joe Hildebrand | 2013-04-04 |
| This document defines a bidirectional protocol mapping for the exchange of single instant messages between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP). | ||
| Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Addresses and Error Conditions | Peter Saint-Andre, Avshalom Houri, Joe Hildebrand | 2013-04-02 |
| As a foundation for the definition of bidirectional protocol mappings between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP), this document specifies the architectural assumptions underlying such mappings as well as the mapping of addresses and error conditions. | ||
| Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence | Peter Saint-Andre, Avshalom Houri, Joe Hildebrand | 2013-04-02 |
| This document defines a bi-directional protocol mapping for the exchange of presence information between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP). | ||
| Session Initiation Protocol (SIP) Recording Call Flows | Ram R, Parthasarathi Ravindran, Paul Kyzivat | 2013-03-25 |
| Session recording is a critical requirement in many communications environments such as call centers and financial trading. In some of these environments, all calls must be recorded for regulatory, compliance, and consumer protection reasons. Recording of a session is typically performed by sending a copy of a media stream to a recording device. This document lists call flows that has snapshot of metadata sent from SRC to SRS, the metadata format for which is described in [I-D.ietf-siprec-metadata] . This is purely an informational document that is written to support the model defined in the metadata draft. | ||
| A Session Initiation Protocol (SIP) Event Package for Communication Diversion Information in support of the Communication Diversion (CDIV) Notification (CDIVN) CDIV service | John-Luc Bakker, Ranjit Avasarala | 2013-03-24 |
| 3GPP and TISPAN are defining the protocol specification for the Communication Diversion (CDIV) service using IP Multimedia (IM) Core Network (CN) subsystem (IMS) supplementary service. As part of CDIV, a SIP based event package is used for notifying users about diversions (re-directions or forwarding) of requests for communication sessions targetting the user. This document defines the SIP event package to support subscription and notification of diversions. The proposed event package is applicable to the CDIV supplementary service in IMS and may not be applicable to the general internet. | ||
| Session Initiation Protocol (SIP) History-Info Header Call Flow Examples | Mary Barnes, Francois Audet, Shida Schubert, Hans van Elburg, Christer Holmberg | 2013-03-19 |
| This document describes use cases and documents call flows which require the History-Info header field to capture the Request-URIs as a Session Initiation Protocol (SIP) Request is retargeted. The use cases are described along with the corresponding call flow diagrams and messaging details. | ||
| Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP) | Keith Drage, Christer Holmberg, Roland Jesske | 2013-03-15 |
| This document describes a set of private Session Initiation Protocol (SIP) header fields (P-headers) used by the 3rd-Generation Partnership Project (3GPP), along with their applicability, which is limited to particular environments. The P-header fields are for a variety of purposes within the networks that the partners use, including charging and information about the networks a call traverses. | ||
| P-Charge-Info - A Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) | Dan York, Tolga Asveren | 2013-03-15 |
| This text documents \'P-Charge-Info\', an existing private Session Initiation Protocol (SIP) header (P-header) used to convey billing information about the party to be charged. This P-Header is currently in production usage by a number of equipment vendors and carriers and this document is submitted to request the registration of this header with IANA. This P-Header may also be used in some situations to carry the ISUP Charge Number parameter for PSTN interconnection. NOTE: This document has been in development since 2008 under the name draft-york-sipping-p-charge-info. This -01 document is identical to draft-york-sipping-p-charge-info-15 except for edits to the text to indicate this is now for the DISPATCH working group as the SIPPING working group no longer exists. | ||
| A Session Initiation Protocol (SIP) Load Control Event Package | Charles Shen, Henning Schulzrinne, Arata Koike | 2013-03-14 |
| We define a load control event package for the Session Initiation Protocol (SIP). It allows SIP entities to distribute load filtering policies to other SIP entities in the network. The load filtering policies contain rules to throttle calls based on their source or destination domain, telephone number prefix or for a specific user. The mechanism helps to prevent signaling overload and complements feedback-based SIP overload control efforts. | ||
| The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP) | Inaki Castillo, Jose Millan, Victor Pascual | 2013-03-11 |
| The WebSocket protocol enables two-way realtime communication between clients and servers in web-based applications. This document specifies a WebSocket sub-protocol as a reliable transport mechanism between SIP (Session Initiation Protocol) entities to enable usage of SIP in web-oriented deployments. This document normatively updates RFC 3261. | ||
| Interoperability between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) | Chris Christou, Michael Lundberg, Christopher Ross, Peter Saint-Andre | 2013-03-10 |
| This document is intended to serve as a reference point for developers and operators implementing the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) within their networks. This document does not define any new protocols but does define the different reference models for deployment of combined use of SIP and XMPP ("CUSAX") clients and SIP- XMPP interworking to ensure consistency across the community. | ||
| Session Initiation Protocol (SIP) Recording Call Flows | Ram R, Parthasarathi Ravindran, Paul Kyzivat | 2013-02-25 |
| Session recording is a critical requirement in many communications environments such as call centers and financial trading. In some of these environments, all calls must be recorded for regulatory, compliance, and consumer protection reasons. Recording of a session is typically performed by sending a copy of a media stream to a recording device. This document lists call flows that has snapshot of metadata sent from SRC to SRS, the metadata format for which is described in [I-D.ietf-siprec-metadata] . This is purely an informational document that is written to support the model defined in the metadata draft. | ||
| Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs) | Hadriel Kaplan, Victor Pascual | 2013-02-25 |
| SIP Back-to-Back User Agents (B2BUAs) can cause unending SIP request routing loops because, as User Agent Clients, they can generate SIP requests with new Max-Forwards values. This document discusses the difficulties associated with loop detection for B2BUAs, and requirements for them to prevent infinite loops. | ||
| Using Interactive Connectivity Establishment (ICE) with Session Description Protocol (SDP) offer/answer and Session Initiation Protocol (SIP) | Marc Petit-Huguenin, Ari Keränen | 2013-02-25 |
| This document describes how Interactive Connectivity Establishment (ICE) is used with Session Description Protocol (SDP) offer/answer and Session Initiation Protocol (SIP). | ||
| A SIP Usage for RELOAD | Cullen Jennings, Bruce Lowekamp, Eric Rescorla, Salman Baset, Henning Schulzrinne, Thomas Schmidt | 2013-02-25 |
| This document defines a SIP Usage for REsource LOcation And Discovery (RELOAD). The SIP Usage provides the functionality of a SIP proxy or registrar in a fully-distributed system and includes a lookup service for Address of Records (AORs) stored in the overlay. It also defines Globally Routable User Agent Uris (GRUUs) that allow the registrations to map an AOR to a specific node reachable through the overlay. After such initial contact of a peer, the AppAttach method is used to establish a direct connection between nodes through which SIP messages are exchanged. | ||
| A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents | Hadriel Kaplan | 2013-02-25 |
| In many SIP deployments, SIP entities exist in the SIP signaling path between the originating UAC and final terminating UAS, which go beyond the definition of a Proxy, performing functions not defined in standards-track RFCs. The only term for such devices provided in [RFC3261] is for a Back-to-Back User Agent (B2BUA), which is defined as the logical concatenation of a User Agent Server (UAS) and User Agent Client (UAC). There are numerous types of SIP Back-to-Back User Agents (B2BUAs), performing different roles in different ways. For Example IP-PBXs, SBCs and Application Servers. This document identifies several common B2BUA roles, in order to provide taxonomy other documents can use and reference. | ||
| IANA Registering a SIP Resource Priority Header Field Namespace for Local Emergency Communications | James Polk | 2013-02-23 |
| This document creates the new Session Initiation Protocol (SIP) Resource Priority header field namespace \'esnet\' for local emergency session establishment to a public safety answering point (PSAP), between PSAPs, and between a PSAP and first responders and their organizations, and places this namespace in the IANA registry. | ||
| << Start < Prev 1 2 Next > End >> | ||
| Display # Results 1 - 25 of 41 | ||