|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
## SIPPINGwg
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
|
|
|
|
|
|
|
|
|
Last Update: May 9, 2008
-- Color Legend: RFC Editor Queue
/ Processed by IESG
/ ID Exists
/ Recently Expired
-- Each I-D name is a link to an I-D description, which points to a text version, a two-page and fit-in-window PDF version, as well as the IETF Tools' HTML version.
|
|
|
|
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
## SIPPINGwg
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
## SIPPINGwg
##
##
##
##
##
##
##
##
##
##
##
##
##
##
|
|
|
|
|
|
| The charter of the SIPPING working group -- updated on November 4, 2005 --
is reported below.
|
|
|
|
The Session Initiation Protocol Project INvestiGation (SIPPING)
working group is chartered to document the use of SIP for several
applications related to telephony and multimedia, and to develop
requirements for extensions to SIP needed for those applications.
Such requirements will be referred to the SIP working group for
development of any new SIP method, header, or option-tag as described
in Change Policy for SIP (RFC 3427).
Guiding principles for the performance of SIPPING's work will include:
|
|
| 1. |
Documenting the requirements of specific chartered tasks.
|
| 2. |
Documenting the usage of SIP to solve real problems that need
to be solved in a standardized way. Examples of important
topics identified are the session policy architecture, allowing
network entities to convey policy into an User Agent's
activity; requirements analysis for session border
controllers to determine how best such devices can
operate with SIP usage; and guidance on IPv4-IPv6
co-existence support by SIP and SIP-supported media.
|
| 3. |
Looking for commonalities among the chartered tasks and ongoing
SIP-related development, as commonalities may indicate for general,
reusable functionality in SIP.
|
| 4. |
Describing the requirements for any extension determined to pass
there hurdles, and handing the development task to the SIP WG.
|
| 5. |
Developing procedures and requirements for configuration and
delivery of SIP User Profiles.
|
|
Besides performing needed specification of several applications
of SIP, SIPPING can be seen as also working out use cases that
clarify the role of SIP in the Internet, and help to ensure that
Occam's razor is appropriately applied to SIP usage.
The security of all the deliverables will be of special importance.
The technology for security will be keyed from the SIP Security
specification within RFC 3261, and additional SIP specifications
as they apply.
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
## SIPPINGwg
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
|
|
|
|
|
|
|
|
|
|
| | |
sipping-app-
interaction-
framework-05
RFC Ed Queue (10/05)
Jul 18, 2005
(39 p.)
[pdf(2)]
[html]
|
J. Rosenberg |
| A Framework for Application Interaction in
SIP |
|
This document describes a framework for the interaction between users
and SIP-based applications. By
interacting with applications, users can guide the way in which they
operate. The focus of this framework is stimulus signaling, which
allows a user agent to interact with an application without knowledge
of the semantics of that application. Stimulus signaling can occur
to a user interface running locally with the client, or to a remote
user interface, through media streams. Stimulus signaling
encompasses a wide range of mechanisms, ranging from clicking on
hyperlinks, to pressing buttons, to traditional Dual Tone Multi
Frequency (DTMF) input. In all cases, stimulus signaling is
supported through the use of markup languages, which play a key role
in this framework.
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
sipping-gruu-
reg-event-09
RFC Ed Queue (08/07)
Jul 6, 2007
(16 p.)
[pdf(2)]
[html]
|
P. Kyzivat |
|
Registration Event Package Extension for
SIP Globally Routable User Agent URIs (GRUUs) |
RFC 3680
defines a SIP event package
for registration state. This package allows a watcher to learn about
information stored by a SIP registrar, including its registered
contact.
However, the registered contact is frequently unreachable and thus
not useful for watchers. The Globally Routable User Agent URI
(GRUU), defined in RFC YYYY, is a URI that is capable of reaching
a particular contact. However this URI is not included in the
document format defined in RFC 3680. This specification defines an
extension to the registration event package to include GRUUs assigned
by the registrar.
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
sipping-toip-09
RFC Ed Queue (05/08)
Apr 4, 2008
(27 p.)
[pdf(2)]
[html]
|
A. van Wijk
G. Gybels |
| Framework for real-time text over IP using SIP |
|
This document lists the essential requirements for real-time Text-over-IP
(ToIP) and defines a framework for implementation of all
required functions based on the Session Initiation Protocol (SIP) and
the Real-Time Transport Protocol (RTP). This includes interworking
between Text-over-IP and existing text telephony on the PSTN and other
networks.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
sipping-transc-
framework-05
RFC Ed Queue (02/07)
Nov 30, 2006
(12 p.)
[pdf(2)]
[html]
|
G. Camarillo |
|
Framework for Transcoding with
SIP |
|
This document defines a framework for transcoding with SIP. This
framework includes how to discover the need for transcoding services
in a session and how to invoke those transcoding services. Two
models for transcoding services invocation are discussed: the
conference bridge model and the third party call control model. Both
models meet the requirements for SIP regarding transcoding services
invocation to support deaf, hard of hearing, and speech-impaired
individuals.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
| | |
sipping-v6-
transition-07
RFC Ed Queue (08/07)
Aug 16, 2007
(16 p.)
[pdf(2)]
[html]
|
G. Camarillo
K. El Malki
V. Gurbani |
| IPv6 Transition in SIP |
|
This document describes how IPv4 Session Initiation Protocol (SIP)
user agents can communicate with IPv6 SIP user agents (and vice
versa) at the signaling layer as well as exchange media once the
session has been successfully set up. Both single- and dual-stack
(i.e., an IPv4-only and an IPv4/IPv6) user agents are considered.
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
shacham-sipping-
session-mobility-05
RFC Ed Queue (01/08)
Nov 18, 2007
(39 p.)
[pdf(2)]
[html]
|
R. Shacham
H. Schulzrinne
S. Thakolsri
W. Kellerer |
| SIP Session Mobility |
|
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.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
## SIPPINGwg
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
|
|
|
|
|
|
|
|
|
|
| | |
sipping-capacity-
attribute-06
Waiting for Writeup
Dec 18, 2007
(17 p.)
[pdf(2)]
[html]
|
M. Garcia-Martin
G. Camarillo |
|
XML Format Extension for Representing Copy Control Attributes in Resource Lists |
|
In certain types of multimedia communications, a Session Initiation
Protocol (SIP) request is distributed to a group of SIP User Agents
(UAs). The sender sends a single SIP request to a server which
further distributes the request to the group. This SIP request
contains a list of Uniform Resource Identifiers (URIs), which
identify the recipients of the SIP request. This URI-list is
expressed as a resource list XML document. This specification
defines an XML extension to the XML resource list format that allows
the sender of the request to qualify a recipient with a copy control
level similar to the copy control level of existing e-mail systems.
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
sipping-cc-
framework-10
Publication Requested
Apr 16, 2008
(43 p.)
[pdf(2)]
[html]
|
R. Mahy
R. Sparks
J. Rosenberg
D. Petrie
A. Johnston |
|
A Call Control and Multi-party usage framework for SIP |
|
This document defines a framework and requirements for call control
and multi-party usage of SIP. To enable discussion of multi-party
features and applications we define an abstract call model for
describing the media relationships required by many of these. The
model and actions described here are specifically chosen to be
independent of the SIP signaling and/or mixing approach chosen to
actually setup the media relationships. In addition to its dialog
manipulation aspect, this framework includes requirements for
communicating related information and events such as conference and
session state, and session history. This framework also describes
other goals that embody the spirit of SIP applications as used on the
Internet.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
| | |
sipping-cc-
transfer-09
AD Evaluation
Nov 28, 2007
(58 p.)
[pdf(2)]
[html]
|
R. Sparks
A. Johnston
D. Petrie |
| SIP Call Control - Transfer |
|
This document describes providing Call Transfer capabilities in the
Session Initiation Protocol (SIP). SIP extensions such as REFER and
Replaces are used to provide a number of transfer services including
blind transfer, consultative transfer, and attended transfer. This
work is part of the SIP multiparty call control framework.
|
|
|
| |
| Up List |
Intended Status: | Best Current Practice |
|
|
|
|
|
|
|
|
| | |
sipping-config-
framework-15
AD is watching
Feb 13, 2008
(55 p.)
[pdf(2)]
[html]
|
D. Petrie
S.Channabasappa |
|
A Framework for SIP User Agent Profile Delivery |
This document specifies a framework to enable configuration of
Session Initiation Protocol (SIP) User Agents in SIP deployments.
The framework provides a means to deliver profile data that User
Agents need to be functional, automatically and with minimal or no
User and Administrative intervention. The framework describes how
SIP User Agents can discover sources, request profiles and receive
notifications related to profile modifications. As part of this
framework, a new SIP event package is defined for notification of
profile changes. The framework provides minimal data retrieval
options to ensure interoperability. The framework does not include
specification of the profile data within its scope.
This document defines the 'ua-profile' SIP event package, along
with the the following event header parameters: 'profile-type', 'vendor',
'model', 'version', 'effective-by' and
'network-user'.
Three values are defined for the 'profile-type' event header parameter:
'local-network',
'device',
'user'.
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
sipping-
overload-reqs-02
In Last Call
Jan 25, 2008
(15 p.)
[pdf(2)]
[html]
|
J. Rosenberg |
|
Requirements for Management of Overload in SIP |
|
Overload occurs in Session Initiation Protocol (SIP) networks when
proxies and user agents have insuffient resources to complete the
processing of a request. SIP provides limited support for overload
handling through its 503 response code, which tells an upstream
element that it is overloaded. However, numerous problems have been
identified with this mechanism. This draft summarizes the problems
with the existing 503 mechanism, and provides some requirements for a
solution.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
sipping-
race-examples-05
AD Evaluation::
AD Follow up
Feb 18, 2008
(64 p.)
[pdf(2)]
[html]
|
M. Hasebe
J. Koshiko
Y. Suzuki
T. Yoshikawa
P. Kyzivat |
|
Example calls flows of race conditions in SIP |
|
This document gives examples call flows of race conditions in the
Session Initiation Protocol (SIP). Race conditions are inherently
confusing and difficult to thwart; this document shows the best
practices to handle them. The elements in these call flows include
SIP User Agents and SIP Proxy Servers. Call flow diagrams and
message details are given.
|
|
|
| |
| Up List |
Intended Status: | Best Current Practice |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
sipping-
sbc-funcs-05
IESG Evaluation::
Revised ID Needed
Mar 25, 2008
(25 p.)
[pdf(2)]
[html]
|
J. Hautakorpi
G. Camarillo
R. Penfield
A. Hawrylyshen
M. Bhatia |
|
Requirements from SIP Session Border Control Deployments |
|
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.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
| | |
sipping-service-
examples-14
IESG Evaluation::
Revised ID Needed
Feb 19, 2008
(165 p.)
[pdf(2)]
[html]
|
A. Johnston
R. Sparks
C. Cunningham
S. Donovan
K. Summers |
| SIP Service Examples |
|
This document gives examples of Session Initiation Protocol (SIP)
services. This covers most features offered in so-called IP Centrex
offerings from local exchange carriers and PBX (Private Branch
Exchange) features. Most of the services shown in this document are
implemented in the SIP User Agents, although some require the
assistance of a SIP Proxy. Some require some extensions to SIP
including the REFER, SUBSCRIBE, and NOTIFY methods and the Replaces
and Join header fields. These features are not intended to be an
exhaustive set, but rather show implementations of common features
likely to be implemented on SIP IP telephones in a business
environment.
|
|
|
| |
| Up List |
Intended Status: | Best Current Practice |
|
|
|
|
|
|
|
|
| | |
sipping-
sip-offeranswer-08
Publication Requested
Apr 25, 2008
(26 p.)
[pdf(2)]
[html]
|
T. Sawada
P. Kyzivat |
|
SIP Usage of the Offer/Answer Model |
|
The Session Initiation Protocol (SIP) utilizes the offer/answer
model to establish and update multimedia sessions using the Session
Description Protocol (SDP). The description of the offer/answer
model in SIP is dispersed across multiple RFCs. This document
summarizes all the current usages of the offer/answer model in SIP
communication.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
drage-sipping-
service-
identification-01
Waiting for Writeup::
Revised ID Needed
Jul 9, 2007
(20 p.)
[pdf(2)]
[html]
|
K. Drage |
|
A SIP Extension for the Identification of Services |
This document describes private extensions to the Session Initiation
Protocol (SIP) that enable a network of trusted SIP servers to assert
the service of authenticated users. The use of these extensions is
only applicable inside an administrative domain with previously
agreed-upon policies for generation, transport and usage of such
information. This document does NOT offer a general service
identification model suitable for use between different trust
domains, or use in the Internet at large.
The document also defines a URN to identify both services and UA
applications. This URN can be used to identify services within the
SIP header fields defined in this document, and also within the
framework defined for caller preferences and callee capabilities in
RFC 3840 and RFC 3841 to identify usage of both services and
applications between end UAs.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
| | |
hautakorpi-sipping-
uri-list-handling-
refused-03
Waiting for
AD Go-Ahead
Nov 12, 2007
(14 p.)
[pdf(2)]
[html]
|
J. Hautakorpi
G. Camarillo |
|
The SIP P-Refused-URI-List Private-Header (P-Header)
|
|
This document specifies the Session Initiation Protocol (SIP)
P-Refused-URI-List Private-Header (P-Header). This P-Header is used
in the Open Mobile Alliance's (OMA) Pust to talk over Cellular (PoC)
system. It enables URI-list servers to refuse the handling of
incoming URI-list that have embedded URI-lists. This P-Header also
makes it possible for the URI-list server to inform the client about
the embedded URI-list that caused the rejection and the individual
URIs that form such a URI-list.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
vanelburg-sipping-
served-user-05
IESG Evaluation::
Revised ID Needed
Apr 21, 2008
(14 p.)
[pdf(2)]
[html]
|
J. van Elburg |
|
The SIP P-Served-User Private-Header (P-Header) |
|
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 to
convey the identity of the served user and the session case that
applies to this particular communication session and application
invocation.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
## SIPPINGwg
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
|
|
|
|
|
|
|
|
|
|
| | |
sipping-media-
policy-dataset-05
ID Exists
Nov 19, 2007
(34 p.)
[pdf(2)]
[html]
|
V. Hilt
G. Camarillo
J. Rosenberg |
|
A User Agent Profile Data Set for Media Policy |
|
This specification defines a document format for the media properties
of Session Initiation Protocol (SIP) sessions. Examples for media
properties are the codecs or media types used in a session. This
document format is based on XML and extends the Schema for SIP User
Agent Profile Data Sets. It can be used to describe the properties
of a specific SIP session or to define policies that are then applied
to different SIP sessions.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
sipping-
nat-scenarios-08
ID Exists
Apr 25, 2008
(62 p.)
[pdf(2)]
[html]
|
C. Boulton
J. Rosenberg
G. Camarillo |
|
Best Current Practices for NAT Traversal for SIP |
|
Traversal of the Session Initiation Protocol (SIP) and the sessions
it establishes through Network Address Translators (NAT) is a complex
problem. Currently there are many deployment scenarios and traversal
mechanisms for media traffic. This document aims to provide concrete
recommendations and a unified method for NAT traversal as well as
documenting corresponding flows.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
| | |
sipping-profile-
datasets-00
ID Exists
Feb 15, 2008
(34 p.)
[pdf(2)]
[html]
|
S.Channabasappa
S. Ganesan
V. Hilt
D. Petrie |
|
A Schema and Guidelines for Defining SIP User Agent Profile Datasets |
|
This document defines the requirements and a format for SIP user
agent profile data. An overall schema is specified for the
definition of profile datasets. The schema also provides for
expressing constraints for how multiple sources of profile data are
to be combined. This document provides a guide to considerations,
policies and syntax for defining datasets to be included in profile
data.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
