Login Form
RECENT IETF DRAFTS
SIP internet drafts statistics
- 144 SIP related internet drafts (IETF).
- 13 new and updated drafts posted in the last 14 days.
| Title | Author | Date |
| Requirements from SIP (Session Initiation Protocol) Session Border Control Deployments | Jani Hautakorpi, Gonzalo Camarillo, Bob Penfield, Alan Hawrylyshen, Medhavi Bhatia | 2008-03-25 |
| This document describes functions implemented in Session Initiation Protocol (SIP) intermediaries known as Session Border Controllers (SBCs). The goal of this document is to describe the commonly provided functions of SBCs. A special focus is given to those practices that are viewed to be in conflict with SIP architectural principles. This document also explores the underlying requirements of network operators that have led to the use of these functions and practices in order to identify protocol requirements and determine whether those requirements are satisfied by existing specifications or additional standards work is required. | ||
| Managing Client Initiated Connections in the Session Initiation Protocol (SIP) | Cullen Jennings, Rohan Mahy | 2008-03-21 |
| The Session Initiation Protocol (SIP) allows proxy servers to initiate TCP connections and send asynchronous UDP datagrams to User Agents in order to deliver requests. However, many practical considerations, such as the existence of firewalls and Network Address Translators (NATs), prevent servers from connecting to User Agents in this way. This specification defines behaviors for User Agents, registrars and proxy servers that allow requests to be delivered on existing connections established by the User Agent. It also defines keep alive behaviors needed to keep NAT bindings open and specifies the usage of multiple connections from the User Agent to its Registrar. | ||
| Determining When to Discard or Retry a SIP Request During Overload | Timothy Moran | 2008-03-14 |
| SIP servers can become overload and unable to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document proposes an architecture for determining when a client should throttle the sending of SIP requests vs. retrying them. | ||
| IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespaces | James Polk | 2008-03-13 |
| This document creates additional Session Initiation Protocol (SIP) Resource-Priority namespaces to meet the requirements of the US Defense Information Systems Agency, and places these namespaces in the IANA registry. | ||
| An Extension to Session Initiation Protocol (SIP) Events for Pausing and Resuming Notifications | Mohammad Vakil, Sriram Parameswar | 2008-03-12 |
| The Session Initiation Protocol (SIP) events framework enables a subscriber to receive asynchronous notification of various events from other SIP user agents. It defines mechanisms to create, refresh, terminate subscriptions. This framework also defines mechanism to fetch (poll) an event state of a resource without creating persistent subscriptions. There is no mechanism to temporarily pause the notifications, while still maintaining a subscription on the server. This lack of functionality sometime results in a lot of superfluous notification traffic, and put unnecessary load on the server. This draft defines an extension to SIP events that allows the subscriber to pause, un-pause notifications, and be able to perform fetch (poll) subscriptions within an established (created) subscription dialog. | ||
| Call Completion for Session Initiation Protocol(SIP) | Dale Worley, Martin Huelsemann, Denis Alexeitsev | 2008-02-26 |
| This document analyzes the interoperability problems surrounding the call-completion feature that allows a callee to put a caller\'s request into a queue by which the caller can be notified to call back the callee at later time. This document analyzes how different solutions inter-operate and tries to make recommendation on how to best meet this requirement. | ||
| Session Initiation Protocol (SIP) Event Notification Extension for Notification Throttling | Aki Niemi, Krisztian Kiss | 2008-02-25 |
| This memo specifies a throttle mechanism for limiting the rate of Session Initiation Protocol (SIP) event notifications. This mechanism can be applied in subscriptions to all SIP event packages, but the mechanism is especially designed to be used in combination with a subscription to a Resource List Server (RLS). | ||
| Interaction between SIP and HIP | Hannes Tschofenig, Joerg Ott, Henning Schulzrinne, Tom Henderson, Gonzalo Camarillo | 2008-02-25 |
| This document investigates the interworking between the Session Initiation Protocol (SIP) and the Host Identity Protocol (HIP) and the benefits that may arise from their combined operation. The aspect of exchanging Host Identities (or Host Identity Tags) in SIP/SDP for later usage with the Host Identity Protocol Protocol (HIP) is described in more detail as an example of this interworking. | ||
| Lightweight SIP Toolkit for Peer-to-Peer and Basic Client-Server Systems | Henry Sinnreich, Alan Johnston, Eunsoo Shim, Kundan Singh | 2008-02-25 |
| This memo discusses the usage scenario of SIP where all the applications reside in the endpoints. This is an alternative to the current usage of SIP where the services reside in the network. The use of SIP where the applications reside in the endpoints is applicable to P2P SIP networks and also to client-server networks. Such an approach reduces the number of required SIP related standards (as by spring 2008) from roughly 100 to about 11. Successful IP communications must also include the relevant standards for NAT traversal, some of which are not directly related to SIP and also several standards for security. These standards are included in the simple usage scenario for SIP as well. | ||
| The Multiple Appearance Feature using the Session Initiation Protocol (SIP) | Alan Johnston, Mohsen Soroushnejad, Venkatesh Venkataramanan, Paul Pepper, Anil Kumar | 2008-02-25 |
| This document describes the requirements and implementation of a group telephony feature commonly known as Bridged Line Appearance (BLA) or Multiple Line Appearance (MLA), or Shared Call/Line Appearance (SCA). When implemented using the Session Initiation Protocol (SIP), it is referred to as Multiple Appearances (MA) since SIP does not have lines. This feature is commonly offered in the IP Centrex services and IP-PBX offerings and is likely to be implemented on SIP IP telephones and SIP feature servers used in a business environment. This document lists requirements and compares implementation options for this feature. Extensions to the SIP dialog event package are proposed. | ||
| Completely Automated Public Turing Test to Tell Computers and Humans Apart (CAPTCHA) based Robot Challenges for SIP | Hannes Tschofenig, Eva Leppanen, Saverio Niccolini, Mayutan Arumaithurai | 2008-02-25 |
| A common approach to deal with unwanted communication attempts is to rely on some form of authorization policies, typically whitelists. In order to populate the entries in such an access control list it is helpful to have a way to challenge the entity willing to engage in a conversation (unless they are already pre-authorized). One reason why this is desired is to deal with robots that are aggressively distributing messages. This document describes how "Completely Automated Public Turing Test to Tell Computers and Humans Apart" (CAPTCHA) tests, which require human interaction, are applied to SIP. | ||
| The SIP INFO Method and Info Package Framework | Hadriel Kaplan, Christer Holmberg | 2008-02-25 |
| This document defines the INFO method and a mechanism for defining, negotiating and exchanging Info Packages in it. INFO requests are used within SIP INVITE-created dialogs, for applications which need to exchange session-related information inside the INVITE-created dialog. This draft addresses issues and open items from RFC 2976, and replaces it. | ||
| SIP-based Bicasting for Seamless Handover between Heterogeneous Networks | Haruki Izumikawa, Ross Lillie | 2008-02-25 |
| A vertical session handoff occurs in heterogeneous networks when a session media is moved between access networks within the same device. During session handoff, bi-casting media streams to both access networks of the session\'s device may be desirable to insure a seamless session handoff. This document describes the general methods and specifies the signaling and media flows for providing this service using the Session Initiation Protocol (SIP) [1]. | ||
| An ID/Locator Architecture for P2PSIP | Eric Cooper, Alan Johnston, Philip Matthews | 2008-02-25 |
| This document describes an architecture where peers in an peer-to- peer overlay use special IP addresses to identify other peers. Two of the advantages of this approach are that (a) most existing applications can run in an overlay without needing any changes and (b) peer mobility and NAT traversal are handled in a way that is transparent to most applications. | ||
| P2PSIP Clients | Victor Pascual, Marchin Matuszewski, Eunsoo Shim, Hewen Zhang, Song Yongchao | 2008-02-25 |
| This document describes why and when some devices would better be a Client rather than a Peer. The purpose of this document is to facilitate the discussion and understanding about the Client node type. | ||
| SIP INFO Use Cases | Hadriel Kaplan | 2008-02-25 |
| This document lists several known and potential use cases for SIP INFO requests, as discussed on the SIP WG mailing list. The use cases were requested by the WG chairs at the SIP WG meeting in IETF 70, and are documented herein for the purpose of discussion only. | ||
| A Provisioning Protocol for ENUM-SIP Addressing Servers | Kenneth Cartwright, Stephen Dimig, Mark Teodoro, Jean-Francois Mule | 2008-02-25 |
| This document defines a provisioning protocol for ENUM-SIP addressing servers. This protocol has been recently published as part of CableLabs(r) PacketCable(tm) specifications. It allows SIP service providers to provision and manage session establishment data used by SIP network elements to route SIP sessions to the target destinations which may be served by the SIP service provider\'s own internal network or by a session peering partner. The data provisioned into an ENUM-SIP addressing server is queried by SIP entities using ENUM or SIP. | ||
| SIP End-to-End Performance Metrics | Daryl Malas | 2008-02-25 |
| This document defines a set of metrics and their usage to evaluate the performance of end-to-end Session Initiation Protocol (SIP) based services in both production and testing environments. The purpose of this document is to combine a set of common metrics, allowing interoperable performance measurements, easing the comparison of industry implementations. | ||
| Presence Interdomain Scaling Analysis for SIP/SIMPLE | Avshalom Houri, Edwin Aoki, Sriram Parameswar, Tim Rang, Vishal Singh, Henning Schulzrinne | 2008-02-25 |
| The document analyzes the traffic that is generated due to presence subscriptions between domains. It is shown that the amount of traffic can be extremely big. In addition to the very large traffic the document also analyzes the affects of a large presence system on the memory footprint and the CPU load. Current approved and in work optimizations to the SIP protocol are analyzed with the possible impact on the load. Separate documents contain the requirements for optimizations and suggestions for new optimizations. | ||
| An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification | Aki Niemi | 2008-02-25 |
| The Session Initiation Protocol (SIP) events framework enables receiving asynchronous notification of various events from other SIP user agents. This framework defines the procedures for creating, refreshing and terminating subscriptions, as well as fetching and periodic polling of resource state. These procedures have a serious deficiency in that they provide no tools to avoid replaying event notifications that have already been received by a user agent. This memo defines an extension to SIP events that allows the subscriber to condition the subscription request to whether the state has changed since the previous notification was received. When such a condition is true, either the body of a resulting event notification or the entire notification message is suppressed. | ||
| SPEERMINT Requirements for SIP-based VoIP Interconnection | Jean-Francois Mule | 2008-02-25 |
| A number of use cases have been described for session peering of voice, presence, instant messaging and other types of multimedia traffic. This memo captures some of the requirements identified by these use case scenarios. It is intended to become an informational document linking the use cases to potential protocol solutions. | ||
| Basic Level of Interoperability for Session Initiation Protocol (SIP) Services (BLISS) Problem Statement | Jonathan Rosenberg | 2008-02-24 |
| The Session Initiation Protocol (SIP) has been designed as a general purpose protocol for establishing and managing multimedia sessions. It provides many core functions and extensions in support of features such as transferring of calls, parking calls, and so on. However, interoperability of more advanced features between different vendors has been poor. This document describes the reason behind these interoperability problems, and presents a framework for addressing them. | ||
| Spam Score for SIP | Dan Wing, Saverio Niccolini, Martin Stiemerling, Hannes Tschofenig | 2008-02-24 |
| This document defines a mechanism for SIP proxies to communicate a spam score to downstream SIP proxies and to SIP user agents. This information can then be used as input to other decision making engines, for example, to provide alternate call routing or call handling. | ||
| Diagnose P2PSIP Overlay Network Failures | Song Yongchao, Hewen Zhang, XingFeng Jiang | 2008-02-24 |
| This document describes a simple and efficient mechanism that can be used to detect and localize failures in P2PSIP overlay network. This document mainly consists of two parts: information carried in a P2PSIP Peer "Echo request" message and "Echo response" message for the purpose of fault detection and localization, and mechanisms for processing those messages. | ||
| SIMPLE made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence using the Session Initiation Protocol (SIP) | Jonathan Rosenberg | 2008-02-24 |
| The IETF has produced many specifications related to Presence and Instant Messaging with the Session Initiation Protocol (SIP). Collectively, these specifications are known as SIMPLE - SIP for Instant Messaging and Presence Leveraging Extensions. This document serves as a guide to the SIMPLE suite of specifications. It breaks them up into categories and explains what each is for and how they relate to each other. | ||
| << Start < Prev 1 2 3 4 5 6 Next > End >> | ||
| Display # Results 26 - 50 of 144 | ||
SIP SPOKESPERSON
Anwar Siddiqui is currently a Technical Manager of the Avaya Chief Technology Office (CTO) in Lincroft, New Jersey.
