Login Form
RECENT IETF DRAFTS
SIP internet drafts statistics
- 145 SIP related internet drafts (IETF).
- 12 new and updated drafts posted in the last 14 days.
| Title | Author | Date |
| Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant Messaging | Peter Saint-Andre, Avshalom Houri, Joe Hildebrand | 2008-01-04 |
| This document defines a bi-directional 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): Text Chat | Peter Saint-Andre, Eddy Gavita, Nazin Hossain, Salvatore Loreto | 2008-01-04 |
| This document defines a bi-directional 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): Media Sessions | Peter Saint-Andre | 2008-01-04 |
| This document defines a bi-directional protocol mapping for use by gateways that enable the exchange of media signalling messages between systems that implement the Jingle extensions to the Extensible Messaging and Presence Protocol (XMPP) and those that implement the Session Initiation Protocol (SIP). | ||
| Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP) | Miguel Garcia-Martin, Gonzalo Camarillo | 2007-12-21 |
| This document specifies a mechanism that allows a SIP User Agent Client (UAC) to send a SIP MESSAGE request to a set of destinations, by using a SIP URI-list (Uniform Resource Identifier list) service. The UAC sends a SIP MESSAGE request that includes the payload along with the URI list to the MESSAGE URI-list service, which sends a MESSAGE request including the payload to each of the URIs included in the list. | ||
| Duplicate a SIP session | Pierre Imai, Bernd Lamparter, Paulo Loureiro | 2007-12-19 |
| Session duplication copies media of an ongoing communication session from one device to another. After duplication the two devices have independent control over this media. This is in particular useful for one-way media like broadcast IPTV or Video-on-Demand. This document describes the general methods and specifies the signaling and media flows for providing this service using the Session Initiation Protocol (SIP). | ||
| Referring to Multiple Resources in the Session Initiation Protocol (SIP) | Gonzalo Camarillo, Aki Niemi, Markus Isomaki, Miguel Garcia-Martin, Hisham Khartabil | 2007-12-18 |
| This document defines extensions to the SIP REFER method so that this method can be used to refer to multiple resources in a single request. These extensions include the use of pointers to Uniform Resource Identifier (URI)-lists in the Refer-To header field and the "multiple-refer" SIP option-tag. | ||
| Different types of nodes in P2PSIP | Yao Wang | 2007-12-14 |
| This document is an attempt to classify different types of node in peer-to-peer Session Initiation Protocol (P2PSIP). Four possible types of nodes in P2PSIP are discussed based on two characters: whether it offers overlay-routing services and whether it offers storage functions. The behaviors of each type of nodes and their possible necessities are analyzed. This document is dedicated to be a reference for clarifying some controversial terms in P2PSIP working group, such as "client", "low-function peer", etc. | ||
| An overload control package for the Session Initiation Protocol (SIP). | Youssef Chadli, Xavier Marjou | 2007-12-04 |
| This document specifies an event package for the notification of overload control using the Session Initiation Protocol (SIP) events framework. The overload control package allows an upstream server to retrieve overload control information from an downstream server and to be notified when this information changes. This information is used by the upstream server to adapt its flow toward the downstream server and thus to avoid overloading it. | ||
| Peer-to-Peer SIP Implementation Report | Martin Stiemerling, Marcus Brunner | 2007-11-19 |
| This memo is an implementation report about the peer-to-peer SIP system developed in the European IST Ambient Networks research project. This system replaces the traditional SIP proxy-registrar function with a distributed lookup mechanism, adds overlay functionality to the SIP signalling and to RTP traffic, takes care about media/packet relay lookup and insertion into the SIP/RTP paths, plus automatic adaptation of the voice transmission according to changing network conditions. Standard, unmodified SIP user agents are used for communication. The presented system is work in progress and this memo is an attempt to gather IETF community feedback about the described approach. | ||
| IANA Registering a SIP Resource Priority Header Namespace for Local Emergency Communications | James Polk | 2007-11-19 |
| This document creates and IANA registers the new Session Initiation Protocol (SIP) Resource Priority header (RPH) namespace "sos" for local emergency usage to a public safety answering point (PSAP), between PSAPs, and between a PSAP and first responders and their organizations. | ||
| A Process for Handling Essential Corrections to the Session Initiation Protocol (SIP) | Keith Drage | 2007-11-19 |
| The Session Initial Protocol (SIP) defined in RFC 3261 and a large number of extensions forms a considerable body of work, which through sheer size has a number of errors that require correction. This document explains the process for managing essential corrections to SIP. | ||
| Security requirements in P2PSIP | Marcin Matuszewski, Jan-Erik Ekberg, Pekka Laitinen | 2007-11-19 |
| This document presents main security requirements for the Peer-to- Peer SIP (P2PSIP) architecture and its components. This document also analyses security threats in P2PSIP. Typical security ontology is used as classification for the threats. | ||
| Utilizing HIP (Host Identity Protocol) for P2PSIP (Peer-to-peer Session Initiation Protocol) | Jani Hautakorpi, Gonzalo Camarillo, Joakim Koskela | 2007-11-19 |
| This document specifies how Host Identity Protocol (HIP) can be utilized in Peer-to-Peer Session Initiation Protocol (P2PSIP) networks. Peers in a P2PSIP network need to have long-lived connections to other peers in the network, and HIP can be utilized to setup and maintain those connections. HIP is a good choice for connection maintenance, because it provides functionalities like Network Address Translation (NAT) traversal, mobility, multi-homing, and enhanced security properties. | ||
| Session Initiation Protocol (SIP) Session Mobility | Ron Shacham, Henning Schulzrinne, Srisakul Thakolsri, Wolfgang Kellerer | 2007-11-18 |
| Session mobility is the transfer of media of an ongoing communication session from one device to another. This document describes the basic approaches and shows the signaling and media flow examples for providing this service using the Session Initiation Protocol (SIP). Service discovery is essential to locate targets for session transfer and is discussed using the Service Location Protocol (SLP) as an example. This document is intended as an informational document. | ||
| Terminology for Benchmarking Session Initiation Protocol (SIP) Networking Devices | Scott Poretsky, Vijay Gurbani, Carol Davids | 2007-11-18 |
| This document provides a terminology for benchmarking SIP performance in networking devices. Terms are included for test components, test setup parameters, and performance benchmark metrics for black-box benchmarking of SIP networking devices. The Performance Benchmark Metrics are obtained for the SIP Control Plane and Media Plane. The terms are intedned for use in a companion Methodology document for complete performance characterization of a device in a variety of network conditions making it possible to compare performance of different devices. It is critical to provide Test Setup Parameters and a Methodology document for SIP performance benchmarking because SIP allows a wide range of configuration and operational conditions that can influence performance benchmark measurements. It is necessary to have terminology and methodology standards to ensure that reported benchmarks have consistent definition and were obtained following the same procedures. Benchmarks can be applied to compare performance of a variety of SIP networking devices. | ||
| Methodology for Benchmarking SIP Networking Devices | Scott Poretsky, Vijay Gurbani, Carol Davids | 2007-11-18 |
| This document describes the methodology for benchmarking Session Initiation Protocol (SIP) performance as described in Terminology document [5]. The methodology and terminology are to be used for benchmarking signaling plane performance with varying signaling and media load. Both scale and establishment rate are measured by signaling plane performance. The SIP Devices to be benchmarked may be a single device under test (DUT) or a system under test (SUT). Benchmarks can be obtained and compared for different types of devices such as SIP Proxy Server, SBC, P-CSCF, and Server paired with a Firewall/NAT device. | ||
| Supporting Multiple Path Routing in the Session Initiation Protocol (SIP) | Dale Worley | 2007-11-18 |
| An increasing number of SIP architectures implement multiple path routing (MPR), which is the providing of more than one path for a call to reach a destination user agent (UA). To implement MPR well, the proxy which forks a request onto the redundant paths needs to be able to determine if a fork that failed reached the destination UA and was rejected by the UA (and so an alternate path should not be tried), or if the fork failed before reaching the UA (and so an alternate path should be attempted). This document is to begin a discussion of strategies for making this determination. | ||
| SIP URI Service Discovery using DNS-SD | Jae Woo Lee, Henning Schulzrinne, Wolfgang Kellerer, Zoran Despotovic | 2007-11-18 |
| This document describes how to use the DNS-based Service Discovery (DNS-SD), better known as Apple Bonjour, for advertising Session Initiation Protocol (SIP) URIs in local area networks. Using this mechanism, a SIP user agent (UA) can communicate with another UA even when no SIP registrar is available, as in a wireless ad-hoc network for example. | ||
| Session Initiation Protocol (SIP) INFO Method Use | Eric Burger | 2007-11-18 |
| The purpose of the INFO request for the Session Initiation Protocol (SIP), as described by RFC 2976, is to provide mid-session SIP User Agent (UA)-to-SIP UA application data transport. In the years since the introduction of the INFO request, experience with the use of the INFO request indicates a number of problems. This document explains why there are INFO-based, proprietary protocols in the wild; the flaws of using INFO; and explains why it is not possible to create a framework to rescue INFO for general purpose use. Since SIP has evolved considerably since the introduction of INFO, this document highlights some of the new, robust mechanisms for achieving the work that previously led people to use INFO. As these mechanisms are now available, this document formally deprecates the use of INFO for new usages beyond the existing standardized ones, namely RFC 3372 (SIP-T) and RFC 4497 (QSIG). | ||
| Scaling Requirements for Presence in SIP/SIMPLE | Avshalom Houri, Sriram Parameswar, Edwin Aoki, Vishal Singh, Henning Schulzrinne | 2007-11-18 |
| The document provides a set of requirements for enabling interdomain scaling in presence for SIP/SIMPLE. The requirements are based on a separate scaling analysis document. | ||
| SIP SAML Profile and Binding | Hannes Tschofenig, Jeff Hodges, Jon Peterson, James Polk, Douglas Sicker | 2007-11-18 |
| This document specifies a Session Initiation Protocol (SIP) profile of Security Assertion Markup Language (SAML) as well as a SAML SIP binding. The defined SIP SAML Profile composes with the mechanisms defined in the SIP Identity specification and satisfy requirements presented in "Trait-based Authorization Requirements for the Session Initiation Protocol (SIP)". | ||
| Updates to Asserted Identity in the Session Initiation Protocol (SIP) | John Elwell | 2007-11-16 |
| SIP has a mechanism for conveying the asserted identity of the originator of a request by means of the P-Asserted-Identity header field. This header field is specified for use in requests using a number of SIP methods, in particular the INVITE method. However, RFC 3325 does not specify the insertion of this header field by a trusted UAC, does not specify the use of this header field with the SIP UPDATE, MESSAGE or PUBLISH methods, and is unclear on the use of this header field in responses. This document extends RFC 3325 to cover these situations. This work is being discussed on the sipping@ietf.org mailing list. | ||
| A Session Initiation Protocol (SIP) Event Package and Data Format for Describing Files | Miguel Garcia-Martin, Marcin Matuszewski | 2007-11-16 |
| This document specifies the format and semantics associated to a \'file\' event package that allows SIP endpoints to publish the availability of files. A file can be, for example, images, video files, audio files, etc. The event package reuses the eXtended Mark-up Language (XML) \'file-metadata\' document to provide file descriptions. This event package also allows SIP endpoints to subscribe to changes in the availability of files, or perform searches for the availability and location of a given file. Support for partial notifications and publications is also accomplished by using XML patch operations. | ||
| Sharing Files with the Session Initiation Protocol (SIP) | Miguel Garcia-Martin, Marcin Matuszewski, Nicklas Beijar, Juuso Lehtinen | 2007-11-16 |
| This memo proposes a SIP framework used for advertising and searching for shared files within a given community. The memo defines the signaling that users to announce the availability of files stored in their User Agents (UA). It also provides the signaling for users to perform searches of available files and monitor changes in those files. Additionally, this memo describes the signaling used to access a file. These methods can be used in (but are not limited to) SIP peer-to-peer systems based on centralized, semi-centralized or fully distributed architectures. | ||
| XPP Extensions for Implementing a Passive P2PSIP Overlay Network based on the CAN Distributed Hash Table | Enrico Marocco, Emil Ivov | 2007-11-16 |
| This document defines a set of extensions for the Extensible Peer Protocol (XPP) required for creating a P2PSIP overlay network based on the CAN distributed hash table algorithm. It specifies how peers and clients must behave in order to maintain the overlay and use it for the establishment of multimedia communication sessions. To limit the overhead due to maintenance operations and to allow the adoption of security policies for preventing malicious nodes to damage the overlay, joins are always initiated and controlled by existing peers (hence the passive in PCAN). | ||
| << Start < Prev 1 2 3 4 5 6 Next > End >> | ||
| Display # Results 101 - 125 of 145 | ||
SIP SPOKESPERSON
Bernard Hammer is responsible at Siemens for technical and strategic standardization issues in the field of IP-based communications for enterprise networks.
