draft-ietf-sip-hitchhikers-guide-05.txt   draft-ietf-sip-hitchhikers-guide-06.txt 
SIP J. Rosenberg SIP J. Rosenberg
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Informational February 24, 2008 Intended status: Informational November 3, 2008
Expires: August 27, 2008 Expires: May 7, 2009
A Hitchhiker's Guide to the Session Initiation Protocol (SIP) A Hitchhiker's Guide to the Session Initiation Protocol (SIP)
draft-ietf-sip-hitchhikers-guide-05 draft-ietf-sip-hitchhikers-guide-06
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 27, 2008. This Internet-Draft will expire on May 7, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
The Session Initiation Protocol (SIP) is the subject of numerous The Session Initiation Protocol (SIP) is the subject of numerous
specifications that have been produced by the IETF. It can be specifications that have been produced by the IETF. It can be
difficult to locate the right document, or even to determine the set difficult to locate the right document, or even to determine the set
of Request for Comments (RFC) about SIP. This specification serves of Request for Comments (RFC) about SIP. This specification serves
as a guide to the SIP RFC series. It lists the specifications under as a guide to the SIP RFC series. It lists a current snapshot of the
the SIP umbrella, briefly summarizes each, and groups them into specifications under the SIP umbrella, briefly summarizes each, and
categories. groups them into categories.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Scope of this Document . . . . . . . . . . . . . . . . . . . . 4 2. Scope of this Document . . . . . . . . . . . . . . . . . . . . 5
3. Core SIP Specifications . . . . . . . . . . . . . . . . . . . 5 3. Core SIP Specifications . . . . . . . . . . . . . . . . . . . 6
4. Public Switched Telephone Network (PSTN) Interworking . . . . 9 4. Public Switched Telephone Network (PSTN) Interworking . . . . 9
5. General Purpose Infrastructure Extensions . . . . . . . . . . 11 5. General Purpose Infrastructure Extensions . . . . . . . . . . 11
6. NAT Traversal . . . . . . . . . . . . . . . . . . . . . . . . 13 6. NAT Traversal . . . . . . . . . . . . . . . . . . . . . . . . 13
7. Call Control Primitives . . . . . . . . . . . . . . . . . . . 14 7. Call Control Primitives . . . . . . . . . . . . . . . . . . . 14
8. Event Framework . . . . . . . . . . . . . . . . . . . . . . . 15 8. Event Framework . . . . . . . . . . . . . . . . . . . . . . . 15
9. Event Packages . . . . . . . . . . . . . . . . . . . . . . . . 16 9. Event Packages . . . . . . . . . . . . . . . . . . . . . . . . 16
10. Quality of Service . . . . . . . . . . . . . . . . . . . . . . 17 10. Quality of Service . . . . . . . . . . . . . . . . . . . . . . 17
11. Operations and Management . . . . . . . . . . . . . . . . . . 18 11. Operations and Management . . . . . . . . . . . . . . . . . . 18
12. SIP Compression . . . . . . . . . . . . . . . . . . . . . . . 19 12. SIP Compression . . . . . . . . . . . . . . . . . . . . . . . 19
13. SIP Service URIs . . . . . . . . . . . . . . . . . . . . . . . 19 13. SIP Service URIs . . . . . . . . . . . . . . . . . . . . . . . 19
14. Minor Extensions . . . . . . . . . . . . . . . . . . . . . . . 20 14. Minor Extensions . . . . . . . . . . . . . . . . . . . . . . . 20
15. Security Mechanisms . . . . . . . . . . . . . . . . . . . . . 22 15. Security Mechanisms . . . . . . . . . . . . . . . . . . . . . 22
16. Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 25 16. Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 26
17. Instant Messaging, Presence and Multimedia . . . . . . . . . . 26 17. Instant Messaging, Presence and Multimedia . . . . . . . . . . 27
18. Emergency Services . . . . . . . . . . . . . . . . . . . . . . 27 18. Emergency Services . . . . . . . . . . . . . . . . . . . . . . 27
19. Security Considerations . . . . . . . . . . . . . . . . . . . 27 19. Security Considerations . . . . . . . . . . . . . . . . . . . 28
20. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 20. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
21. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27 21. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 28
22. Informative References . . . . . . . . . . . . . . . . . . . . 28 22. Informative References . . . . . . . . . . . . . . . . . . . . 28
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 41 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 41
Intellectual Property and Copyright Statements . . . . . . . . . . 42 Intellectual Property and Copyright Statements . . . . . . . . . . 42
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) [RFC3261] is the subject of The Session Initiation Protocol (SIP) [RFC3261] is the subject of
numerous specifications that have been produced by the IETF. It can numerous specifications that have been produced by the IETF. It can
be difficult to locate the right document, or even to determine the be difficult to locate the right document, or even to determine the
set of Request for Comments (RFC) about SIP. Don't Panic! [HGTTG] set of Request for Comments (RFC) about SIP. Don't Panic! [HGTTG]
This specification serves as a guide to the SIP RFC series. It lists This specification serves as a guide to the SIP RFC series. It is a
the specifications under the SIP umbrella. For each specification, a current snapshot of the specifications under the SIP umbrella at the
paragraph or so description is included that summarizes the purpose time of publication. It is anticipated that this document itself
of the specification. Each specification also includes a letter that will be regularly updated as SIP specifications mature. Furthermore,
designates its category in the standards track [RFC2026]. These it references many specifications, which, at time of publication of
values are: this document, were not yet finalized, and may eventually be
completed or abandoned. Therefore, the enumeration of specifications
here is a work-in-progress and subject to change.
For each specification, a paragraph or so description is included
that summarizes the purpose of the specification. Each specification
also includes a letter that designates its category in the standards
track [RFC2026]. These values are:
S: Standards Track (Proposed Standard, Draft Standard, or Standard) S: Standards Track (Proposed Standard, Draft Standard, or Standard)
E: Experimental E: Experimental
B: Best Current Practice B: Best Current Practice
I: Informational I: Informational
The specifications are grouped together by topic. The topics are: The specifications are grouped together by topic. The topics are:
skipping to change at page 17, line 32 skipping to change at page 17, line 32
tell user agents about the media characteristics required for a tell user agents about the media characteristics required for a
particular session. The session policy framework has not been particular session. The session policy framework has not been
widely implemented. widely implemented.
draft-ietf-sipping-policy-package, A Session Initiation Protocol draft-ietf-sipping-policy-package, A Session Initiation Protocol
(SIP) Event Package for Session-Specific Session Policies (S): (SIP) Event Package for Session-Specific Session Policies (S):
[I-D.ietf-sipping-policy-package] defines a SIP event package used [I-D.ietf-sipping-policy-package] defines a SIP event package used
in conjunction with the session policy framework in conjunction with the session policy framework
[I-D.ietf-sip-session-policy-framework]. [I-D.ietf-sip-session-policy-framework].
draft-ietf-sipping-pending-additions, The Session Initiation Protocol RFC 5362, The Session Initiation Protocol (SIP) Pending Additions
(SIP) Pending Additions Event Package (S): Event Package (S): [RFC5362] defines a SIP event package that allows
[I-D.ietf-sipping-pending-additions] defines a SIP event package a UA to learn whether consent has been given for the addition of
that allows a UA to learn whether consent has been given for the an address to a SIP "mailing list". It is used in conjunction
addition of an address to a SIP "mailing list". It is used in with the SIP framework for consent [RFC5360].
conjunction with the SIP framework for consent
[I-D.ietf-sip-consent-framework].
10. Quality of Service 10. Quality of Service
Several specifications concern themselves with the interactions of Several specifications concern themselves with the interactions of
SIP with network Quality of Service (QoS) mechanisms. SIP with network Quality of Service (QoS) mechanisms.
RFC 3312, Integration of Resource Management and SIP (S): [RFC3312], RFC 3312, Integration of Resource Management and SIP (S): [RFC3312],
updated by [RFC4032] defines a way to make sure that the phone of updated by [RFC4032] defines a way to make sure that the phone of
the called party doesn't ring until a QoS reservation has been the called party doesn't ring until a QoS reservation has been
installed in the network. It does so by defining a general installed in the network. It does so by defining a general
skipping to change at page 19, line 15 skipping to change at page 19, line 15
12. SIP Compression 12. SIP Compression
Sigcomp [RFC3320] [RFC4896] was defined to allow compression of SIP Sigcomp [RFC3320] [RFC4896] was defined to allow compression of SIP
messages over low bandwidth links. Sigcomp is not formally part of messages over low bandwidth links. Sigcomp is not formally part of
SIP. However, usage of Sigcomp with SIP has required extensions to SIP. However, usage of Sigcomp with SIP has required extensions to
SIP. SIP.
RFC 3486, Compressing SIP (S): [RFC3486] defines a SIP URI parameter RFC 3486, Compressing SIP (S): [RFC3486] defines a SIP URI parameter
that can be used to indicate that a SIP server supports Sigcomp. that can be used to indicate that a SIP server supports Sigcomp.
draft-ietf-rohc-sigcomp-sip, Applying Signaling Compression (SigComp) RFC 5049, Applying Signaling Compression (SigComp) to the Session
to the Session Initiation Protocol (SIP) (S): Initiation Protocol (SIP) (S): [RFC5049] defines how to apply
[I-D.ietf-rohc-sigcomp-sip] defines how to apply Sigcomp to SIP. Sigcomp to SIP.
13. SIP Service URIs 13. SIP Service URIs
Several extensions define well-known services that can be invoked by Several extensions define well-known services that can be invoked by
constructing requests with the specific structures for the Request constructing requests with the specific structures for the Request
URI, resulting in specific behaviors at the UAS. URI, resulting in specific behaviors at the UAS.
RFC 3087, Control of Service Context using Request URI (I): RFC 3087, Control of Service Context using Request URI (I):
[RFC3087] introduced the context of using Request URIs, encoded [RFC3087] introduced the context of using Request URIs, encoded
appropriately, to invoke services. appropriately, to invoke services.
RFC 4662, A SIP Event Notification Extension for Resource Lists (S): RFC 4662, A SIP Event Notification Extension for Resource Lists (S):
[RFC4662] defines a resource called a Resource List Server. A [RFC4662] defines a resource called a Resource List Server. A
client can send a subscribe to this server. The server will client can send a subscribe to this server. The server will
generate a series of subscriptions, and compile the resulting generate a series of subscriptions, and compile the resulting
information and send it back to the subscriber. The set of information and send it back to the subscriber. The set of
resources that the RLS will subscribe to is a property of the resources that the RLS will subscribe to is a property of the
request URI in the SUBSCRIBE request. request URI in the SUBSCRIBE request.
draft-ietf-sipping-uri-services, Framework and Security RFC 5363, Framework and Security Considerations for Session
Considerations for Session Initiation Protocol (SIP) Uniform Resource Initiation Protocol (SIP) Uniform Resource Identifier (URI)-List
Identifier (URI)-List Services (S): [I-D.ietf-sipping-uri-services] Services (S): [RFC5363] defines the framework for list services in
defines the framework for list services in SIP. In this SIP. In this framework, a UA can include an XML list object in
framework, a UA can include an XML list object in the body of the body of various requests and the server provides list-oriented
various requests and the server provides list-oriented services as services as a consequence. For example, a SUBSCRIBE with a list
a consequence. For example, a SUBSCRIBE with a list subscribes to subscribes to the URI in the list.
the URI in the list.
draft-ietf-sip-uri-list-subscribe, Subscriptions To Request-Contained RFC 5367, Subscriptions To Request-Contained Resource Lists in SIP
Resource Lists in SIP (S): [I-D.ietf-sip-uri-list-subscribe] uses (S): [RFC5367] uses the URI list framework [RFC5363] and allows a
the URI list framework [I-D.ietf-sipping-uri-services] and allows client to subscribe to a resource called a Resource List Server.
a client to subscribe to a resource called a Resource List Server.
This server will generate subscriptions to the URI in the list, This server will generate subscriptions to the URI in the list,
and compile the resulting information and send it back to the and compile the resulting information and send it back to the
subscriber. subscriber.
draft-ietf-sip-uri-list-message, Multiple-Recipient MESSAGE Requests RFC 5365, Multiple-Recipient MESSAGE Requests in SIP (S): [RFC5365]
in SIP (S): [I-D.ietf-sip-uri-list-message] uses the URI list uses the URI list framework [RFC5363] and allows a client to send
framework [I-D.ietf-sipping-uri-services] and allows a client to a MESSAGE to a number of recipients.
send a MESSAGE to a number of recipients.
draft-ietf-sip-uri-list-conferencing, Conference Establishment Using RFC 5366, Conference Establishment Using Request-Contained Lists in
Request-Contained Lists in SIP (S): SIP (S): [RFC5366] uses the URI list framework [RFC5363] and allows
[I-D.ietf-sip-uri-list-conferencing] uses the URI list framework a client to ask the server to act as a conference focus and send
[I-D.ietf-sipping-uri-services] and allows a client to ask the an invitation to each recipient in the list.
server to act as a conference focus and send an invitation to each
recipient in the list.
RFC 4240, Basic Network Media Services with SIP (I): [RFC4240] RFC 4240, Basic Network Media Services with SIP (I): [RFC4240]
defines a way for SIP application servers to invoke announcement defines a way for SIP application servers to invoke announcement
and conferencing services from a media server. This is and conferencing services from a media server. This is
accomplished through a set of defined URI parameters which tell accomplished through a set of defined URI parameters which tell
the media server what to do, such as what file to play and what the media server what to do, such as what file to play and what
language to render it in. language to render it in.
RFC 4458, Session Initiation Protocol (SIP) URIs for Applications RFC 4458, Session Initiation Protocol (SIP) URIs for Applications
such as Voicemail and Interactive Voice Response (IVR) (I): such as Voicemail and Interactive Voice Response (IVR) (I):
skipping to change at page 21, line 23 skipping to change at page 21, line 17
the called party whether or not the phone should ring and/or be the called party whether or not the phone should ring and/or be
answered immediately. This is useful for push-to-talk and for answered immediately. This is useful for push-to-talk and for
diagnostic applications. diagnostic applications.
RFC 5079, Rejecting Anonymous Requests in SIP (S): [RFC5079] defines RFC 5079, Rejecting Anonymous Requests in SIP (S): [RFC5079] defines
a mechanism for a called party to indicate to the calling party a mechanism for a called party to indicate to the calling party
that a call was rejected since the caller was anonymous. This is that a call was rejected since the caller was anonymous. This is
needed for implementation of the Anonymous Call Rejection (ACR) needed for implementation of the Anonymous Call Rejection (ACR)
feature in SIP. feature in SIP.
draft-ietf-sip-multiple-refer, Referring to Multiple Resources in SIP RFC 5368, Referring to Multiple Resources in SIP (S): [RFC5368]
(S): [I-D.ietf-sip-multiple-refer] allows a UA sending a REFER to allows a UA sending a REFER to ask the recipient of the REFER to
ask the recipient of the REFER to generate multiple SIP requests, generate multiple SIP requests, not just one. This is useful for
not just one. This is useful for conferencing, where a client conferencing, where a client would like to ask a conference server
would like to ask a conference server to eject multiple users. to eject multiple users.
RFC 4483, A Mechanism for Content Indirection in Session Initiation RFC 4483, A Mechanism for Content Indirection in Session Initiation
Protocol (SIP) Messages (S): [RFC4483] defines a mechanism for Protocol (SIP) Messages (S): [RFC4483] defines a mechanism for
content indirection. Instead of carrying an object within a SIP content indirection. Instead of carrying an object within a SIP
body, a URL reference is carried instead, and the recipient body, a URL reference is carried instead, and the recipient
dereferences the URL to obtain the object. The specification has dereferences the URL to obtain the object. The specification has
potential applicability for sending large instant messages, but potential applicability for sending large instant messages, but
has yet to find much actual use. has yet to find much actual use.
RFC 3890, A Transport Independent Bandwidth Modifier for the Session RFC 3890, A Transport Independent Bandwidth Modifier for the Session
skipping to change at page 24, line 29 skipping to change at page 24, line 29
which can be signed in order to provide an authenticated identity which can be signed in order to provide an authenticated identity
over a request. It was an early predecessor to [RFC4474], and over a request. It was an early predecessor to [RFC4474], and
consequently AIB has seen no deployment. consequently AIB has seen no deployment.
draft-ietf-sip-saml, SIP SAML Profile and Binding (S): draft-ietf-sip-saml, SIP SAML Profile and Binding (S):
[I-D.ietf-sip-saml] defines the usage of the Security Assertion [I-D.ietf-sip-saml] defines the usage of the Security Assertion
Markup Language (SAML) within SIP, and describes how to use it in Markup Language (SAML) within SIP, and describes how to use it in
conjunction with SIP identity [RFC4474] to provide authenticated conjunction with SIP identity [RFC4474] to provide authenticated
assertions about a users role or attributes. assertions about a users role or attributes.
draft-ietf-sip-consent-framework, A Framework for Consent-Based RFC 5360, A Framework for Consent-Based Communications in the
Communications in the Session Initiation Protocol (SIP) (S): Session Initiation Protocol (SIP) (S): [RFC5360] defines several
[I-D.ietf-sip-consent-framework] defines several extensions to extensions to SIP, including the Trigger-Consent and Permission-
SIP, including the Trigger-Consent and Permission-Missing header Missing header fields. These header fields, in addition to the
fields. These header fields, in addition to the other procedures other procedures defined in the document, define a way to manage
defined in the document, define a way to manage membership on "SIP membership on "SIP mailing lists" used for instant messaging or
mailing lists" used for instant messaging or conferencing. In conferencing. In particular, it helps avoid the problem of using
particular, it helps avoid the problem of using such amplification such amplification services for the purposes of an attack on the
services for the purposes of an attack on the network, by making network, by making sure a user authorizes the addition of their
sure a user authorizes the addition of their address onto such a address onto such a service.
service.
draft-ietf-sipping-consent-format, A Document Format for Requesting RFC 5361, A Document Format for Requesting Consent (S): [RFC5361]
Consent (S): [I-D.ietf-sipping-consent-format] defines an XML object defines an XML object used by the consent framework. Consent
used by the consent framework. Consent documents are sent from documents are sent from SIP "mailing list servers" to users to
SIP "mailing list servers" to users to allow them to manage their allow them to manage their membership on lists.
membership on lists.
draft-ietf-sipping-pending-additions, The Session Initiation Protocol RFC 5362, The Session Initiation Protocol (SIP) Pending Additions
(SIP) Pending Additions Event Package (S): Event Package (S): [RFC5362] defines a SIP event package that allows
[I-D.ietf-sipping-pending-additions] defines a SIP event package a UA to learn whether consent has been given for the addition of
that allows a UA to learn whether consent has been given for the an address to a SIP "mailing list". It is used in conjunction
addition of an address to a SIP "mailing list". It is used in with the SIP framework for consent [RFC5360].
conjunction with the SIP framework for consent
[I-D.ietf-sip-consent-framework].
RFC 3329, Security Mechanism Agreement for SIP (S): [RFC3329] RFC 3329, Security Mechanism Agreement for SIP (S): [RFC3329]
defines a mechanism to prevent bid-down attacks in conjunction defines a mechanism to prevent bid-down attacks in conjunction
with SIP authentication. The mechanism has seen very limited with SIP authentication. The mechanism has seen very limited
deployment. It was defined as part of the 3gpp IMS specification deployment. It was defined as part of the 3gpp IMS specification
suite [3GPP.24.229], and is needed only when there is a suite [3GPP.24.229], and is needed only when there is a
multiplicity of security mechanisms deployed at a particular multiplicity of security mechanisms deployed at a particular
server. In practice, this has not been the case. server. In practice, this has not been the case.
draft-ietf-sip-e2m-sec, End-to-Middle Security in SIP (S): draft-ietf-sip-e2m-sec, End-to-Middle Security in SIP (S):
skipping to change at page 25, line 33 skipping to change at page 25, line 32
signaling parameters defined in [RFC4145] to include fingerprint signaling parameters defined in [RFC4145] to include fingerprint
information for TLS streams, so that TLS can operate between end information for TLS streams, so that TLS can operate between end
hosts using self-signed certificates. hosts using self-signed certificates.
RFC 5027, Security Preconditions for Session Description Protocol RFC 5027, Security Preconditions for Session Description Protocol
Media Streams (S): [RFC5027] defines a precondition for use with the Media Streams (S): [RFC5027] defines a precondition for use with the
preconditions framework [RFC3312]. The security precondition preconditions framework [RFC3312]. The security precondition
prevents a session from being established until a security media prevents a session from being established until a security media
stream is set up. stream is set up.
RFC 3310, Hypertext Transfer Protocol (HTTP) Digest Authentication
Using Authentication and Key Agreement (S): [RFC3310] defines an
extension to digest authentication to allow it to work with the
credentials stored in cell phones. Though technically it is an
extension to HTTP digest, it's primary application is SIP. This
extension is usefully primarily to implementors of IMS.
RFC 4169, Hypertext Transfer Protocol (HTTP) Digest Authentication
Using Authentication and Key Agreement (AKA) Version-2 (S):
[RFC4169] is an enhancement to [RFC3310] which further improves
security of the authentication.
RFC 3329, Security Mechanism Agreement for SIP (S): [RFC3329] is a
SIP security extension meant to be used in conjunction with IMS,
to ensure that there are no bid-down attacks in the negotiation of
an authentication mechanism.
16. Conferencing 16. Conferencing
Numerous SIP and SDP extensions are aimed at conferencing as their Numerous SIP and SDP extensions are aimed at conferencing as their
primary application. primary application.
RFC 4574, The SDP (Session Description Protocol) Label Attribute RFC 4574, The SDP (Session Description Protocol) Label Attribute
(S): [RFC4574] defines an SDP attribute for providing an opaque (S): [RFC4574] defines an SDP attribute for providing an opaque
label for media streams. These labels can be referred to by label for media streams. These labels can be referred to by
external documents, and in particular, by conference policy external documents, and in particular, by conference policy
documents. This allows a UA to tie together documents it may documents. This allows a UA to tie together documents it may
skipping to change at page 26, line 9 skipping to change at page 26, line 27
RFC 3911, The SIP Join Header Field (S): [RFC3911] defines the Join RFC 3911, The SIP Join Header Field (S): [RFC3911] defines the Join
header field. When sent in an INVITE, it causes the recipient to header field. When sent in an INVITE, it causes the recipient to
join the resulting dialog into a conference with another dialog in join the resulting dialog into a conference with another dialog in
progress. progress.
RFC 4575, A SIP Event Package for Conference State (S): [RFC4575] RFC 4575, A SIP Event Package for Conference State (S): [RFC4575]
defines a mechanism for learning about changes in conference defines a mechanism for learning about changes in conference
state, including conference membership. state, including conference membership.
draft-ietf-sip-multiple-refer, Referring to Multiple Resources in SIP RFC 5368, Referring to Multiple Resources in SIP (S): [RFC5368]
(S): [I-D.ietf-sip-multiple-refer] allows a UA sending a REFER to allows a UA sending a REFER to ask the recipient of the REFER to
ask the recipient of the REFER to generate multiple SIP requests, generate multiple SIP requests, not just one. This is useful for
not just one. This is useful for conferencing, where a client conferencing, where a client would like to ask a conference server
would like to ask a conference server to eject multiple users. to eject multiple users.
draft-ietf-sip-uri-list-conferencing, Conference Establishment Using RFC 5366, Conference Establishment Using Request-Contained Lists in
Request-Contained Lists in SIP (S): SIP (S): [RFC5366] is similar to [RFC5367]. However, instead of
[I-D.ietf-sip-uri-list-conferencing] is similar to
[I-D.ietf-sip-uri-list-subscribe]. However, instead of
subscribing to the resource, an INVITE request is sent to the subscribing to the resource, an INVITE request is sent to the
resource, and it will act as a conference focus and generate an resource, and it will act as a conference focus and generate an
invitation to each recipient in the list. invitation to each recipient in the list.
RFC4579, Session Initiation Protocol (SIP) Call Control - RFC4579, Session Initiation Protocol (SIP) Call Control -
Conferencing for User Agents (B): [RFC4579] defines best practice Conferencing for User Agents (B): [RFC4579] defines best practice
procedures and call flows for conferencing. This includes procedures and call flows for conferencing. This includes
conference creation, joining, and dial out, amongst other conference creation, joining, and dial out, amongst other
capabilities. capabilities.
skipping to change at page 29, line 44 skipping to change at page 30, line 15
[I-D.ietf-sip-gruu] [I-D.ietf-sip-gruu]
Rosenberg, J., "Obtaining and Using Globally Routable User Rosenberg, J., "Obtaining and Using Globally Routable User
Agent (UA) URIs (GRUU) in the Session Initiation Protocol Agent (UA) URIs (GRUU) in the Session Initiation Protocol
(SIP)", draft-ietf-sip-gruu-15 (work in progress), (SIP)", draft-ietf-sip-gruu-15 (work in progress),
October 2007. October 2007.
[I-D.ietf-sip-outbound] [I-D.ietf-sip-outbound]
Jennings, C. and R. Mahy, "Managing Client Initiated Jennings, C. and R. Mahy, "Managing Client Initiated
Connections in the Session Initiation Protocol (SIP)", Connections in the Session Initiation Protocol (SIP)",
draft-ietf-sip-outbound-11 (work in progress), draft-ietf-sip-outbound-16 (work in progress),
November 2007. October 2008.
[RFC2848] Petrack, S. and L. Conroy, "The PINT Service Protocol: [RFC2848] Petrack, S. and L. Conroy, "The PINT Service Protocol:
Extensions to SIP and SDP for IP Access to Telephone Call Extensions to SIP and SDP for IP Access to Telephone Call
Services", RFC 2848, June 2000. Services", RFC 2848, June 2000.
[RFC3910] Gurbani, V., Brusilovsky, A., Faynberg, I., Gato, J., Lu, [RFC3910] Gurbani, V., Brusilovsky, A., Faynberg, I., Gato, J., Lu,
H., and M. Unmehopa, "The SPIRITS (Services in PSTN H., and M. Unmehopa, "The SPIRITS (Services in PSTN
requesting Internet Services) Protocol", RFC 3910, requesting Internet Services) Protocol", RFC 3910,
October 2004. October 2004.
skipping to change at page 31, line 30 skipping to change at page 31, line 51
Identification in the Session Initiation Protocol (SIP)", Identification in the Session Initiation Protocol (SIP)",
RFC 4538, June 2006. RFC 4538, June 2006.
[RFC4508] Levin, O. and A. Johnston, "Conveying Feature Tags with [RFC4508] Levin, O. and A. Johnston, "Conveying Feature Tags with
the Session Initiation Protocol (SIP) REFER Method", the Session Initiation Protocol (SIP) REFER Method",
RFC 4508, May 2006. RFC 4508, May 2006.
[I-D.ietf-sip-answermode] [I-D.ietf-sip-answermode]
Willis, D. and A. Allen, "Requesting Answering Modes for Willis, D. and A. Allen, "Requesting Answering Modes for
the Session Initiation Protocol (SIP)", the Session Initiation Protocol (SIP)",
draft-ietf-sip-answermode-06 (work in progress), draft-ietf-sip-answermode-07 (work in progress), May 2008.
September 2007.
[HGTTG] Adams, D., "The Hitchhiker's Guide to the Galaxy", [HGTTG] Adams, D., "The Hitchhiker's Guide to the Galaxy",
September 1979. September 1979.
[RFC5079] Rosenberg, J., "Rejecting Anonymous Requests in the [RFC5079] Rosenberg, J., "Rejecting Anonymous Requests in the
Session Initiation Protocol (SIP)", RFC 5079, Session Initiation Protocol (SIP)", RFC 5079,
December 2007. December 2007.
[I-D.ietf-sip-multiple-refer] [RFC5368] Camarillo, G., Niemi, A., Isomaki, M., Garcia-Martin, M.,
Camarillo, G., Niemi, A., Isomaki, M., Garcia-Martin, M.,
and H. Khartabil, "Referring to Multiple Resources in the and H. Khartabil, "Referring to Multiple Resources in the
Session Initiation Protocol (SIP)", Session Initiation Protocol (SIP)", RFC 5368,
draft-ietf-sip-multiple-refer-03 (work in progress), October 2008.
December 2007.
[RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer [RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer
Method", RFC 3515, April 2003. Method", RFC 3515, April 2003.
[RFC3725] Rosenberg, J., Peterson, J., Schulzrinne, H., and G. [RFC3725] Rosenberg, J., Peterson, J., Schulzrinne, H., and G.
Camarillo, "Best Current Practices for Third Party Call Camarillo, "Best Current Practices for Third Party Call
Control (3pcc) in the Session Initiation Protocol (SIP)", Control (3pcc) in the Session Initiation Protocol (SIP)",
BCP 85, RFC 3725, April 2004. BCP 85, RFC 3725, April 2004.
[RFC3891] Mahy, R., Biggs, B., and R. Dean, "The Session Initiation [RFC3891] Mahy, R., Biggs, B., and R. Dean, "The Session Initiation
skipping to change at page 32, line 48 skipping to change at page 33, line 18
[RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session [RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
Initiation Protocol (SIP) Event Package for Conference Initiation Protocol (SIP) Event Package for Conference
State", RFC 4575, August 2006. State", RFC 4575, August 2006.
[RFC4730] Burger, E. and M. Dolly, "A Session Initiation Protocol [RFC4730] Burger, E. and M. Dolly, "A Session Initiation Protocol
(SIP) Event Package for Key Press Stimulus (KPML)", (SIP) Event Package for Key Press Stimulus (KPML)",
RFC 4730, November 2006. RFC 4730, November 2006.
[I-D.ietf-sipping-rtcp-summary] [I-D.ietf-sipping-rtcp-summary]
Pendleton, A., "Session Initiation Protocol Package for Clark, A., Pendleton, A., Johnston, A., and H. Sinnreich,
Voice Quality Reporting Event", "Session Initiation Protocol Package for Voice Quality
draft-ietf-sipping-rtcp-summary-02 (work in progress), Reporting Event", draft-ietf-sipping-rtcp-summary-05 (work
May 2007. in progress), October 2008.
[RFC3312] Camarillo, G., Marshall, W., and J. Rosenberg, [RFC3312] Camarillo, G., Marshall, W., and J. Rosenberg,
"Integration of Resource Management and Session Initiation "Integration of Resource Management and Session Initiation
Protocol (SIP)", RFC 3312, October 2002. Protocol (SIP)", RFC 3312, October 2002.
[RFC4032] Camarillo, G. and P. Kyzivat, "Update to the Session [RFC4032] Camarillo, G. and P. Kyzivat, "Update to the Session
Initiation Protocol (SIP) Preconditions Framework", Initiation Protocol (SIP) Preconditions Framework",
RFC 4032, March 2005. RFC 4032, March 2005.
[RFC3313] Marshall, W., "Private Session Initiation Protocol (SIP) [RFC3313] Marshall, W., "Private Session Initiation Protocol (SIP)
skipping to change at page 33, line 37 skipping to change at page 34, line 6
the Global Switched Telephone Network (GSTN): An the Global Switched Telephone Network (GSTN): An
Overview", RFC 3482, February 2003. Overview", RFC 3482, February 2003.
[RFC3087] Campbell, B. and R. Sparks, "Control of Service Context [RFC3087] Campbell, B. and R. Sparks, "Control of Service Context
using SIP Request-URI", RFC 3087, April 2001. using SIP Request-URI", RFC 3087, April 2001.
[RFC4662] Roach, A., Campbell, B., and J. Rosenberg, "A Session [RFC4662] Roach, A., Campbell, B., and J. Rosenberg, "A Session
Initiation Protocol (SIP) Event Notification Extension for Initiation Protocol (SIP) Event Notification Extension for
Resource Lists", RFC 4662, August 2006. Resource Lists", RFC 4662, August 2006.
[I-D.ietf-sip-uri-list-subscribe] [RFC5367] Camarillo, G., Roach, A., and O. Levin, "Subscriptions to
Camarillo, G., Roach, A., and O. Levin, "Subscriptions to
Request-Contained Resource Lists in the Session Initiation Request-Contained Resource Lists in the Session Initiation
Protocol (SIP)", draft-ietf-sip-uri-list-subscribe-02 Protocol (SIP)", RFC 5367, October 2008.
(work in progress), November 2007.
[I-D.ietf-sip-uri-list-message] [RFC5365] Garcia-Martin, M. and G. Camarillo, "Multiple-Recipient
Garcia-Martin, M. and G. Camarillo, "Multiple-Recipient
MESSAGE Requests in the Session Initiation Protocol MESSAGE Requests in the Session Initiation Protocol
(SIP)", draft-ietf-sip-uri-list-message-03 (work in (SIP)", RFC 5365, October 2008.
progress), December 2007.
[I-D.ietf-sip-uri-list-conferencing] [RFC5366] Camarillo, G. and A. Johnston, "Conference Establishment
Camarillo, G. and A. Johnston, "Conference Establishment
Using Request-Contained Lists in the Session Initiation Using Request-Contained Lists in the Session Initiation
Protocol (SIP)", draft-ietf-sip-uri-list-conferencing-02 Protocol (SIP)", RFC 5366, October 2008.
(work in progress), November 2007.
[RFC3853] Peterson, J., "S/MIME Advanced Encryption Standard (AES) [RFC3853] Peterson, J., "S/MIME Advanced Encryption Standard (AES)
Requirement for the Session Initiation Protocol (SIP)", Requirement for the Session Initiation Protocol (SIP)",
RFC 3853, July 2004. RFC 3853, July 2004.
[RFC3329] Arkko, J., Torvinen, V., Camarillo, G., Niemi, A., and T. [RFC3329] Arkko, J., Torvinen, V., Camarillo, G., Niemi, A., and T.
Haukka, "Security Mechanism Agreement for the Session Haukka, "Security Mechanism Agreement for the Session
Initiation Protocol (SIP)", RFC 3329, January 2003. Initiation Protocol (SIP)", RFC 3329, January 2003.
[I-D.ietf-sip-e2m-sec] [I-D.ietf-sip-e2m-sec]
skipping to change at page 35, line 7 skipping to change at page 35, line 20
in Session Description Protocol (SDP)", RFC 3605, in Session Description Protocol (SDP)", RFC 3605,
October 2003. October 2003.
[RFC4916] Elwell, J., "Connected Identity in the Session Initiation [RFC4916] Elwell, J., "Connected Identity in the Session Initiation
Protocol (SIP)", RFC 4916, June 2007. Protocol (SIP)", RFC 4916, June 2007.
[I-D.ietf-sip-fork-loop-fix] [I-D.ietf-sip-fork-loop-fix]
Sparks, R., Lawrence, S., Hawrylyshen, A., and B. Campen, Sparks, R., Lawrence, S., Hawrylyshen, A., and B. Campen,
"Addressing an Amplification Vulnerability in Session "Addressing an Amplification Vulnerability in Session
Initiation Protocol (SIP) Forking Proxies", Initiation Protocol (SIP) Forking Proxies",
draft-ietf-sip-fork-loop-fix-06 (work in progress), draft-ietf-sip-fork-loop-fix-08 (work in progress),
November 2007. October 2008.
[RFC3959] Camarillo, G., "The Early Session Disposition Type for the [RFC3959] Camarillo, G., "The Early Session Disposition Type for the
Session Initiation Protocol (SIP)", RFC 3959, Session Initiation Protocol (SIP)", RFC 3959,
December 2004. December 2004.
[RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,
F., Watson, M., and M. Zonoun, "MIME media types for ISUP F., Watson, M., and M. Zonoun, "MIME media types for ISUP
and QSIG Objects", RFC 3204, December 2001. and QSIG Objects", RFC 3204, December 2001.
[RFC3420] Sparks, R., "Internet Media Type message/sipfrag", [RFC3420] Sparks, R., "Internet Media Type message/sipfrag",
skipping to change at page 35, line 32 skipping to change at page 35, line 45
the Session Description Protocol (SDP)", RFC 4145, the Session Description Protocol (SDP)", RFC 4145,
September 2005. September 2005.
[RFC4091] Camarillo, G. and J. Rosenberg, "The Alternative Network [RFC4091] Camarillo, G. and J. Rosenberg, "The Alternative Network
Address Types (ANAT) Semantics for the Session Description Address Types (ANAT) Semantics for the Session Description
Protocol (SDP) Grouping Framework", RFC 4091, June 2005. Protocol (SDP) Grouping Framework", RFC 4091, June 2005.
[I-D.ietf-mmusic-ice-tcp] [I-D.ietf-mmusic-ice-tcp]
Rosenberg, J., "TCP Candidates with Interactive Rosenberg, J., "TCP Candidates with Interactive
Connectivity Establishment (ICE)", Connectivity Establishment (ICE)",
draft-ietf-mmusic-ice-tcp-05 (work in progress), draft-ietf-mmusic-ice-tcp-07 (work in progress),
November 2007. July 2008.
[RFC4483] Burger, E., "A Mechanism for Content Indirection in [RFC4483] Burger, E., "A Mechanism for Content Indirection in
Session Initiation Protocol (SIP) Messages", RFC 4483, Session Initiation Protocol (SIP) Messages", RFC 4483,
May 2006. May 2006.
[RFC3890] Westerlund, M., "A Transport Independent Bandwidth [RFC3890] Westerlund, M., "A Transport Independent Bandwidth
Modifier for the Session Description Protocol (SDP)", Modifier for the Session Description Protocol (SDP)",
RFC 3890, September 2004. RFC 3890, September 2004.
[RFC4583] Camarillo, G., "Session Description Protocol (SDP) Format [RFC4583] Camarillo, G., "Session Description Protocol (SDP) Format
skipping to change at page 36, line 7 skipping to change at page 36, line 19
RFC 4583, November 2006. RFC 4583, November 2006.
[RFC5027] Andreasen, F. and D. Wing, "Security Preconditions for [RFC5027] Andreasen, F. and D. Wing, "Security Preconditions for
Session Description Protocol (SDP) Media Streams", Session Description Protocol (SDP) Media Streams",
RFC 5027, October 2007. RFC 5027, October 2007.
[I-D.ietf-mmusic-connectivity-precon] [I-D.ietf-mmusic-connectivity-precon]
Andreasen, F., Camarillo, G., Oran, D., and D. Wing, Andreasen, F., Camarillo, G., Oran, D., and D. Wing,
"Connectivity Preconditions for Session Description "Connectivity Preconditions for Session Description
Protocol Media Streams", Protocol Media Streams",
draft-ietf-mmusic-connectivity-precon-04 (work in draft-ietf-mmusic-connectivity-precon-05 (work in
progress), January 2008. progress), October 2008.
[RFC4796] Hautakorpi, J. and G. Camarillo, "The Session Description [RFC4796] Hautakorpi, J. and G. Camarillo, "The Session Description
Protocol (SDP) Content Attribute", RFC 4796, Protocol (SDP) Content Attribute", RFC 4796,
February 2007. February 2007.
[RFC4574] Levin, O. and G. Camarillo, "The Session Description [RFC4574] Levin, O. and G. Camarillo, "The Session Description
Protocol (SDP) Label Attribute", RFC 4574, August 2006. Protocol (SDP) Label Attribute", RFC 4574, August 2006.
[I-D.ietf-sipping-policy-package] [I-D.ietf-sipping-policy-package]
Hilt, V. and G. Camarillo, "A Session Initiation Protocol Hilt, V. and G. Camarillo, "A Session Initiation Protocol
(SIP) Event Package for Session-Specific Session (SIP) Event Package for Session-Specific Session
Policies", draft-ietf-sipping-policy-package-04 (work in Policies.", draft-ietf-sipping-policy-package-05 (work in
progress), August 2007. progress), July 2008.
[RFC3524] Camarillo, G. and A. Monrad, "Mapping of Media Streams to [RFC3524] Camarillo, G. and A. Monrad, "Mapping of Media Streams to
Resource Reservation Flows", RFC 3524, April 2003. Resource Reservation Flows", RFC 3524, April 2003.
[RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network [RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network
Media Services with SIP", RFC 4240, December 2005. Media Services with SIP", RFC 4240, December 2005.
[I-D.ietf-sip-certs] [I-D.ietf-sip-certs]
Jennings, C., Peterson, J., and J. Fischl, "Certificate Jennings, C. and J. Fischl, "Certificate Management
Management Service for The Session Initiation Protocol Service for The Session Initiation Protocol (SIP)",
(SIP)", draft-ietf-sip-certs-05 (work in progress), draft-ietf-sip-certs-06 (work in progress), April 2008.
February 2008.
[I-D.ietf-sip-consent-framework] [RFC5360] Rosenberg, J., Camarillo, G., and D. Willis, "A Framework
Rosenberg, J., Camarillo, G., and D. Willis, "A Framework for Consent-Based Communications in the Session Initiation
for Consent-based Communications in the Session Initiation Protocol (SIP)", RFC 5360, October 2008.
Protocol (SIP)", draft-ietf-sip-consent-framework-04 (work
in progress), January 2008.
[I-D.ietf-sip-saml] [I-D.ietf-sip-saml]
Tschofenig, H., Hodges, J., Peterson, J., Polk, J., and D. Tschofenig, H., Hodges, J., Peterson, J., Polk, J., and D.
Sicker, "SIP SAML Profile and Binding", Sicker, "SIP SAML Profile and Binding",
draft-ietf-sip-saml-03 (work in progress), November 2007. draft-ietf-sip-saml-04 (work in progress), July 2008.
[I-D.ietf-sipping-pending-additions] [RFC5362] Camarillo, G., "The Session Initiation Protocol (SIP)
Camarillo, G., "The Session Initiation Protocol (SIP) Pending Additions Event Package", RFC 5362, October 2008.
Pending Additions Event Package",
draft-ietf-sipping-pending-additions-03 (work in
progress), November 2007.
[RFC4572] Lennox, J., "Connection-Oriented Media Transport over the [RFC4572] Lennox, J., "Connection-Oriented Media Transport over the
Transport Layer Security (TLS) Protocol in the Session Transport Layer Security (TLS) Protocol in the Session
Description Protocol (SDP)", RFC 4572, July 2006. Description Protocol (SDP)", RFC 4572, July 2006.
[I-D.ietf-mmusic-sdp-capability-negotiation] [I-D.ietf-mmusic-sdp-capability-negotiation]
Andreasen, F., "SDP Capability Negotiation", Andreasen, F., "SDP Capability Negotiation",
draft-ietf-mmusic-sdp-capability-negotiation-08 (work in draft-ietf-mmusic-sdp-capability-negotiation-09 (work in
progress), December 2007. progress), July 2008.
[I-D.ietf-mmusic-sdp-media-capabilities] [I-D.ietf-mmusic-sdp-media-capabilities]
Gilman, R., Even, R., and F. Andreasen, "SDP media Gilman, R., Even, R., and F. Andreasen, "SDP media
capabilities Negotiation", capabilities Negotiation",
draft-ietf-mmusic-sdp-media-capabilities-02 (work in draft-ietf-mmusic-sdp-media-capabilities-05 (work in
progress), November 2007. progress), July 2008.
[I-D.ietf-mmusic-file-transfer-mech] [I-D.ietf-mmusic-file-transfer-mech]
Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S., Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S.,
and P. Kyzivat, "A Session Description Protocol (SDP) and P. Kyzivat, "A Session Description Protocol (SDP)
Offer/Answer Mechanism to Enable File Transfer", Offer/Answer Mechanism to Enable File Transfer",
draft-ietf-mmusic-file-transfer-mech-06 (work in draft-ietf-mmusic-file-transfer-mech-08 (work in
progress), December 2007. progress), May 2008.
[I-D.ietf-sip-ice-option-tag] [I-D.ietf-sip-ice-option-tag]
Rosenberg, J., "Indicating Support for Interactive Rosenberg, J., "Indicating Support for Interactive
Connectivity Establishment (ICE) in the Session Connectivity Establishment (ICE) in the Session
Initiation Protocol (SIP)", Initiation Protocol (SIP)",
draft-ietf-sip-ice-option-tag-02 (work in progress), draft-ietf-sip-ice-option-tag-02 (work in progress),
June 2007. June 2007.
[3GPP.24.229] [3GPP.24.229]
3GPP, "Internet Protocol (IP) multimedia call control 3GPP, "Internet Protocol (IP) multimedia call control
protocol based on Session Initiation Protocol (SIP) and protocol based on Session Initiation Protocol (SIP) and
Session Description Protocol (SDP); Stage 3", 3GPP Session Description Protocol (SDP); Stage 3", 3GPP
TS 24.229 5.21.0, December 2007. TS 24.229 5.22.0, September 2008.
[I-D.ietf-sip-record-route-fix] [I-D.ietf-sip-record-route-fix]
Froment, T. and C. Lebel, "Addressing Record-Route issues Froment, T., Lebel, C., and B. Bonnaerens, "Addressing
in the Session Initiation Protocol (SIP)", Record-Route issues in the Session Initiation Protocol
draft-ietf-sip-record-route-fix-01 (work in progress), (SIP)", draft-ietf-sip-record-route-fix-05 (work in
November 2007. progress), October 2008.
[I-D.ietf-sip-subnot-etags] [I-D.ietf-sip-subnot-etags]
Niemi, A., "An Extension to Session Initiation Protocol Niemi, A., "An Extension to Session Initiation Protocol
(SIP) Events for Conditional Event Notification", (SIP) Events for Conditional Event Notification",
draft-ietf-sip-subnot-etags-01 (work in progress), draft-ietf-sip-subnot-etags-03 (work in progress),
August 2007. July 2008.
[I-D.ietf-sip-sips] [I-D.ietf-sip-sips]
Audet, F., "The use of the SIPS URI Scheme in the Session Audet, F., "The use of the SIPS URI Scheme in the Session
Initiation Protocol (SIP)", draft-ietf-sip-sips-07 (work Initiation Protocol (SIP)", draft-ietf-sip-sips-08 (work
in progress), November 2007. in progress), February 2008.
[RFC4896] Surtees, A., West, M., and A. Roach, "Signaling [RFC4896] Surtees, A., West, M., and A. Roach, "Signaling
Compression (SigComp) Corrections and Clarifications", Compression (SigComp) Corrections and Clarifications",
RFC 4896, June 2007. RFC 4896, June 2007.
[I-D.ietf-rohc-sigcomp-sip] [RFC5049] Bormann, C., Liu, Z., Price, R., and G. Camarillo,
Bormann, C., Liu, Z., Price, R., and G. Camarillo,
"Applying Signaling Compression (SigComp) to the Session "Applying Signaling Compression (SigComp) to the Session
Initiation Protocol (SIP)", Initiation Protocol (SIP)", RFC 5049, December 2007.
draft-ietf-rohc-sigcomp-sip-08 (work in progress),
September 2007.
[I-D.ietf-simple-simple] [I-D.ietf-simple-simple]
Rosenberg, J., "SIMPLE made Simple: An Overview of the Rosenberg, J., "SIMPLE made Simple: An Overview of the
IETF Specifications for Instant Messaging and Presence IETF Specifications for Instant Messaging and Presence
using the Session Initiation Protocol (SIP)", using the Session Initiation Protocol (SIP)",
draft-ietf-simple-simple-01 (work in progress), draft-ietf-simple-simple-03 (work in progress), July 2008.
November 2007.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
RFC 4960, September 2007. RFC 4960, September 2007.
[RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E. [RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E.
Carrara, "Key Management Extensions for Session Carrara, "Key Management Extensions for Session
Description Protocol (SDP) and Real Time Streaming Description Protocol (SDP) and Real Time Streaming
Protocol (RTSP)", RFC 4567, July 2006. Protocol (RTSP)", RFC 4567, July 2006.
[RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session [RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session
Description Protocol (SDP) Security Descriptions for Media Description Protocol (SDP) Security Descriptions for Media
Streams", RFC 4568, July 2006. Streams", RFC 4568, July 2006.
[I-D.ietf-sip-dtls-srtp-framework] [I-D.ietf-sip-dtls-srtp-framework]
Fischl, J., Tschofenig, H., and E. Rescorla, "Framework Fischl, J., Tschofenig, H., and E. Rescorla, "Framework
for Establishing an SRTP Security Context using DTLS", for Establishing an SRTP Security Context using DTLS",
draft-ietf-sip-dtls-srtp-framework-00 (work in progress), draft-ietf-sip-dtls-srtp-framework-05 (work in progress),
November 2007. October 2008.
[I-D.ietf-ecrit-framework] [I-D.ietf-ecrit-framework]
Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling using Internet "Framework for Emergency Calling using Internet
Multimedia", draft-ietf-ecrit-framework-04 (work in Multimedia", draft-ietf-ecrit-framework-06 (work in
progress), November 2007. progress), July 2008.
[RFC2833] Schulzrinne, H. and S. Petrack, "RTP Payload for DTMF [RFC2833] Schulzrinne, H. and S. Petrack, "RTP Payload for DTMF
Digits, Telephony Tones and Telephony Signals", RFC 2833, Digits, Telephony Tones and Telephony Signals", RFC 2833,
May 2000. May 2000.
[RFC4458] Jennings, C., Audet, F., and J. Elwell, "Session [RFC4458] Jennings, C., Audet, F., and J. Elwell, "Session
Initiation Protocol (SIP) URIs for Applications such as Initiation Protocol (SIP) URIs for Applications such as
Voicemail and Interactive Voice Response (IVR)", RFC 4458, Voicemail and Interactive Voice Response (IVR)", RFC 4458,
April 2006. April 2006.
skipping to change at page 39, line 26 skipping to change at page 39, line 29
Security", RFC 4347, April 2006. Security", RFC 4347, April 2006.
[I-D.ietf-sipping-v6-transition] [I-D.ietf-sipping-v6-transition]
Camarillo, G., "IPv6 Transition in the Session Initiation Camarillo, G., "IPv6 Transition in the Session Initiation
Protocol (SIP)", draft-ietf-sipping-v6-transition-07 (work Protocol (SIP)", draft-ietf-sipping-v6-transition-07 (work
in progress), August 2007. in progress), August 2007.
[I-D.ietf-sipping-update-pai] [I-D.ietf-sipping-update-pai]
Elwell, J., "Updates to Asserted Identity in the Session Elwell, J., "Updates to Asserted Identity in the Session
Initiation Protocol (SIP)", Initiation Protocol (SIP)",
draft-ietf-sipping-update-pai-00 (work in progress), draft-ietf-sipping-update-pai-07 (work in progress),
February 2008. October 2008.
[RFC3665] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and [RFC3665] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and
K. Summers, "Session Initiation Protocol (SIP) Basic Call K. Summers, "Session Initiation Protocol (SIP) Basic Call
Flow Examples", BCP 75, RFC 3665, December 2003. Flow Examples", BCP 75, RFC 3665, December 2003.
[RFC3666] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and [RFC3666] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and
K. Summers, "Session Initiation Protocol (SIP) Public K. Summers, "Session Initiation Protocol (SIP) Public
Switched Telephone Network (PSTN) Call Flows", BCP 76, Switched Telephone Network (PSTN) Call Flows", BCP 76,
RFC 3666, December 2003. RFC 3666, December 2003.
[I-D.ietf-sip-ipv6-abnf-fix] [I-D.ietf-sip-ipv6-abnf-fix]
Gurbani, V., Carpenter, B., and B. Tate, "Essential Gurbani, V., Carpenter, B., and B. Tate, "Essential
correction for IPv6 ABNF and URI comparison in RFC3261", correction for IPv6 ABNF and URI comparison in RFC3261",
draft-ietf-sip-ipv6-abnf-fix-00 (work in progress), draft-ietf-sip-ipv6-abnf-fix-02 (work in progress),
February 2008. May 2008.
[RFC4497] Elwell, J., Derks, F., Mourot, P., and O. Rousseau, [RFC4497] Elwell, J., Derks, F., Mourot, P., and O. Rousseau,
"Interworking between the Session Initiation Protocol "Interworking between the Session Initiation Protocol
(SIP) and QSIG", BCP 117, RFC 4497, May 2006. (SIP) and QSIG", BCP 117, RFC 4497, May 2006.
[I-D.ietf-sip-ua-privacy] [I-D.ietf-sip-ua-privacy]
Munakata, M., Schubert, S., and T. Ohba, "UA-Driven Munakata, M., Schubert, S., and T. Ohba, "UA-Driven
Privacy Mechanism for SIP", draft-ietf-sip-ua-privacy-00 Privacy Mechanism for SIP", draft-ietf-sip-ua-privacy-03
(work in progress), November 2007. (work in progress), October 2008.
[I-D.ietf-sip-body-handling] [I-D.ietf-sip-body-handling]
Camarillo, G., "Message Body Handling in the Session Camarillo, G., "Message Body Handling in the Session
Initiation Protocol (SIP)", Initiation Protocol (SIP)",
draft-ietf-sip-body-handling-01 (work in progress), draft-ietf-sip-body-handling-04 (work in progress),
January 2008. October 2008.
[I-D.ietf-sip-domain-certs] [I-D.ietf-sip-domain-certs]
Gurbani, V., Lawrence, S., and B. Laboratories, "Domain Gurbani, V., Lawrence, S., and B. Laboratories, "Domain
Certificates in the Session Initiation Protocol (SIP)", Certificates in the Session Initiation Protocol (SIP)",
draft-ietf-sip-domain-certs-00 (work in progress), draft-ietf-sip-domain-certs-02 (work in progress),
November 2007. October 2008.
[I-D.ietf-sipping-gruu-reg-event] [I-D.ietf-sipping-gruu-reg-event]
Kyzivat, P., "Registration Event Package Extension for Kyzivat, P., "Registration Event Package Extension for
Session Initiation Protocol (SIP) Globally Routable User Session Initiation Protocol (SIP) Globally Routable User
Agent URIs (GRUUs)", draft-ietf-sipping-gruu-reg-event-09 Agent URIs (GRUUs)", draft-ietf-sipping-gruu-reg-event-09
(work in progress), July 2007. (work in progress), July 2007.
[I-D.ietf-sip-session-policy-framework] [I-D.ietf-sip-session-policy-framework]
Hilt, V., "A Framework for Session Initiation Protocol Hilt, V., Camarillo, G., and J. Rosenberg, "A Framework
(SIP) Session Policies", for Session Initiation Protocol (SIP) Session Policies",
draft-ietf-sip-session-policy-framework-02 (work in draft-ietf-sip-session-policy-framework-04 (work in
progress), August 2007. progress), August 2008.
[I-D.ietf-mmusic-qos-identification] [I-D.ietf-mmusic-qos-identification]
Polk, J., Dhesikan, S., and G. Camarillo, "Quality of Polk, J., Dhesikan, S., and G. Camarillo, "Quality of
Service (QoS) Mechanism Selection in the Session Service (QoS) Mechanism Selection in the Session
Description Protocol (SDP)", Description Protocol (SDP)",
draft-ietf-mmusic-qos-identification-01 (work in draft-ietf-mmusic-qos-identification-02 (work in
progress), January 2008. progress), October 2008.
[I-D.ietf-sipping-uri-services] [RFC5363] Camarillo, G. and A. Roach, "Framework and Security
Camarillo, G. and A. Roach, "Framework and Security Considerations for Session Initiation Protocol (SIP) URI-
Considerations for Session Initiation Protocol (SIP) List Services", RFC 5363, October 2008.
Uniform Resource Identifier (URI)-List Services",
draft-ietf-sipping-uri-services-07 (work in progress),
November 2007.
[I-D.ietf-sip-connect-reuse] [I-D.ietf-sip-connect-reuse]
Mahy, R., Gurbani, V., and B. Tate, "Connection Reuse in Gurbani, V., Mahy, R., and B. Tate, "Connection Reuse in
the Session Initiation Protocol (SIP)", the Session Initiation Protocol (SIP)",
draft-ietf-sip-connect-reuse-09 (work in progress), draft-ietf-sip-connect-reuse-12 (work in progress),
February 2008. October 2008.
[I-D.ietf-mmusic-sdp-dtls] [I-D.ietf-mmusic-sdp-dtls]
Fischl, J. and H. Tschofenig, "Session Description Fischl, J. and H. Tschofenig, "Session Description
Protocol (SDP) Indicators for Datagram Transport Layer Protocol (SDP) Indicators for Datagram Transport Layer
Security (DTLS)", draft-ietf-mmusic-sdp-dtls-00 (work in Security (DTLS)", draft-ietf-mmusic-sdp-dtls-00 (work in
progress), January 2008. progress), January 2008.
[I-D.ietf-sipping-consent-format] [RFC5361] Camarillo, G., "A Document Format for Requesting Consent",
Camarillo, G., "A Document Format for Requesting Consent", RFC 5361, October 2008.
draft-ietf-sipping-consent-format-05 (work in progress),
November 2007.
[RFC4579] Johnston, A. and O. Levin, "Session Initiation Protocol [RFC4579] Johnston, A. and O. Levin, "Session Initiation Protocol
(SIP) Call Control - Conferencing for User Agents", (SIP) Call Control - Conferencing for User Agents",
BCP 119, RFC 4579, August 2006. BCP 119, RFC 4579, August 2006.
[I-D.ietf-sip-location-conveyance] [I-D.ietf-sip-location-conveyance]
Polk, J. and B. Rosen, "Location Conveyance for the Polk, J. and B. Rosen, "Location Conveyance for the
Session Initiation Protocol", Session Initiation Protocol",
draft-ietf-sip-location-conveyance-09 (work in progress), draft-ietf-sip-location-conveyance-10 (work in progress),
November 2007. September 2008.
[RFC3310] Niemi, A., Arkko, J., and V. Torvinen, "Hypertext Transfer
Protocol (HTTP) Digest Authentication Using Authentication
and Key Agreement (AKA)", RFC 3310, September 2002.
[RFC4169] Torvinen, V., Arkko, J., and M. Naslund, "Hypertext
Transfer Protocol (HTTP) Digest Authentication Using
Authentication and Key Agreement (AKA) Version-2",
RFC 4169, November 2005.
Author's Address Author's Address
Jonathan Rosenberg Jonathan Rosenberg
Cisco Cisco
Edison, NJ Iselin, NJ
US US
Email: jdrosen@cisco.com Email: jdrosen@cisco.com
URI: http://www.jdrosen.net URI: http://www.jdrosen.net
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
 End of changes. 66 change blocks. 
195 lines changed or deleted 192 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/