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 |
| SIP E.164 Problem Statement | John Elwell | 2008-02-15 |
| SIP has long supported the use of both email-style addresses (user@host) and telephone-style addresses (number@host) in the "From:" address. A significant number of SIP deployments use the latter style with E.164 numbers. This document describes the problems that occur when such E.164 numbers are used in SIP. | ||
| Spam feedback for SIP | Saverio Niccolini, Kai Fischer, Dan Wing, Martin Stiemerling, Hannes Tschofenig | 2008-02-15 |
| This document gives on overview of possible mechanisms for SIP UAs to feedback spam information to the system (e.g. other SIP entities like upstream SIP proxies) thus they can use this information for handling subsequent calls (e.g. blacklist the caller, input this info to reputation systems, compute spam-specific caller statistics, etc.). | ||
| NICE: Non Session Initiation Protocol (SIP) usage of Interactive Connectivity Establishment (ICE) | Jonathan Rosenberg | 2008-02-15 |
| Interative Connectivity Establishment (ICE) has been specified as a NAT traversal mechanism for protocols based on the offer/answer exchange model. In practice, only the Session Initiation Protocol (SIP) has been based on the offer/answer model. This document defines a SIP independent subset of ICE, called NICE, which can be used with any protocol wishing to establish a direct host-to-host relationship through NAT. Protocol specifications need only reference this document, and include the object defined here in their messages, in order to achieve NAT traversal. | ||
| What is a Session Initiation Protocol (SIP) Trunk Anyway? | Jonathan Rosenberg | 2008-02-15 |
| The term "Session Initiation Protocol (SIP) Trunk" has become almost commonplace amongst vendors and SIP providers. Even though the notion of a \'trunk\' has a well defined meaning in circuit switched systems, it has never been defined for SIP. This document provides a formal definition for a SIP trunk, discusses its scope and applications, and establishes best practices for identification and security of SIP trunks. | ||
| Change Process for the Session Initiation Protocol (SIP) | Jon Peterson, Cullen Jennings | 2008-02-15 |
| This memo documents a process intended to apply architectural discipline to the future development of the Session Initiation Protocol (SIP). There have been concerns with regards to new SIP proposals. Specifically, that the addition of new SIP features can be damaging towards security and/or greatly increase the complexity of the protocol. The RAI Area directors, along with the SIP and Session Initiation Proposal Investigation (SIPPING) working group chairs, have provided suggestions for SIP modifications and extensions. | ||
| Call Completion for Session Initiation Protocol(SIP) | Dale Worley, Martin Huelsemann, Denis Alexeitsev | 2008-02-15 |
| 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 | ||
| The Session Initiation Protocol (SIP) Pending Additions Event Package | Gonzalo Camarillo | 2008-02-15 |
| This document defines the SIP Pending Additions event package. This event package is used by SIP relays to inform user agents about the consent-related status of the entries to be added to a resource list. | ||
| A Binary Floor Control Protocol (BFCP) Control Package for the Session Initiation Protocol (SIP) | Lorenzo Miniero, Alessandro Amirante, Tobia Castaldi, Simon Romano | 2008-02-12 |
| This document defines a Session Initiation Protocol (SIP) Control Package for BFCP-based conference moderation. The control of Media Servers and their related resources in decomposed network architectures plays an important role in various Next Generation Networks. This Control Package aims at adding BFCP functionality to conferences using the SIP Control Framework. | ||
| SPEERMINT Terminology | Daryl Malas, Dave Meyer | 2008-02-12 |
| This document defines the terminology that is to be used in describing Session PEERing for Multimedia INTerconnect (SPEERMINT). | ||
| Scaling Requirements for Presence in SIP/SIMPLE | Avshalom Houri, Sriram Parameswar, Edwin Aoki, Vishal Singh, Henning Schulzrinne | 2008-02-11 |
| 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 E.164 Return Routability Check (RRC) | Dan Wing | 2008-02-08 |
| SIP lacks a mechanism to determine which domain can claim ownership of a certain telephone number. Due to this, it is impossible to establish meaningful identity or to authenticate endpoints that use telephone number URIs and domain names in their From address. This document proposes a solution to this problem using a return routability test. | ||
| Indicating Support for Basic Media Server Capabilities in the Session Initiation Protocol (SIP) | Chris Boulton | 2008-02-07 |
| This specification defines a profile set of media feature tags that can be used with the Session Initiation Protocol (SIP). The media feature tags allow a Media Server to communicate a basic set of media server capabilities that are supported to its Application Server. | ||
| P2PSIP Security Analysis and Evaluation | Song Yongchao, Ben Zhao, XingFeng Jiang, Jiang Haifeng | 2008-02-04 |
| This document provides an analysis and evaluation of security with P2PSIP overlay network. The draft compares security difference between C/S and P2P, then partitions the P2PSIP architecture into layers, and analyze the security issues in each layer and the security relationship among the layers. Security issues with different kind of application scenarios are distinct. This draft classifies the application scenarios into two main types, and the security threats with these two types of scenarios are analyzed in detail. | ||
| A Framework for Consent-based Communications in the Session Initiation Protocol (SIP) | Jonathan Rosenberg, Gonzalo Camarillo, Dean Willis | 2008-01-31 |
| The Session Initiation Protocol (SIP) supports communications for several services, including, real-time audio, video, text, instant messaging, and presence. In its current form, it allows session invitations, instant messages, and other requests to be delivered from one party to another without requiring explicit consent of the recipient. Without such consent, it is possible for SIP to be used for malicious purposes, including amplification, and DoS (Denial of Service) attacks. This document identifies a framework for consent- based communications in SIP. | ||
| Analysis of Rendezvous Mechanism for Home Access Using SIP | Makoto Saito, Dan Wing | 2008-01-29 |
| Home servers are becoming more common and people expect to still access them even when they are outside their home. However, there are several requirements to realize remote access to the home such as name resolution, NAT/Firewall traversal, and authentication/ authorization. This document describes what technologies can be used to solve these issues and analyzes the utility of SIP as a rendezvous mechanism for this use case. | ||
| Applying Loose Routing to Session Initiation Protocol (SIP) User Agents (UA) | Jonathan Rosenberg | 2008-01-25 |
| A key part of the behavior of the Session Initiation Protocol (SIP) is that SIP proxies rewrite the Request-URI as a request moves throughout the network. Over the years, experience has shown this to be problematic. It makes it difficult to use Request URI for service invocation, complicates emergency services, makes it more complex to support aliases, and so on. Architecturally, it confounds the concepts of address and route. This document proposes to change this through a new mechanism called UA loose routing. | ||
| Message Body Handling in the Session Initiation Protocol (SIP) | Gonzalo Camarillo | 2008-01-23 |
| This document specifies how message bodies are handled in SIP. Additionally, it specifies SIP user agent support for MIME (Multipurpose Internet Mail Extensions) in message bodies. | ||
| Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information | Mikko Lonnfors, Jose Costa-Requena, Eva Leppanen, Hisham Khartabil | 2008-01-21 |
| By default, presence delivered using the Presence Event Package for the Session Initiation Protocol (SIP) is represented in the Presence Information Data Format (PIDF). A PIDF document contains a set of elements, each representing a different aspect of the presence being reported. When any subset of the elements change, even just a single element, a new document containing the full set of elements is delivered. This memo defines an extension allowing delivery of only the presence data that has actually changed. | ||
| SIP Interface to VoiceXML Media Services | Dave Burke, Mark Scott | 2008-01-16 |
| This document describes a SIP interface to VoiceXML media services. Commonly, application servers controlling media servers use this protocol for pure VoiceXML processing capabilities. This protocol is an adjunct to the full MEDIACTRL protocol and packages mechanism.Comments Please send comments on this draft to the MEDIACTRL mail list, mediactrl@ietf.org. | ||
| Target URI delivery in the Session Initiation Protocol (SIP) | Christer Holmberg, Hans Erik van Elburg | 2008-01-16 |
| This document specifies an alternative mechanism how to deliver the current target URI to the UAS, e.g. in order to implement the use- cases specified in draft-rosenberg-sip-ua-loose-route-01 [8]. | ||
| SIP Usage Scenarios Similar to SPIT | Dan York | 2008-01-16 |
| This document outlines scenarios in which legitimate SIP traffic may appear similar to traffic associated with voice spam, also known as "SPIT" or "Spam for Internet Telephony. This document is created to provide input into the current discussions about how best to address the issue of SPIT. | ||
| Transporting User to User Call Control Information in SIP for ISDN Interworking | Alan Johnston, Joanne McMillen | 2008-01-15 |
| Several approaches to transporting the ITU-T Q.931 User to User Information Element (UU IE) data in SIP have been implemented. As networks move to SIP it is important that applications requiring this data can continue to function in SIP networks as well as the ability to interwork the information to/from ISDN for end-to-end transparency. This document discusses the approaches and recommends a new header field User-to-User be standardized. An example application of an Automatic Call Distributor (ACD) in a contact center is given. | ||
| A Conference List Information Event Package for the Session Initiation Protocol (SIP) | Oded Koren | 2008-01-07 |
| This document describes the usage of the Session Initiation Protocol (SIP) for subscriptions and notifications related to conference lists. A new conference list event package is specified. This event package allows a user to subscribe to a single event (the conference-list) and receive notifications that contain the list of conferences to which the user belongs and the status of each conference. The notifications sent from the conference server can contain either the entire list of the user\'s conferences or a partial list with the updates since the previous notification. | ||
| Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Core | Peter Saint-Andre, Avshalom Houri, Joe Hildebrand | 2008-01-04 |
| As a foundation for the definition of application-specific, bi- directional 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 | 2008-01-04 |
| 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). | ||
| << Start < Prev 1 2 3 4 5 6 Next > End >> | ||
| Display # Results 76 - 100 of 145 | ||
SIP SPOKESPERSON
Eric is Deputy Chief Technology Officer and General Manager of the Communications Division at BEA Systems, primarily focusing on real-time multimedia communications and the telecommunications industry vertical.
