Login Form

Lost Password?

No account yet? Register

RECENT IETF DRAFTS

SIP internet drafts statistics

  • 25 SIP related internet drafts (IETF).
  • 0 new and updated drafts posted in the last 14 days.

Read more ...

Title Author Date
DISPATCH-Style Working Groups and the SIP-Change Process Ben Campbell, Alissa Cooper, Barry Leiba 0000-00-00
RFC 5727 defined several processes for the former Real-time Applications and Infrastructure (RAI) area. These processes include the evolution of the Session Initiation Protocol (SIP) and related protocols, as well as the operation of the DISPATCH and SIPCORE working groups. This document updates RFC 5727 to allow flexibility for the area and working group structure, while preserving the SIP- change processes. It also generalizes the DISPATCH working group processes so that they can be easily adopted by other working groups.

End-to-End Session Identification in IP-Based Multimedia Communication Networks Paul Jones, Gonzalo Salgueiro, Chris Pearce, Paul Giralt 0000-00-00
This document describes an end-to-end Session Identifier for use in IP-based multimedia communication systems that enables endpoints, intermediary devices, and management systems to identify a session end-to-end, associate multiple endpoints with a given multipoint conference, track communication sessions when they are redirected, and associate one or more media flows with a given communication session. This document also describes a backwards compatibility mechanism for an existing session identifier implementation (RFC 7329) that is sufficiently different from the procedures defined in this document. This document obsoletes RFC 7329.

Requirements for Marking SIP Messages to be Logged Peter Dawes, Chidambaram Arunachalam 0000-00-00
SIP networks use signalling monitoring tools to debug customer reported problems and for regression testing if network or client software is upgraded. As networks grow and become interconnected, including connection via transit networks, it becomes impractical to predict the path that SIP signalling will take between clients, and therefore impractical to monitor SIP signalling end-to-end. This draft describes requirements for adding an indicator to the SIP protocol data unit (PDU, or a SIP message) that marks the PDU as a candidate for logging. Such marking will typically be applied as part of network testing controlled by the network operator and not used in regular client signalling. However, such marking can be carried end-to-end including the SIP terminals, even if a session originates and terminates in different networks.

Marking SIP Messages to be Logged Peter Dawes 0000-00-00
SIP networks use signalling monitoring tools to diagnose user reported problems and for regression testing if network or user agent software is upgraded. As networks grow and become interconnected, including connection via transit networks, it becomes impractical to predict the path that SIP signalling will take between user agents, and therefore impractical to monitor SIP signalling end-to-end. This document describes an indicator for the SIP protocol which can be used to mark signalling as of interest to logging. Such marking will typically be applied as part of network testing controlled by the network operator and not used in regular user agent signalling. However, such marking can be carried end-to-end including the SIP user agents, even if a session originates and terminates in different networks.

Using Interactive Connectivity Establishment (ICE) with Session Description Protocol (SDP) offer/answer and Session Initiation Protocol (SIP) Marc Petit-Huguenin, Ari Keranen, Suhas Nandakumar 0000-00-00
This document describes how Interactive Connectivity Establishment (ICE) is used with Session Description Protocol (SDP) offer/answer and Session Initiation Protocol (SIP).

Port Control Protocol (PCP) for SIP Deployments in Managed Networks Mohamed Boucadair, Parthasarathi Ravindran 0000-00-00
This document discusses how PCP (Port Control Protocol) can be used in SIP deployments in managed networks. This document applies for both IPv4 and IPv6.

The Session Initiation Protocol (SIP) OAuth Rifaat Shekh-Yusef, Victor Pascual, Christer Holmberg 0000-00-00
This document defines an authorization framework for SIP that is based on the OAuth 2.0 framework, and adds a simple identity layer on top of that, based on the OpenID Connect Core 1.0, to enable Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User.

Session Initiation Protocol (SIP) Cause URI parameter for Service Number translation Marianne Mohali, Mary Barnes 0000-00-00
[RFC4458] defines a "cause" URI parameter as having predefined values for Redirecting reasons as a mapping from ITU-T Q.732.2-5 Redirecting Reasons. The "cause" URI parameter is to be used in SIP or SIPs URI. In particular, it may appear in the Request-URI of a SIP request. This specification creates a new predefined value for the "cause" URI parameter for cases when the retargeting is due to specific service action leading to a called service access number translation. This document updates [RFC4458].

Remote Call Control and Call Pick-up in SIP Anton Tveretin 0000-00-00
This memo defines a mechanism by which a SIP user agent could inspect calls at another user agent, and control a call, including picking up for itself.

SIP Authentication using the EC-SRP5 Protocol Fuwen liu, Minpeng Qi, Min Zuo 0000-00-00
This document specifies the way that the elliptic curve secure remote protocol (EC-SRP) is applied to SIP authentication. SIP Client and server perform mutual authenticate by using the modern \'zero knowledge\' method without disclosing the password in the process. It has low computation complexity and low bandwidth consumption due to the use of elliptical curve cryptography. This makes it more suitable for resource-constrained environments,e.g. wireless network. The security of the scheme is based on the computational intractability of the elliptic curve discrete logarithm problem. It is resilient to various kinds of attacks, including off-line dictionary attacks.

Location Source Parameter for the SIP Geolocation Header Field James Winterbottom, Laura Liess, Bruno Chatras, Andrew Hutton 0000-00-00
There are some circumstances where a geolocation header field may contain more than one location value. Knowing the identity of the node adding the location value allows the recipient more freedom in selecting the value to look at first rather than relying solely on the order of the location values.

Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests/Responses Christer Holmberg, Nevenka Biondic, Gonzalo Salgueiro 0000-00-00
The 3rd-Generation Partnership Project 3GPP has identified cases where different SIP private header extensions referred to as P- header fields, defined in RFC 7315, need to be included in SIP requests and responses currently not allowed according to RFC 7315. This document updates RFC 7315, in order to allow inclusion of the affected P- header fields in such requests and responses. This document also makes updates for RFC 7315 in order to fix misalignments that occurred when RFC 3455 was updated and obsoleted by RFC 7315.

IANA Registration of New Session Initiation Protocol (SIP) Resource- Priority Namespace for Mission Critical Push To Talk service Christer Holmberg, J├Ârgen Axell 0000-00-00
This document creates an additional Session Initiation Protocol (SIP) Resource-Priority namespace to meet the requirements of the 3GPP defined Mission Critical Push To Talk, and places this namespace in the IANA registry.

Push Notifications in the Session Initiation Protocol (SIP) Viktor Ivanov 0000-00-00
The Session Initiation Protocol (SIP) allows User Agents to register for inbound requests. However, the existence of firewalls and Network Address Translators (NATs) prevent servers from reaching the User Agents unless the User Agents keep connections to the server alive. To keep such connections alive User Agents employ various methods, most of which require constant uptime resulting in high energy cost. This is especially a problem on mobile platforms that operate entirely on battery power. To resolve these issues many mobile manufacturers have provided a cost effective way of pushing messages to their devices. This specification defines behaviors for User Agents, registrars and proxy servers that allow a User Agent to provide a Push Notification Configuration to its Registrar.

P-Served-User Header Field Parameter for Originating CDIV session case in Session Initiation Protocol (SIP) Marianne Mohali 0000-00-00
This specification defines a new Session Initiation Protocol (SIP) P- Served-User header field parameter, "orig-cdiv-param", which defines the session case used by a proxy when handling an originating session after Call Diversion (CDIV) services has been invoked for the served user. The P-Served-User header field is defined in [RFC5502]. The P-Served-User header field conveys the identity of the served user and the session case that applies to this particular communication session and application invocation. This document updates [RFC5502] in order to add the originating after CDIV session case.

Best Practices for Securing RTP Media Signaled with SIP Jon Peterson, Eric Rescorla, Richard Barnes, Russ Housley 0000-00-00
Although the Session Initital Protocol (SIP) includes a suite of security services that has been expanded by numerous specifications over the years, there is no single place that explains how to use SIP to establish confidential media sessions. Additionally, existing mechanisms have some feature gaps that need to be identified and resolved in order for them to address the pervasive monitoring threat model. This specification describes practices for negotiating confidential media with SIP, including both comprehensive security solutions which bind the media to SIP-layer identities as well as opportunistic security solutions.

Concepts and Terminology for Peer to Peer SIP David Bryan, Philip Matthews, Eunsoo Shim, Dean Willis, Spencer Dawkins 0000-00-00
This document defines concepts and terminology for the use of the Session Initiation Protocol in a peer-to-peer environment where the traditional proxy-registrar and message routing functions are replaced by a distributed mechanism. These mechanisms may be implemented using a distributed hash table or other distributed data mechanism with similar external properties. This document includes a high-level view of the functional relationships between the network elements defined herein, a conceptual model of operations, and an outline of the related problems addressed by the P2PSIP working group and the RELOAD protocol and SIP usage document defined by the working group.

A SIP Usage for RELOAD Cullen Jennings, Bruce Lowekamp, Eric Rescorla, Salman Baset, Henning Schulzrinne, Thomas Schmidt 0000-00-00
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 RELOAD AppAttach method is used to establish a direct connection between nodes through which SIP messages are exchanged.

Considerations for Information Services and Operator Services Using SIP John Haluska, Richard Ahern, Marty Cruze, Chris Blackwell 0000-00-00
Information Services are services whereby information is provided in response to user requests, and may include involvement of a human or automated agent. A popular existing Information Service is Directory Assistance (DA). Moving ahead, Information Services providers envision exciting multimedia services that support simultaneous voice and data interactions with full operator backup at any time during the call. Information Services providers are planning to migrate to SIP based platforms, which will enable such advanced services, while continuing to support traditional DA services. Operator Services are traditional PSTN services which often involve providing human or automated assistance to a caller, and often require the specialized capabilities traditionally provided by an operator services switch. Market and/or regulatory factors in some jurisdictions dictate that some subset of Operator Services continue to be provided going forward. This document aims to identify how Operator and Information Services can be implemented using existing or currently proposed SIP mechanisms, to identity existing protocol gaps, and to provide a set of Best Current Practices to facilitate interoperability. For Operator Services, the intention is to describe how current operator services can continue to be provided to PSTN based subscribers via a SIP based operator services architecture. It also looks at how current operator services might be provided to SIP based subscribers via such an architecture, but does not consider the larger question of the need for or usefulness or suitability of each of these services for SIP based subscribers. This document addresses the needs of current Operator and Information Services providers; as such, the intended audience includes vendors of equipment and services to such providers.

Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network oej, Gonzalo Salgueiro, Vijay Gurbani, Dale Worley 0000-00-00
RFC 3263 defines how a Session Initiation Protocol (SIP) implementation, given a SIP Uniform Resource Identifier (URI), should locate the next-hop SIP server using Domain Name System (DNS) procedures. As SIP networks increasingly transition from IPv4-only to dual-stack, a quality user experience must be ensured for dual- stack SIP implementations. This document updates the DNS procedures described in RFC 3263 for dual-stack SIP implementations in preparation for forthcoming specifications for applying Happy Eyeballs principles to SIP.

Session Initiation Protocol (SIP) Recording Metadata Ram R, Parthasarathi Ravindran, Paul Kyzivat 0000-00-00
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 describes the metadata model as viewed by Session Recording Server(SRS) and the Recording metadata format.

Session Initiation Protocol (SIP) Recording Call Flows Ram R, Parthasarathi Ravindran, Paul Kyzivat 0000-00-00
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 a Session Recording Client to Session Recording Server. This is purely an informational document that is written to support the model defined in the metadata draft.

Authenticated Identity Management in the Session Initiation Protocol (SIP) Jon Peterson, Cullen Jennings, Eric Rescorla, Chris Wendt 0000-00-00
The baseline security mechanisms in the Session Initiation Protocol (SIP) are inadequate for cryptographically assuring the identity of the end users that originate SIP requests, especially in an interdomain context. This document defines a mechanism for securely identifying originators of SIP requests. It does so by defining a SIP header field for conveying a signature used for validating the identity, and for conveying a reference to the credentials of the signer.

Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence Peter Saint-Andre 0000-00-00
This document defines a bidirectional protocol mapping for the exchange of presence information between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP). This document obsoletes RFC 7248.

DTLS-SRTP Handling in Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs) Ram R, Tirumaleswar Reddy, Gonzalo Salgueiro, Victor Pascual, Parthasarathi Ravindran 0000-00-00
Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUA) exist on the signaling and media paths between the endpoints. This document describes the behavior of B2BUAs when Secure Real-time Transport (SRTP) security context is set up with the Datagram Transport Layer Security (DTLS) protocol.

<< Start < Prev 1 Next > End >>
Display # Results 1 - 25 of 25