Login Form
RECENT IETF DRAFTS
SIP internet drafts statistics
- 144 SIP related internet drafts (IETF).
- 29 new and updated drafts posted in the last 14 days.
| Title | Author | Date |
| Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP) | Keith Drage | 2008-07-14 |
| This document describes a set of private Session Initiation Protocol (SIP) headers (P-headers) used by the 3rd-Generation Partnership Project (3GPP), along with their applicability, which is limited to particular environments. The P-headers are for a variety of purposes within the networks that the partners use, including charging and information about the networks a call traverses.1. Overall Applicability The SIP extensions specified in this document make certain assumptions regarding network topology, linkage between SIP and lower layers, and the availability of transitive trust. These assumptions are generally NOT APPLICABLE in the Internet as a whole. The mechanisms specified here were designed to satisfy the requirements specified in the 3GPP Release 5 requirements on SIP [RFC4083] for which either no general-purpose solution was planned, where insufficient operational experience was available to understand if a general solution is needed, or where a more general solution is not yet mature. For more details about the assumptions made about these extensions, consult the Applicability subsection for each extension.2. Conventions | ||
| IANA Registering a SIP Resource Priority Header Namespace for Local Emergency Communications | James Polk | 2008-07-14 |
| This document creates and IANA registers the new Session Initiation Protocol (SIP) Resource Priority header (RPH) namespace "esnet" for local emergency usage to a public safety answering point (PSAP), between PSAPs, and between a PSAP and first responders and their organizations. | ||
| Security requirements in Peer-to-Peer Session Initiation Protocol (P2PSIP) | Marcin Matuszewski, Haibin Song, XingFeng Jiang, Jan-Erik Ekberg, Pekka Laitinen | 2008-07-14 |
| This document outlines the security requirements for a Peer-to-Peer Session Initiation Protocol (P2PSIP) overlay network. It compares security difference between client/server (C/S) and P2P implementations of SIP, partitions the P2PSIP architecture into layers and analyzes the security issues in each layer and the security relationship among the layers. This draft also classifies the application scenarios into two main types and then analyzes in detail the security threats with these two types of scenarios. In the end, it summarizes the main security requirements for the P2PSIP architecture and its components. This draft is a merge of features from the P2PSIP security requirements draft and the P2PSIP security analysis and evaluation draft and is still a work in progress. | ||
| Internet Assigned Numbers Authority (IANA) Registration of Instant Messaging and Presence DNS SRV RRs for the Session Initiation Protocol (SIP) | Salvatore Loreto | 2008-07-14 |
| This document registers with IANA two new DNS SRV Protocol Labels for resolving Instant Messaging and Presence services with SIP. | ||
| Guidelines for Usage of Interactive Connectivity Establishment (ICE) by non Session Initiation Protocol (SIP) Protocols | Jonathan Rosenberg | 2008-07-14 |
| 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 used ICE. This document provides guidance on how other protocols can make use of ICE. | ||
| Litmus Tests for Usage of the Session Initiation Protocol (SIP) INFO Method | Jonathan Rosenberg | 2008-07-14 |
| The Session Initiation Protocol (SIP) Working Group is considering the standardization of a framework for conveying application data through the INFO method. However, the INFO method is just one of several techniques available in SIP for the transfer of application data. Others include through the SIP events framework and through a media session. This document provides guidelines and litmus tests for determining which is the right technique to use. | ||
| SIP Usage Scenarios Similar to SPIT | Dan York | 2008-07-14 |
| 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. | ||
| Provisioning Protocol Requirements for ENUM-SIP Addressing Servers | Tom Creighton, Jean-Francois Mule | 2008-07-14 |
| This document presents use cases and protocol requirements for provisioning ENUM-SIP addressing servers. The provisioned data is used by the addressing server to return session establishment data for SIP entities to route SIP requests to the target destinations. An ENUM-SIP addressing server acts as a Lookup Function in session peering to determine the target domain of a given SIP request. It may also act as a Location Routing Function to develop the location of the SIP signaling entity in the target domain. | ||
| A Provisioning Protocol for ENUM-SIP Addressing Servers | Kenneth Cartwright, Stephen Dimig, Mark Teodoro, Jean-Francois Mule | 2008-07-14 |
| This document defines a provisioning protocol for ENUM-SIP addressing servers. An ENUM-SIP addressing server is a host that acts as Lookup Function in session peering to determine the target domain of a given SIP request and it may also act as a Location Routing Function to develop the location of the SIP signaling entity in that target domain. This protocol 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. This version of the protocol integrates comments received on the IETF peppermint and drinks mailing lists before July 2008. This document is an Internet-Draft and the protocol it describes is subject to technical changes that may make this version incompatible with future versions defined in Internet-Drafts. It is expected that the authors will continue to update this protocol based on the drinks working group requirements on the session establishment data. | ||
| Connection Reuse in the Session Initiation Protocol (SIP) | Rohan Mahy, Vijay Gurbani, Brett Tate | 2008-07-14 |
| This document enables a pair of communicating proxies to reuse a congestion-controlled connection between themselves for sending requests in the forward and backwards direction. Because the connection is essentially aliased for requests going in the backwards direction, reuse is predicated upon both the communicating endpoints authenticating themselves using X.509 certificates through TLS. For this reason, we only consider connection reuse for TLS over TCP and TLS over SCTP. A single connection should not be reused for the TCP or SCTP transport between two peers, and this document provides insight into why this is the case. As a remedy, it suggests using two TCP connections (or two SCTP associations), each opened pro- actively towards the recipient by the sender. Finally, this document also provides guidelines on connection reuse and virtual SIP servers and the interaction of connection reuse and DNS SRV lookups in SIP. | ||
| SIP SAML Profile and Binding | Hannes Tschofenig, Jeff Hodges, Jon Peterson, James Polk, Douglas Sicker | 2008-07-14 |
| 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)". | ||
| An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification | Aki Niemi | 2008-07-14 |
| 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. | ||
| Using Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 Certificates | Scott Lawrence, Vijay Gurbani | 2008-07-14 |
| This memo documents an extended key usage (EKU) X.509 certificate extension for identifying the holder of a certificate as authoritative for a Session Initiation Protocol (SIP) service in the domain named by the DNS name in the certificate. | ||
| Domain Certificates in the Session Initiation Protocol (SIP) | Vijay Gurbani, Scott Lawrence, Bell Laboratories | 2008-07-14 |
| This document describes how to interpret certain information in a X.509 PKIX-compliant certificate used in a Session Initiation Protocol (SIP) over Transport Layer Security (TLS) connection. More specifically, it describes how to find the right identity for authentication in such certificates and how to use it for SIP domain authentication. | ||
| UA-Driven Privacy Mechanism for SIP | Mayumi Munakata, Shida Schubert, Takumi Ohba | 2008-07-14 |
| This document defines a best current practice for a user agent to generate an anonymous SIP message by utilizing mechanisms such as GRUU and TURN without the need for a privacy service defined in RFC 3323. | ||
| Identification of Communications Services in the Session Initiation Protocol (SIP) | Jonathan Rosenberg | 2008-07-14 |
| This document considers the problem of service identification in the Session Initiation Protocol (SIP). Service identification is the process of determining the user-level use case that is driving the signaling being utilized by the user agent. This document discusses the uses of service identification, and outlines several architectural principles behind the process. It identifies perils when service identification is not done properly - including fraud, interoperability failures and stifling of innovation. | ||
| SPEERMINT Requirements for SIP-based Session Peering | Jean-Francois Mule | 2008-07-14 |
| This memo captures protocol requirements to enable session peering of voice, presence, instant messaging and other types of multimedia traffic. It is based on the use cases that have been described in the speermint working group. This informational document is intended to link the session peering use cases to protocol solutions. | ||
| Session Initiation Protocol (SIP) Overload Control | Volker Hilt, Indra Widjaja, Henning Schulzrinne | 2008-07-13 |
| Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources 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 defines an overload control mechanism for SIP. | ||
| The Multiple Appearance Feature using the Session Initiation Protocol (SIP) | Alan Johnston, Mohsen Soroushnejad, Venkatesh Venkataramanan, Paul Pepper, Anil Kumar | 2008-07-13 |
| 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. | ||
| SIP URI Service Discovery using DNS-SD | Jae Woo Lee, Henning Schulzrinne, Wolfgang Kellerer, Zoran Despotovic | 2008-07-12 |
| 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) Event Package for the Common Alerting Protocol (CAP) | Brian Rosen, Henning Schulzrinne, Hannes Tschofenig | 2008-07-12 |
| The Common Alerting Protocol (CAP) is an XML document format for exchanging emergency alerts and public warnings. This document allows CAP documents to be distributed via the event notification mechanism available with the Session Initiation Protocol (SIP). | ||
| A Session Initiation Protocol (SIP) Event Package for Session-Specific Session Policies. | Volker Hilt, Gonzalo Camarillo | 2008-07-12 |
| This specification defines a Session Initiation Protocol (SIP) event package for session-specific policies. This event package enables user agents to subscribe to session policies for a SIP session and to receive notifications if these policies change. | ||
| The Session Initiation Protocol (SIP) P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem | Hans Erik van Elburg | 2008-07-11 |
| This document specifies the SIP P-Served-User P-header. This header field addresses an issue that was found in the 3rd-Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an S-CSCF (Serving Call Session Control Function) and an AS (Application Server) on the ISC (IMS Subsystem Service Control) interface. This header field conveys the identity of the served user and the session case that applies to this particular communication session and application invocation. | ||
| Providing guidance for Session Initiation Protocol (SIP) services | Arnaud Ligot, Thomas Froment | 2008-07-11 |
| Implementing Session Initiation Protocol (SIP) advanced features and services requires to use numerous specifications. Today, for each service in the scope of BLISS, one can already find references to many possible specifications which do not cover the same things. Some of them are primitive operations, requirements or call flow examples, some have a scope larger than the others, or can not be compared at the same level. Very often, architecture hypothesis are hidden behind the same service name, either assuming that an intermediary; like an application server, has an active role in the service, or, as opposed, assuming a pure end-to-end model where only endpoint implementations are involved. The goal of this document is not to present the best solutions or give recommendations; but to give an overview of every standard specification related to these services, centralizing and categorizing them as input to the working group. | ||
| An overload control package for the Session Initiation Protocol (SIP). | Youssef Chadli, Xavier Marjou | 2008-07-11 |
| 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 a 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. | ||
| << Start < Prev 1 2 3 4 5 6 Next > End >> | ||
| Display # Results 1 - 25 of 144 | ||
