draft-ietf-sip-hitchhikers-guide-00.txt   draft-ietf-sip-hitchhikers-guide-01.txt 
SIP J. Rosenberg SIP J. Rosenberg
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Expires: December 21, 2006 June 19, 2006 Expires: April 20, 2007 October 17, 2006
A Hitchhikers Guide to the Session Initiation Protocol (SIP) A Hitchhikers Guide to the Session Initiation Protocol (SIP)
draft-ietf-sip-hitchhikers-guide-00 draft-ietf-sip-hitchhikers-guide-01
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 33 skipping to change at page 1, line 33
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 December 21, 2006. This Internet-Draft will expire on April 20, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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
skipping to change at page 2, line 21 skipping to change at page 2, line 21
5. General Purpose Infrastructure Extensions . . . . . . . . . . 8 5. General Purpose Infrastructure Extensions . . . . . . . . . . 8
6. Minor Extensions . . . . . . . . . . . . . . . . . . . . . . . 10 6. Minor Extensions . . . . . . . . . . . . . . . . . . . . . . . 10
7. Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Call Control Primitives . . . . . . . . . . . . . . . . . . . 12 8. Call Control Primitives . . . . . . . . . . . . . . . . . . . 12
9. Event Framework and Packages . . . . . . . . . . . . . . . . . 13 9. Event Framework and Packages . . . . . . . . . . . . . . . . . 13
10. Quality of Service . . . . . . . . . . . . . . . . . . . . . . 15 10. Quality of Service . . . . . . . . . . . . . . . . . . . . . . 15
11. Operations and Management . . . . . . . . . . . . . . . . . . 15 11. Operations and Management . . . . . . . . . . . . . . . . . . 15
12. SIP Compression . . . . . . . . . . . . . . . . . . . . . . . 16 12. SIP Compression . . . . . . . . . . . . . . . . . . . . . . . 16
13. SIP Service URIs . . . . . . . . . . . . . . . . . . . . . . . 16 13. SIP Service URIs . . . . . . . . . . . . . . . . . . . . . . . 16
14. Security Mechanisms . . . . . . . . . . . . . . . . . . . . . 17 14. Security Mechanisms . . . . . . . . . . . . . . . . . . . . . 17
15. Instant Messaging and Presence . . . . . . . . . . . . . . . . 18 15. Instant Messaging and Presence . . . . . . . . . . . . . . . . 19
16. Emergency Services . . . . . . . . . . . . . . . . . . . . . . 18 16. Emergency Services . . . . . . . . . . . . . . . . . . . . . . 19
17. Security Considerations . . . . . . . . . . . . . . . . . . . 19 17. Security Considerations . . . . . . . . . . . . . . . . . . . 19
18. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 18. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
19. Informative References . . . . . . . . . . . . . . . . . . . . 19 19. Informative References . . . . . . . . . . . . . . . . . . . . 20
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 28 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 29
Intellectual Property and Copyright Statements . . . . . . . . . . 29 Intellectual Property and Copyright Statements . . . . . . . . . . 30
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) [1] is the subject of numerous The Session Initiation Protocol (SIP) [1] 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. Don't Panic! [42] This of Request for Comments (RFC) about SIP. Don't Panic! [42] This
specification serves as a guide to the SIP RFC series. It lists the specification serves as a guide to the SIP RFC series. It lists the
specifications under the SIP umbrella. For each specification, a specifications under the SIP umbrella. For each specification, a
paragraph or so description is included that summarizes the purpose paragraph or so description is included that summarizes the purpose
skipping to change at page 4, line 40 skipping to change at page 4, line 40
would be used for almost every registration initiated by a user would be used for almost every registration initiated by a user
agent agent
o For specifications that impact SIP subscriptions, the extension o For specifications that impact SIP subscriptions, the extension
would be used for almost every subscription initiated by a user would be used for almost every subscription initiated by a user
agent agent
In other words, these are not specifications that are used just for In other words, these are not specifications that are used just for
some requests and not others; they are specifications that would some requests and not others; they are specifications that would
apply to each and every request that the extension is relevant for. apply to each and every request that the extension is relevant for.
In the galaxy of SIP, these specifications are like towels [42].
RFC 3261, The Session Initiation Protocol (S): RFC 3261 [1] is the RFC 3261, The Session Initiation Protocol (S): RFC 3261 [1] is the
core SIP protocol itself. RFC 3261 is an update to RFC 2543 [9]. core SIP protocol itself. RFC 3261 is an update to RFC 2543 [9].
It is the president of the galaxy as far as the suite of SIP It is the president of the galaxy [42] as far as the suite of SIP
specifications is concerned. specifications is concerned.
RFC 3263, Locating SIP Servers (S): RFC 3263 [10] provides DNS RFC 3263, Locating SIP Servers (S): RFC 3263 [10] provides DNS
procedures for taking a SIP URI, and determining a SIP server that procedures for taking a SIP URI, and determining a SIP server that
is associated with that SIP URI. RFC 3263 is essential for any is associated with that SIP URI. RFC 3263 is essential for any
implementation using SIP with DNS. RFC 3263 makes use of both DNS implementation using SIP with DNS. RFC 3263 makes use of both DNS
SRV records [11] and NAPTR records [12]. SRV records [11] and NAPTR records [12].
RFC 3264, An Offer/Answer Model with the Session Description Protocol RFC 3264, An Offer/Answer Model with the Session Description Protocol
(S): RFC 3264 [4] defines how the Session Description Protocol (SDP) (S): RFC 3264 [4] defines how the Session Description Protocol (SDP)
[77] is used with SIP to negotiate the parameters of a media [78] is used with SIP to negotiate the parameters of a media
session. It is in widespread usage and an integral part of the session. It is in widespread usage and an integral part of the
behavior of RFC 3261. behavior of RFC 3261.
RFC 3265, SIP-Specific Event Notification (S): RFC 3265 [13] defines RFC 3265, SIP-Specific Event Notification (S): RFC 3265 [13] defines
the SUBSCRIBE and NOTIFY methods. These two methods provide a the SUBSCRIBE and NOTIFY methods. These two methods provide a
general event notification framework for SIP. To actually use the general event notification framework for SIP. To actually use the
framework, extensions need to be defined for specific event framework, extensions need to be defined for specific event
packages. An event package defines a schema for the event data, packages. An event package defines a schema for the event data,
and describes other aspects of event processing specific to that and describes other aspects of event processing specific to that
schema. An RFC 3265 implementation is required when any event schema. An RFC 3265 implementation is required when any event
skipping to change at page 6, line 5 skipping to change at page 6, line 6
like INVITE. It has found use with conferencing (the isfocus like INVITE. It has found use with conferencing (the isfocus
parameter declares that a user agent is a conference server) and parameter declares that a user agent is a conference server) and
with applications like push-to-talk. with applications like push-to-talk.
RFC 4320, Actions Addressing Issues Identified with the Non-INVITE RFC 4320, Actions Addressing Issues Identified with the Non-INVITE
Transaction in SIP (S): RFC 4320 [18] formally updates RFC 3261, and Transaction in SIP (S): RFC 4320 [18] formally updates RFC 3261, and
modifies some of the behaviors associated with non-INVITE modifies some of the behaviors associated with non-INVITE
transactions. These address some problems found in timeout and transactions. These address some problems found in timeout and
failure cases. failure cases.
RFC XXXX, Enhancements for Authenticated Identity Management in SIP RFC 4474, Enhancements for Authenticated Identity Management in SIP
(S): RFC XXXX [19] defines a mechanism for providing a (S): RFC 4474 [19] defines a mechanism for providing a
cryptographically verifiable identity of the calling party in a cryptographically verifiable identity of the calling party in a
SIP request. Also known as "SIP Identity", this mechanism SIP request. Also known as "SIP Identity", this mechanism
provides an alternative to RFC 3325. It has seen little provides an alternative to RFC 3325. It has seen little
deployment so far, but its importance as a key construct for deployment so far, but its importance as a key construct for
almost also anti-spam techniques makes it a core part of the SIP almost also anti-spam techniques makes it a core part of the SIP
specifications. specifications.
RFC XXXX, Obtaining and Using Globally Routable User Agent RFC XXXX, Obtaining and Using Globally Routable User Agent
Identifiers (GRUU) in SIP (S): RFC XXXX [20] defines a mechanism for Identifiers (GRUU) in SIP (S): RFC XXXX [20] defines a mechanism for
directing requests towards a specific UA instance. GRUU is directing requests towards a specific UA instance. GRUU is
essential for features like transfer and provides another piece of essential for features like transfer and provides another piece of
the SIP NAT traversal story. the SIP NAT traversal story.
RFC XXXX, Managing Client Initiated Connections through SIP (S): RFC RFC XXXX, Managing Client Initiated Connections through SIP (S): RFC
XXXX [21], also known as SIP outbound, defines important changes XXXX [21], also known as SIP outbound, defines important changes
to the SIP registration mechanism which enable delivery of SIP to the SIP registration mechanism which enable delivery of SIP
messages towards a UA when it is behind a NAT. This specification messages towards a UA when it is behind a NAT. This specification
is the cornerstone of the SIP NAT traversal strategy. is the cornerstone of the SIP NAT traversal strategy.
RFC XXXX, Session Description Protocol (S): RFC XXXX [77] defines a RFC 4566, Session Description Protocol (S): RFC 4566 [78] defines a
format for representing multimedia sessions. SDP objects are format for representing multimedia sessions. SDP objects are
carried in the body of SIP messages, and based on the offer/answer carried in the body of SIP messages, and based on the offer/answer
model, are used to negotiate the media characteristics of a model, are used to negotiate the media characteristics of a
session between users. session between users.
RFC 3388, Grouping of Media Lines in the Session Description Protocol RFC 3388, Grouping of Media Lines in the Session Description Protocol
(S): RFC 3388 [78] defines a framework for grouping together media (S): RFC 3388 [79] defines a framework for grouping together media
streams in an SDP message. Such a grouping allows relationships streams in an SDP message. Such a grouping allows relationships
between these streams, such as which stream is the audio for a between these streams, such as which stream is the audio for a
particular video feed, to be expressed. particular video feed, to be expressed.
RFC XXXX, Interactive Connectivity Establishment (ICE) (S): RFC XXXX RFC XXXX, Interactive Connectivity Establishment (ICE) (S): RFC XXXX
[5] defines a technique for NAT traversal of media sessions for [5] defines a technique for NAT traversal of media sessions for
protocols that make use of the offer/answer model. This protocols that make use of the offer/answer model. This
specification is the IETF recommended mechanism for NAT traversal specification is the IETF recommended mechanism for NAT traversal
for SIP media streams, and is meant to be used even by endpoints for SIP media streams, and is meant to be used even by endpoints
which are themselves never behind a NAT. which are themselves never behind a NAT.
RFC 3605, Real Time Control Protocol (RTCP) Attribute in the Session RFC 3605, Real Time Control Protocol (RTCP) Attribute in the Session
Description Protocol (SDP) (S): RFC 3605 [79] defines a way to Description Protocol (SDP) (S): RFC 3605 [80] defines a way to
explicitly signal, within an SDP message, the IP address and port explicitly signal, within an SDP message, the IP address and port
for RTCP, rather than using the port+1 rule in the Real Time for RTCP, rather than using the port+1 rule in the Real Time
Transport Protocol (RTP) [3]. It is needed for devices behind NAT Transport Protocol (RTP) [3]. It is needed for devices behind NAT
and used by ICE. and used by ICE.
RFC XXXX, Connected Identity in the Session Initiation Protocol (SIP) RFC XXXX, Connected Identity in the Session Initiation Protocol (SIP)
(S): RFC XXXX [80] defines an extension to SIP that allows a UAC to (S): RFC XXXX [81] defines an extension to SIP that allows a UAC to
determine the identity of the UAS. Due to forwarding and determine the identity of the UAS. Due to forwarding and
retargeting services, this may not be the same as the user that retargeting services, this may not be the same as the user that
the UAC was originally trying to reach. The mechanism works in the UAC was originally trying to reach. The mechanism works in
tandem with the SIP identity specification [19] to provide tandem with the SIP identity specification [19] to provide
signatures over the connected party identity. signatures over the connected party identity.
RFC XXXX, Addressing an Amplification Vulnerability in Forking RFC XXXX, Addressing an Amplification Vulnerability in Forking
Proxies (S): RFC XXXX [81] makes a small normative change to RFC Proxies (S): RFC XXXX [82] makes a small normative change to RFC
3261, requiring loop detection in any proxy that forks a request. 3261, requiring loop detection in any proxy that forks a request.
It addresses a vulnerability uncovered in RFC 3261. It addresses a vulnerability uncovered in RFC 3261.
4. Public Switched Telephone Network (PSTN) Interworking 4. Public Switched Telephone Network (PSTN) Interworking
Numerous extensions and usages of SIP related to interoperability and Numerous extensions and usages of SIP related to interoperability and
communications with or through the PSTN. communications with or through the PSTN.
RFC 2848, The PINT Service Protocol (S): RFC 2848 [22] is one of the RFC 2848, The PINT Service Protocol (S): RFC 2848 [22] is one of the
earliest extensions to SIP. It defines procedures for using SIP earliest extensions to SIP. It defines procedures for using SIP
to invoke services that actually execute on the PSTN. Its main to invoke services that actually execute on the PSTN. Its main
application is for third party call control, allowing an IP host application is for third party call control, allowing an IP host
to set up a call between two PSTN endpoints. PINT has a to set up a call between two PSTN endpoints. PINT has a
relatively narrow focus and has not seen widespread deployment. relatively narrow focus and has not seen widespread deployment.
RFC 3910, The SPIRITS Protocol (S): Continuing the trend of naming RFC 3910, The SPIRITS Protocol (S): Continuing the trend of naming
PSTN related extensions with alcohol references, SPIRITS [23] PSTN related extensions with alcohol references, SPIRITS [23]
defines the inverse of PINT. It allows a switch in the PSTN to defines the inverse of PINT. It allows a switch in the PSTN to
ask an IP element about how to proceed with call waiting. It was ask an IP element about how to proceed with call waiting. It was
developed primarily to support Internet Call Waiting (ICW). developed primarily to support Internet Call Waiting (ICW).
Perhaps the next specification will be called the PGGB. Perhaps the next specification will be called the Pan Galactic
Gargle Blaster [42].
RFC 3372, SIP for Telephones (SIP-T): Context and Architectures RFC 3372, SIP for Telephones (SIP-T): Context and Architectures
(I): SIP-T [24] defines a mechanism for using SIP between pairs of (I): SIP-T [24] defines a mechanism for using SIP between pairs of
PSTN gateways. Its essential idea is to tunnel ISUP signaling PSTN gateways. Its essential idea is to tunnel ISUP signaling
between the gateways in the body of SIP messages. SIP-T motivated between the gateways in the body of SIP messages. SIP-T motivated
the development of INFO [30]. SIP-T has seen widespread the development of INFO [30]. SIP-T has seen widespread
implementation. implementation.
RFC 3398, ISUP to SIP Mapping (S): RFC 3398 [25] defines how to do RFC 3398, ISUP to SIP Mapping (S): RFC 3398 [25] defines how to do
protocol mapping from the SS7 ISDN User Part (ISUP) signaling to protocol mapping from the SS7 ISDN User Part (ISUP) signaling to
skipping to change at page 8, line 22 skipping to change at page 8, line 22
with SIP at some fairly fundamental levels. That said, RFC 3578 with SIP at some fairly fundamental levels. That said, RFC 3578
is mostly harmless and has seen some usage. is mostly harmless and has seen some usage.
RFC 3960, Early Media and Ringtone Generation in SIP (I): RFC 3960 RFC 3960, Early Media and Ringtone Generation in SIP (I): RFC 3960
[27] defines some guidelines for handling early media - the [27] defines some guidelines for handling early media - the
practice of sending media from the called party towards the caller practice of sending media from the called party towards the caller
- prior to acceptance of the call. Early media is generated only - prior to acceptance of the call. Early media is generated only
from the PSTN. from the PSTN.
RFC 3959, Early Session Disposition Type for the Session Initiation RFC 3959, Early Session Disposition Type for the Session Initiation
Protocol (SIP) (S): RFC 3959 [82] defines a new session disposition Protocol (SIP) (S): RFC 3959 [83] defines a new session disposition
type for use with early media. It indicates that the SDP in the type for use with early media. It indicates that the SDP in the
body is for a special early media session. body is for a special early media session.
RFC 3204, MIME Media Types for ISUP and QSIG Objects (S): RFC 3204 RFC 3204, MIME Media Types for ISUP and QSIG Objects (S): RFC 3204
[83] defines MIME objects for representing SS7 signaling messages. [84] defines MIME objects for representing SS7 signaling messages.
These are carried in the body of SIP messages when SIP-T is used. These are carried in the body of SIP messages when SIP-T is used.
5. General Purpose Infrastructure Extensions 5. General Purpose Infrastructure Extensions
These extensions are general purpose enhancements to SIP, SDP and These extensions are general purpose enhancements to SIP, SDP and
MIME that can serve a wide variety of uses. However, they are not as MIME that can serve a wide variety of uses. However, they are not as
widely used or as essential as the core specifications. widely used or as essential as the core specifications.
RFC 3262, Reliability of Provisional Responses in SIP (S): SIP RFC 3262, Reliability of Provisional Responses in SIP (S): SIP
defines two types of responses to a request - final and defines two types of responses to a request - final and
skipping to change at page 9, line 31 skipping to change at page 9, line 31
information when using SIP between a pair of gateways. Though information when using SIP between a pair of gateways. Though
originally conceived for broader use, it only found standardized originally conceived for broader use, it only found standardized
usage with SIP-T [24]. It has been used to support numerous usage with SIP-T [24]. It has been used to support numerous
proprietary and non-interoperable extensions due to its poorly proprietary and non-interoperable extensions due to its poorly
defined scope. defined scope.
RFC 3326, The Reason header field for SIP (S): RFC 3326 [31] defines RFC 3326, The Reason header field for SIP (S): RFC 3326 [31] defines
the Reason header field. It is used in requests, such as BYE, to the Reason header field. It is used in requests, such as BYE, to
indicate the reason that the request is being sent. indicate the reason that the request is being sent.
RFC 3420, Internet Media Type message/sipfrag (S): RFC 3420 [84] RFC 3420, Internet Media Type message/sipfrag (S): RFC 3420 [85]
defines a MIME object that contains a SIP message fragment. Only defines a MIME object that contains a SIP message fragment. Only
certain header fields and parts of the SIP message are present. certain header fields and parts of the SIP message are present.
For example, it is used to report back on the responses received For example, it is used to report back on the responses received
to a request sent as a consequence of a REFER. to a request sent as a consequence of a REFER.
RFC 3608, SIP Extension Header Field for Service Route Discovery RFC 3608, SIP Extension Header Field for Service Route Discovery
During Registration (S): RFC 3608 [32] allows a client to determine, During Registration (S): RFC 3608 [32] allows a client to determine,
from a REGISTER response, a path of proxies to use in requests it from a REGISTER response, a path of proxies to use in requests it
sends outside of a dialog. In many respects, it is the inverse of sends outside of a dialog. In many respects, it is the inverse of
the Path header field, but has seen less usage since default the Path header field, but has seen less usage since default
skipping to change at page 10, line 21 skipping to change at page 10, line 21
Protocol (SCTP). SCTP has seen very limited usage for SIP Protocol (SCTP). SCTP has seen very limited usage for SIP
transport. transport.
RFC 4244, An Extension to SIP for Request History Information RFC 4244, An Extension to SIP for Request History Information
(S): RFC 4244 [37] defines the History-Info header field, which (S): RFC 4244 [37] defines the History-Info header field, which
indicates information on how a call came to be routed to a indicates information on how a call came to be routed to a
particular destination. Its primary application was in support of particular destination. Its primary application was in support of
voicemail services. voicemail services.
RFC 4145, TCP-Based Media Transport in the Session Description RFC 4145, TCP-Based Media Transport in the Session Description
Protocol (SDP) (S): RFC 4145 [85] defines an extension to SDP for Protocol (SDP) (S): RFC 4145 [86] defines an extension to SDP for
setting up TCP-based sessions between user agents. It defines who setting up TCP-based sessions between user agents. It defines who
sets up the connection and how its lifecycle is managed. It has sets up the connection and how its lifecycle is managed. It has
seen relatively little usage due to the small number of media seen relatively little usage due to the small number of media
types to date which use TCP. types to date which use TCP.
RFC 4091, The Alternative Network Address Types (ANAT) Semantics for RFC 4091, The Alternative Network Address Types (ANAT) Semantics for
the Session Description Protocol (SDP) Grouping Framework (S): RFC the Session Description Protocol (SDP) Grouping Framework (S): RFC
4091 [86] defines a mechanism for including both IPv4 and IPv6 4091 [87] defines a mechanism for including both IPv4 and IPv6
addresses for a media session as alternates. addresses for a media session as alternates.
RFC XXXX, TCP Candidates with Interactive Connectivity Establishment RFC XXXX, TCP Candidates with Interactive Connectivity Establishment
(ICE) (S): RFC XXXX [87] specifies the usage of ICE for TCP streams. (ICE) (S): RFC XXXX [88] specifies the usage of ICE for TCP streams.
This allows for selection of RTP-based voice ontop of TCP only This allows for selection of RTP-based voice ontop of TCP only
when NAT or firewalls would prevent UDP-based voice from working. when NAT or firewalls would prevent UDP-based voice from working.
6. Minor Extensions 6. Minor Extensions
These SIP extensions don't fit easily into a single specific use These SIP extensions don't fit easily into a single specific use
case. They have somewhat general applicability, but they solve a case. They have somewhat general applicability, but they solve a
relatively small problem or provide an optimization. relatively small problem or provide an optimization.
RFC 4488, Suppression of the SIP REFER Implicit Subscription (S): RFC RFC 4488, Suppression of the SIP REFER Implicit Subscription (S): RFC
4488 [38] defines an enhancement to REFER. REFER normally creates 4488 [38] defines an enhancement to REFER. REFER normally creates
an implicit subscription to the target of the REFER. This an implicit subscription to the target of the REFER. This
subscription is used to pass back updates on the progress of the subscription is used to pass back updates on the progress of the
referral. This extension allows that implicit subscription to be referral. This extension allows that implicit subscription to be
bypassed as an optimization. bypassed as an optimization.
RFC 4538, Request Authorization through Dialog Identification in SIP RFC 4538, Request Authorization through Dialog Identification in SIP
(S): RFC 4538 [39] provides a mechanism that allows a UAS to (S): RFC 4538 [39] provides a mechanism that allows a UAS to
authorize a request because the requestor proves it knows a dialog authorize a request because the requestor proves it knows a dialog
that is in progress with the UAS. The specification is useful in that is in progress with the UAS. The specification is useful in
conjunction with the SIP application interaction framework [76]. conjunction with the SIP application interaction framework [77].
RFC 4508, Conveying Feature Tags with the REFER Method in SIP RFC 4508, Conveying Feature Tags with the REFER Method in SIP
(S): RFC 4508 [40] defines a mechanism for carrying RFC 3840 (S): RFC 4508 [40] defines a mechanism for carrying RFC 3840
feature tags in REFER. It is useful for informing the target of feature tags in REFER. It is useful for informing the target of
the REFER about the characteristics of the REFER target. the REFER about the characteristics of the REFER target.
RFC XXXX, Requesting Answer Modes for SIP (S): RFC XXXX [41] defines RFC XXXX, Requesting Answer Modes for SIP (S): RFC XXXX [41] defines
an extension for indicating to the called party whether or not the an extension for indicating to the called party whether or not the
phone should ring and/or be answered immediately. This is useful phone should ring and/or be answered immediately. This is useful
for push-to-talk and for diagnostic applications. for push-to-talk and for diagnostic applications.
skipping to change at page 11, line 34 skipping to change at page 11, line 34
This is needed for implementation of the Anonymous Call Rejection This is needed for implementation of the Anonymous Call Rejection
(ACR) feature in SIP. (ACR) feature in SIP.
RFC XXXX, Referring to Multiple Resources in SIP (S): RFC XXXX [44] RFC XXXX, Referring to Multiple Resources in SIP (S): RFC XXXX [44]
allows a UA sending a REFER to ask the recipient of the REFER to allows a UA sending a REFER to ask the recipient of the REFER to
generate multiple SIP requests, not just one. This is useful for generate multiple SIP requests, not just one. This is useful for
conferencing, where a client would like to ask a conference server conferencing, where a client 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): RFC 4483 [88] defines a mechanism for Protocol (SIP) Messages (S): RFC 4483 [89] 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
Description Protocol (SDP) (S): RFC 3890 [89] specifies an SDP Description Protocol (SDP) (S): RFC 3890 [90] specifies an SDP
extension that allows for the description of the bandwidth for a extension that allows for the description of the bandwidth for a
media session that is independent of the underlying transport media session that is independent of the underlying transport
mechanism. It has seen relatively little usage. mechanism. It has seen relatively little usage.
RFC XXXX, Session Description Protocol (SDP) Format for Binary Floor RFC XXXX, Session Description Protocol (SDP) Format for Binary Floor
Control Protocol (BFCP) Streams (S): RFC XXXX [90] defines a Control Protocol (BFCP) Streams (S): RFC XXXX [91] defines a
mechanism in SDP to signal floor control streams that use BFCP. mechanism in SDP to signal floor control streams that use BFCP.
It is used for Push-To-Talk and conference floor control. It is used for Push-To-Talk and conference floor control.
RFC XXXX, Connectivity Preconditions for Session Description Protocol RFC XXXX, Connectivity Preconditions for Session Description Protocol
Media Streams (S): RFC XXXX [92] defines a usage of the precondition Media Streams (S): RFC XXXX [93] defines a usage of the precondition
framework [59]. The connectivity precondition makes sure that the framework [59]. The connectivity precondition makes sure that the
session doesn't get established until actual packet connectivity session doesn't get established until actual packet connectivity
is checked. is checked.
RFC XXXX, The SDP (Session Description Protocol) Content Attribute RFC XXXX, The SDP (Session Description Protocol) Content Attribute
(S): RFC XXXX [93] defines an SDP attribute for describing the (S): RFC XXXX [94] defines an SDP attribute for describing the
purpose of a media stream. Examples include a slide view, the purpose of a media stream. Examples include a slide view, the
speaker, a sign language feed, and so on. speaker, a sign language feed, and so on.
7. Conferencing 7. 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 XXXX, The SDP (Session Description Protocol) Label Attribute RFC 4574, The SDP (Session Description Protocol) Label Attribute
(S): RFC XXXX [94] defines an SDP attribute for providing an opaque (S): RFC 4574 [95] 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
obtain through conferencing mechanisms to media streams to which obtain through conferencing mechanisms to media streams to which
they refer. they refer.
RFC 3911, The SIP Join Header Field (S): RFC 3911 [49] defines the RFC 3911, The SIP Join Header Field (S): RFC 3911 [49] defines the
Join header field. When sent in an INVITE, it causes the Join header field. When sent in an INVITE, it causes the
recipient to join the resulting dialog into a conference with recipient to join the resulting dialog into a conference with
another dialog in progress. another dialog in progress.
RFC XXXX, A SIP Event Package for Conference State (S): RFC XXXX [56] RFC 4575, A SIP Event Package for Conference State (S): RFC 4575 [56]
defines a mechanism for learning about changes in conference defines a mechanism for learning about changes in conference
state, including group membership. state, including group membership.
RFC XXXX, Conference Establishment Using Request-Contained Lists in RFC XXXX, Conference Establishment Using Request-Contained Lists in
SIP (S): RFC XXXX [69] is similar to [67]. However, instead of SIP (S): RFC XXXX [70] is similar to [68]. 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.
8. Call Control Primitives 8. Call Control Primitives
Numerous SIP extensions provide a toolkit of dialog and call Numerous SIP extensions provide a toolkit of dialog and call
management techniques. These techniques have been combined together management techniques. These techniques have been combined together
to build many SIP-based services. to build many SIP-based services.
skipping to change at page 13, line 46 skipping to change at page 13, line 46
introduces the notion of an event package, which is a collection of introduces the notion of an event package, which is a collection of
related state and event information. Much of the state and events in related state and event information. Much of the state and events in
SIP systems have event packages, allowing other entities to learn SIP systems have event packages, allowing other entities to learn
about changes in that state. about changes in that state.
RFC 3903, SIP Extension for Event State Publication (S): RFC 3903 RFC 3903, SIP Extension for Event State Publication (S): RFC 3903
[51] defines the PUBLISH method. It is not an event package, but [51] defines the PUBLISH method. It is not an event package, but
is used by all event packages as a mechanism for pushing an event is used by all event packages as a mechanism for pushing an event
into the system. into the system.
RFC XXXX, A Session Initiation Protocol (SIP) Event Notification RFC 4662, A Session Initiation Protocol (SIP) Event Notification
Extension for Resource Lists (S): RFC XXXX [66] defines an extension Extension for Resource Lists (S): RFC 4662 [67] defines an extension
to RFC 3265 that allows a client to subscribe to a list of to RFC 3265 that allows a client to subscribe to a list of
resources using a single subscription. The server, called a resources using a single subscription. The server, called a
Resource List Server (RLS) will "expand" the subscription and Resource List Server (RLS) will "expand" the subscription and
subscribe to each individual member of the list. It has found subscribe to each individual member of the list. It has found
applicability primarily in the area of presence, but can be used applicability primarily in the area of presence, but can be used
with any event package. with any event package.
RFC 3680, A SIP Event Package for Registrations (S): RFC 3680 [52] RFC 3680, A SIP Event Package for Registrations (S): RFC 3680 [52]
defines an event package for finding out about changes in defines an event package for finding out about changes in
registration state. registration state.
RFC 3842, A Message Summary and Message Waiting Indication Event RFC 3842, A Message Summary and Message Waiting Indication Event
Package for SIP (S): RFC 3842 [64] defines a way for a user agent to Package for SIP (S): RFC 3842 [65] defines a way for a user agent to
find out about voicemails and other messages that are waiting for find out about voicemails and other messages that are waiting for
it. Its primary purpose is to enable the voicemail waiting lamp it. Its primary purpose is to enable the voicemail waiting lamp
on most business telephones. on most business telephones.
RFC 3856, A Presence Event Package for SIP (S): RFC 3856 [53] defines RFC 3856, A Presence Event Package for SIP (S): RFC 3856 [53] defines
an event package for indicating user presence through SIP. an event package for indicating user presence through SIP.
RFC 3857, A Watcher Information Event Template Package for SIP RFC 3857, A Watcher Information Event Template Package for SIP
(S): RFC 3857 [54], also known as winfo, provides a mechanism for (S): RFC 3857 [54], also known as winfo, provides a mechanism for
a user agent to find out what subscriptions are in place for a a user agent to find out what subscriptions are in place for a
particular event package. Its primary usage is with presence, but particular event package. Its primary usage is with presence, but
it can be used with any event package. it can be used with any event package.
RFC 4235, An INVITE Initiated Dialog Event Package for SIP (S): RFC RFC 4235, An INVITE Initiated Dialog Event Package for SIP (S): RFC
4235 [55] defines an event package for learning the state of the 4235 [55] defines an event package for learning the state of the
dialogs in progress at a user agent. dialogs in progress at a user agent.
RFC XXXX, A SIP Event Package for Conference State (S): RFC XXXX [56] RFC 4575, A SIP Event Package for Conference State (S): RFC 4575 [56]
defines a mechanism for learning about changes in conference defines a mechanism for learning about changes in conference
state, including group membership. state, including group membership.
RFC XXXX, A SIP Event Package for Keypress Stimulus (KPML) (S): RFC RFC XXXX, A SIP Event Package for Keypress Stimulus (KPML) (S): RFC
XXXX [57] defines a way for an application in the network to XXXX [57] defines a way for an application in the network to
subscribe to the set of keypresses made on the keypad of a subscribe to the set of keypresses made on the keypad of a
traditional telephone. traditional telephone.
RFC XXXX, SIP Event Package for Voice Quality Reporting (S): RFC XXXX RFC XXXX, SIP Event Package for Voice Quality Reporting (S): RFC XXXX
[58] defines a SIP event package that enables the collection and [58] defines a SIP event package that enables the collection and
reporting of metrics that measure the quality for Voice over reporting of metrics that measure the quality for Voice over
Internet Protocol (VoIP) sessions. Internet Protocol (VoIP) sessions.
RFC XXXX, A Session Initiation Protocol (SIP) Event Package for RFC XXXX, A Session Initiation Protocol (SIP) Event Package for
Session-Specific Session Policies (S): RFC XXXX [95] defines a SIP Session-Specific Session Policies (S): RFC XXXX [96] defines a SIP
event package that allows a proxy to notify a user agent about its event package that allows a proxy to notify a user agent about its
desire for the UA to use certain codecs or generally obey certain desire for the UA to use certain codecs or generally obey certain
media session policies. media session policies.
RFC XXXX, The Session Initiation Protocol (SIP) Pending Additions
Event Package (S): RFC XXXX [103] defines a SIP event package that
allows a UA to learn whether consent has been given for the
addition of an address to a SIP "mailing list". It is used in
conjunction with the SIP framework for consent [101].
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): RFC 3312 RFC 3312, Integration of Resource Management and SIP (S): RFC 3312
[59], updated by RFC 4032 [60] defines a way to make sure that the [59], updated by RFC 4032 [60] defines a way to make sure that the
phone of the called party doesn't ring until a QoS reservation has phone of the called party doesn't ring until a QoS reservation has
been installed in the network. It does so by defining a general been installed in the network. It does so by defining a general
preconditions framework, which defines conditions that must be preconditions framework, which defines conditions that must be
skipping to change at page 15, line 28 skipping to change at page 15, line 34
3313 [61] defines a P-header that provides a mechanism for passing 3313 [61] defines a P-header that provides a mechanism for passing
an authorization token between SIP and a network QoS reservation an authorization token between SIP and a network QoS reservation
protocol like RSVP. Its purpose is to make sure network QoS is protocol like RSVP. Its purpose is to make sure network QoS is
only granted if a client has made a SIP call through the same only granted if a client has made a SIP call through the same
providers network. This specification is sometimes referred to as providers network. This specification is sometimes referred to as
the SIP walled garden specification by the truly paranoid androids the SIP walled garden specification by the truly paranoid androids
in the SIP community. This is because it requires coupling of in the SIP community. This is because it requires coupling of
signaling and the underlying IP network. signaling and the underlying IP network.
RFC 3524, Mapping of Media Streams to Resource Reservation Flows RFC 3524, Mapping of Media Streams to Resource Reservation Flows
(S): RFC 3524 [96] defines a usage of the SDP grouping framework for (S): RFC 3524 [97] defines a usage of the SDP grouping framework for
indicating that a set of media streams should be handled by a indicating that a set of media streams should be handled by a
single resource reservation. single resource reservation.
11. Operations and Management 11. Operations and Management
Several specifications have been defined to support operations and Several specifications have been defined to support operations and
management of SIP systems. These include mechanisms for management of SIP systems. These include mechanisms for
configuration and network diagnostics. configuration and network diagnostics.
RFC XXXX, Diagnostic Responses for SIP Hop Limit Errors (S): RFC XXXX RFC XXXX, Diagnostic Responses for SIP Hop Limit Errors (S): RFC XXXX
[97] defines a mechanism for including diagnostic information in a [98] defines a mechanism for including diagnostic information in a
483 response. This response is sent when the hop-count of a SIP 483 response. This response is sent when the hop-count of a SIP
request was exceeded. request was exceeded.
RFC XXXX, A Framework for SIP User Agent Profile Delivery (S): RFC RFC XXXX, A Framework for SIP User Agent Profile Delivery (S): RFC
XXXX [62] defines a mechanism that allows a SIP user agent to XXXX [62] defines a mechanism that allows a SIP user agent to
bootstrap its configuration from the network, and receive updates bootstrap its configuration from the network, and receive updates
to its configuration should it change. This is considered an to its configuration should it change. This is considered an
essential piece of deploying a usable SIP network. essential piece of deploying a usable SIP network.
RFC XXXX, Extensions to the Session Initiation Protocol (SIP) User
Agent Profile Delivery Change Notification Event Package for the
Extensible Markup Language Language Configuration Access Protocol
(XCAP) (S): RFC XXXX [63] defines an extension to [62] for learning
about changes in documents managed by XCAP.
RFC XXXX, SIP Event Package for Voice Quality Reporting (S): RFC XXXX RFC XXXX, SIP Event Package for Voice Quality Reporting (S): RFC XXXX
[58] defines a SIP event package that enables the collection and [58] defines a SIP event package that enables the collection and
reporting of metrics that measure the quality for Voice over reporting of metrics that measure the quality for Voice over
Internet Protocol (VoIP) sessions. Internet Protocol (VoIP) sessions.
12. SIP Compression 12. SIP Compression
Sigcomp [6] was defined to allow compression of SIP messages over low Sigcomp [6] was defined to allow compression of SIP messages over low
bandwidth links. Sigcomp is not formally part of SIP. However, bandwidth links. Sigcomp is not formally part of SIP. However,
usage of Sigcomp with SIP has required extensions to SIP. usage of Sigcomp with SIP has required extensions to SIP.
RFC 3486, Compressing SIP (S): RFC 3486 [63] defines a SIP URI RFC 3486, Compressing SIP (S): RFC 3486 [64] defines a SIP URI
parameter that can be used to indicate that a SIP server supports parameter that can be used to indicate that a SIP server supports
Sigcomp. Sigcomp.
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 RFC 3087, Control of Service Context using Request URI (I): RFC 3087
[65] introduced the context of using Request URIs, encoded [66] introduced the context of using Request URIs, encoded
appropriately, to invoke services. appropriately, to invoke services.
RFC XXXX, A SIP Event Notification Extension for Resource Lists RFC 4662, A SIP Event Notification Extension for Resource Lists
(S): RFC XXXX [66] defines a resource called a Resource List (S): RFC 4662 [67] defines a resource called a Resource List
Server. A client can send a subscribe to this server. The server Server. A client can send a subscribe to this server. The server
will generate a series of subscriptions, and compile the resulting will 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.
RFC XXXX, Subscriptions To Request-Contained Resource Lists in SIP RFC XXXX, Subscriptions To Request-Contained Resource Lists in SIP
(S): RFC XXXX [67] allows a client to subscribe to a resource called (S): RFC XXXX [68] allows a client to subscribe to a resource called
a Resource List Server. This server will generate a series of a Resource List Server. This server will generate a series of
subscriptions, and compile the resulting information and send it subscriptions, and compile the resulting information and send it
back to the subscriber. For this specification, the list of back to the subscriber. For this specification, the list of
things to subscribe to is in the body of the SUBSCRIBE request. things to subscribe to is in the body of the SUBSCRIBE request.
RFC XXXX, Multiple-Recipient MESSAGE Requests in SIP (S): RFC XXXX RFC XXXX, Multiple-Recipient MESSAGE Requests in SIP (S): RFC XXXX
[68] is similar to [67]. However, instead of subscribing to the [69] is similar to [68]. However, instead of subscribing to the
resource, a MESSAGE request is sent to the resource, and it will resource, a MESSAGE request is sent to the resource, and it will
send a copy to each recipient. send a copy to each recipient.
RFC XXXX, Conference Establishment Using Request-Contained Lists in RFC XXXX, Conference Establishment Using Request-Contained Lists in
SIP (S): RFC XXXX [69] is similar to [67]. However, instead of SIP (S): RFC XXXX [70] is similar to [68]. 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.
RFC 4240, Basic Network Media Services with SIP (I): RFC 4240 [98] RFC 4240, Basic Network Media Services with SIP (I): RFC 4240 [99]
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.
14. Security Mechanisms 14. Security Mechanisms
Several extensions provide additional security features to SIP. Several extensions provide additional security features to SIP.
RFC 3853, S/MIME AES Requirement for SIP (S): RFC 3853 [70] is a RFC 3853, S/MIME AES Requirement for SIP (S): RFC 3853 [71] is a
brief specification that updates the cryptography mechanisms used brief specification that updates the cryptography mechanisms used
in SIP S/MIME. However, SIP S/MIME has seen very little in SIP S/MIME. However, SIP S/MIME has seen very little
deployment. deployment.
RFC XXXX, Certificate Management Service for The Session Initiation RFC XXXX, Certificate Management Service for The Session Initiation
Protocol (SIP) (S): RFC XXXX [99] defines a certificate service for Protocol (SIP) (S): RFC XXXX [100] defines a certificate service for
SIP whose purpose is to facilitate the deployment of S/MIME. The SIP whose purpose is to facilitate the deployment of S/MIME. The
certificate service allows clients to store and retrieve their own certificate service allows clients to store and retrieve their own
certificates, in addition to obtaining the certificates for other certificates, in addition to obtaining the certificates for other
users. users.
RFC 3893, Session Initiation Protocol (SIP) Authenticated Identity RFC 3893, Session Initiation Protocol (SIP) Authenticated Identity
Body (AIB) Format (S): RFC 3893 [7] defines a SIP message fragment Body (AIB) Format (S): RFC 3893 [7] defines a SIP message fragment
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 [19], and over a request. It was an early predecessor to [19], and
consequently AIB has seen no deployment. consequently AIB has seen no deployment.
RFC 3329, Security Mechanism Agreement for SIP (S): RFC 3329 [71] RFC XXXX, SIP SAML Profile and Binding (S): RFC XXXX [102] defines
the usage of the Security Assertion Markup Language (SAML) within
SIP, and describes how to use it in conjunction with SIP identity
[19] to provide authenticated assertions about a users role or
attributes.
RFC XXXX, A Framework for Consent-Based Communications in the Session
Initiation Protocol (SIP) (S): RFC XXX [101] defines several
extensions to SIP, including the Trigger-Consent and Permission-
Missing header fields. These header fields, in addition to the
other procedures defined in the document, define a way to manage
membership on "SIP mailing lists" used for instant messaging or
conferencing. In particular, it helps avoid the problem of using
such amplification services for the purposes of an attack on the
network, by making sure a user authorizes the addition of their
address onto such a service.
RFC XXXX, The Session Initiation Protocol (SIP) Pending Additions
Event Package (S): RFC XXXX [103] defines a SIP event package that
allows a UA to learn whether consent has been given for the
addition of an address to a SIP "mailing list". It is used in
conjunction with the SIP framework for consent [101].
RFC 3329, Security Mechanism Agreement for SIP (S): RFC 3329 [72]
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, and is needed only when there are a multiplicity of suite, and is needed only when there are a multiplicity of
security mechanisms deployed at a particular server. In practice, security mechanisms deployed at a particular server. In practice,
this has not been the case. this has not been the case.
RFC XXXX, End-to-Middle Security in SIP (S): RFC XXXX [72] defines RFC XXXX, End-to-Middle Security in SIP (S): RFC XXXX [73] defines
mechanisms for encrypting content from user agents to specific mechanisms for encrypting content from user agents to specific
network intermediaries. network intermediaries.
RFC XXXX, Connection-Oriented Media Transport over the Transport RFC 4572, Connection-Oriented Media Transport over the Transport
Layer Security (TLS) Protocol in the Session Description Protocol Layer Security (TLS) Protocol in the Session Description Protocol
(SDP) (S): RFC XXXX [100] specifies a mechanism for signaling TLS- (SDP) (S): RFC 4572 [104] specifies a mechanism for signaling TLS-
based media streams between endpoints. It expands the TCP-based based media streams between endpoints. It expands the TCP-based
media signaling parameters defined in [85] to include fingerprint media signaling parameters defined in [86] 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 XXXX, Security Preconditions for Session Description Protocol RFC XXXX, Security Preconditions for Session Description Protocol
Media Streams (S): RFC XXXX [91] defines a precondition for use with Media Streams (S): RFC XXXX [92] defines a precondition for use with
the preconditions framework [59]. The security precondition the preconditions framework [59]. 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.
15. Instant Messaging and Presence 15. Instant Messaging and Presence
SIP provides extensions for instant messaging and presence. SIP provides extensions for instant messaging and presence.
RFC 3428, SIP Extension for Instant Messaging (S): RFC 3428 [73] RFC 3428, SIP Extension for Instant Messaging (S): RFC 3428 [74]
defines the MESSAGE method, used for sending a page mode instant defines the MESSAGE method, used for sending a page mode instant
message. message.
RFC 3856, A Presence Event Package for SIP (S): RFC 3856 [53] defines RFC 3856, A Presence Event Package for SIP (S): RFC 3856 [53] defines
an event package for indicating user presence through SIP. an event package for indicating user presence through SIP.
RFC 3857, A Watcher Information Event Template Package for SIP RFC 3857, A Watcher Information Event Template Package for SIP
(S): RFC 3857 [54], also known as winfo, provides a mechanism for (S): RFC 3857 [54], also known as winfo, provides a mechanism for
a user agent to find out what subscriptions are in place for a a user agent to find out what subscriptions are in place for a
particular event package. Its primary usage is with presence, but particular event package. Its primary usage is with presence, but
it can be used with any event package. it can be used with any event package.
16. Emergency Services 16. Emergency Services
Emergency services here covers both emergency calling (for example, Emergency services here covers both emergency calling (for example,
911 in the United States), and pre-emption services, which allow 911 in the United States), and pre-emption services, which allow
authorized individuals to gain access to network resources in time of authorized individuals to gain access to network resources in time of
emergency. emergency.
RFC 4411, Extending the SIP Reason Header for Preemption Events RFC 4411, Extending the SIP Reason Header for Preemption Events
(S): RFC 4411 [74] defines an extension to the Reason header, (S): RFC 4411 [75] defines an extension to the Reason header,
allowing a UA to know that its dialog was torn down because a allowing a UA to know that its dialog was torn down because a
higher priority session came through. higher priority session came through.
RFC 4412, Communications Resource Priority for SIP (S): RFC 4412 [75] RFC 4412, Communications Resource Priority for SIP (S): RFC 4412 [76]
defines a new header field, Resource-Priority, that allows a defines a new header field, Resource-Priority, that allows a
session to get priority treatment from the network. session to get priority treatment from the network.
17. Security Considerations 17. Security Considerations
This specification is an overview of existing specifications, and This specification is an overview of existing specifications, and
does not introduce any security considerations on its own. does not introduce any security considerations on its own.
18. IANA Considerations 18. IANA Considerations
skipping to change at page 19, line 36 skipping to change at page 20, line 23
[3] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, [3] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
"RTP: A Transport Protocol for Real-Time Applications", "RTP: A Transport Protocol for Real-Time Applications",
RFC 3550, July 2003. RFC 3550, July 2003.
[4] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with [4] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
Session Description Protocol (SDP)", RFC 3264, June 2002. Session Description Protocol (SDP)", RFC 3264, June 2002.
[5] Rosenberg, J., "Interactive Connectivity Establishment (ICE): [5] Rosenberg, J., "Interactive Connectivity Establishment (ICE):
A Methodology for Network Address Translator (NAT) Traversal A Methodology for Network Address Translator (NAT) Traversal
for Offer/Answer Protocols", draft-ietf-mmusic-ice-08 (work in for Offer/Answer Protocols", draft-ietf-mmusic-ice-11 (work in
progress), March 2006. progress), October 2006.
[6] Price, R., Bormann, C., Christoffersson, J., Hannu, H., Liu, [6] Price, R., Bormann, C., Christoffersson, J., Hannu, H., Liu,
Z., and J. Rosenberg, "Signaling Compression (SigComp)", Z., and J. Rosenberg, "Signaling Compression (SigComp)",
RFC 3320, January 2003. RFC 3320, January 2003.
[7] Peterson, J., "Session Initiation Protocol (SIP) Authenticated [7] Peterson, J., "Session Initiation Protocol (SIP) Authenticated
Identity Body (AIB) Format", RFC 3893, September 2004. Identity Body (AIB) Format", RFC 3893, September 2004.
[8] Mankin, A., Bradner, S., Mahy, R., Willis, D., Ott, J., and B. [8] Mankin, A., Bradner, S., Mahy, R., Willis, D., Ott, J., and B.
Rosen, "Change Process for the Session Initiation Protocol Rosen, "Change Process for the Session Initiation Protocol
skipping to change at page 20, line 39 skipping to change at page 21, line 25
[17] Rosenberg, J. and H. Schulzrinne, "An Extension to the Session [17] Rosenberg, J. and H. Schulzrinne, "An Extension to the Session
Initiation Protocol (SIP) for Symmetric Response Routing", Initiation Protocol (SIP) for Symmetric Response Routing",
RFC 3581, August 2003. RFC 3581, August 2003.
[18] Sparks, R., "Actions Addressing Identified Issues with the [18] Sparks, R., "Actions Addressing Identified Issues with the
Session Initiation Protocol's (SIP) Non-INVITE Transaction", Session Initiation Protocol's (SIP) Non-INVITE Transaction",
RFC 4320, January 2006. RFC 4320, January 2006.
[19] Peterson, J. and C. Jennings, "Enhancements for Authenticated [19] Peterson, J. and C. Jennings, "Enhancements for Authenticated
Identity Management in the Session Initiation Protocol Identity Management in the Session Initiation Protocol (SIP)",
(SIP)", draft-ietf-sip-identity-06 (work in progress), RFC 4474, August 2006.
October 2005.
[20] Rosenberg, J., "Obtaining and Using Globally Routable User [20] 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-07 (work in progress), May 2006. (SIP)", draft-ietf-sip-gruu-10 (work in progress),
August 2006.
[21] Jennings, C. and R. Mahy, "Managing Client Initiated [21] 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-03 (work in progress), March 2006. draft-ietf-sip-outbound-04 (work in progress), June 2006.
[22] Petrack, S. and L. Conroy, "The PINT Service Protocol: [22] 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.
[23] Gurbani, V., Brusilovsky, A., Faynberg, I., Gato, J., Lu, H., [23] Gurbani, V., Brusilovsky, A., Faynberg, I., Gato, J., Lu, H.,
and M. Unmehopa, "The SPIRITS (Services in PSTN requesting and M. Unmehopa, "The SPIRITS (Services in PSTN requesting
Internet Services) Protocol", RFC 3910, October 2004. Internet Services) Protocol", RFC 3910, October 2004.
[24] Vemuri, A. and J. Peterson, "Session Initiation Protocol for [24] Vemuri, A. and J. Peterson, "Session Initiation Protocol for
Telephones (SIP-T): Context and Architectures", BCP 63, Telephones (SIP-T): Context and Architectures", BCP 63,
RFC 3372, September 2002. RFC 3372, September 2002.
skipping to change at page 22, line 36 skipping to change at page 23, line 21
May 2006. May 2006.
[41] Willis, D. and A. Allen, "Requesting Answering Modes for the [41] Willis, D. and A. Allen, "Requesting Answering Modes for the
Session Initiation Protocol (SIP)", Session Initiation Protocol (SIP)",
draft-ietf-sip-answermode-01 (work in progress), May 2006. draft-ietf-sip-answermode-01 (work in progress), May 2006.
[42] Adams, D., "The Hitchhikers Guide to the Galaxy", [42] Adams, D., "The Hitchhikers Guide to the Galaxy",
September 1979. September 1979.
[43] Rosenberg, J., "Rejecting Anonymous Requests in the Session [43] Rosenberg, J., "Rejecting Anonymous Requests in the Session
Initiation Protocol (SIP)", draft-ietf-sip-acr-code-00 (work Initiation Protocol (SIP)", draft-ietf-sip-acr-code-03 (work
in progress), January 2006. in progress), October 2006.
[44] Camarillo, G., "Refering to Multiple Resources in the Session [44] Camarillo, G., "Refering to Multiple Resources in the Session
Initiation Protocol (SIP)", Initiation Protocol (SIP)", draft-ietf-sip-multiple-refer-00
draft-ietf-sipping-multiple-refer-05 (work in progress), (work in progress), September 2006.
May 2006.
[45] Sparks, R., "The Session Initiation Protocol (SIP) Refer [45] Sparks, R., "The Session Initiation Protocol (SIP) Refer
Method", RFC 3515, April 2003. Method", RFC 3515, April 2003.
[46] Rosenberg, J., Peterson, J., Schulzrinne, H., and G. [46] 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.
[47] Mahy, R., Biggs, B., and R. Dean, "The Session Initiation [47] Mahy, R., Biggs, B., and R. Dean, "The Session Initiation
skipping to change at page 23, line 36 skipping to change at page 24, line 19
Initiation Protocol (SIP)", RFC 3856, August 2004. Initiation Protocol (SIP)", RFC 3856, August 2004.
[54] Rosenberg, J., "A Watcher Information Event Template-Package [54] Rosenberg, J., "A Watcher Information Event Template-Package
for the Session Initiation Protocol (SIP)", RFC 3857, for the Session Initiation Protocol (SIP)", RFC 3857,
August 2004. August 2004.
[55] Santesson, S. and R. Housley, "Internet X.509 Public Key [55] Santesson, S. and R. Housley, "Internet X.509 Public Key
Infrastructure Authority Information Access Certificate Infrastructure Authority Information Access Certificate
Revocation List (CRL) Extension", RFC 4325, December 2005. Revocation List (CRL) Extension", RFC 4325, December 2005.
[56] Rosenberg, J., "A Session Initiation Protocol (SIP) Event [56] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
Package for Conference State", Initiation Protocol (SIP) Event Package for Conference State",
draft-ietf-sipping-conference-package-12 (work in progress), RFC 4575, August 2006.
July 2005.
[57] Burger, E., "A Session Initiation Protocol (SIP) Event Package [57] Dolly, M. and E. Burger, "A Session Initiation Protocol (SIP)
for Key Press Stimulus (KPML)", draft-ietf-sipping-kpml-07 Event Package for Key Press Stimulus (KPML)",
(work in progress), December 2004. draft-ietf-sipping-kpml-08 (work in progress), July 2006.
[58] Pendleton, A., "Session Initiation Protocol Package for Voice [58] Pendleton, A., "Session Initiation Protocol Package for Voice
Quality Reporting Event", draft-ietf-sipping-rtcp-summary-01 Quality Reporting Event", draft-ietf-sipping-rtcp-summary-01
(work in progress), February 2006. (work in progress), February 2006.
[59] Camarillo, G., Marshall, W., and J. Rosenberg, "Integration of [59] Camarillo, G., Marshall, W., and J. Rosenberg, "Integration of
Resource Management and Session Initiation Protocol (SIP)", Resource Management and Session Initiation Protocol (SIP)",
RFC 3312, October 2002. RFC 3312, October 2002.
[60] Camarillo, G. and P. Kyzivat, "Update to the Session [60] Camarillo, G. and P. Kyzivat, "Update to the Session
Initiation Protocol (SIP) Preconditions Framework", RFC 4032, Initiation Protocol (SIP) Preconditions Framework", RFC 4032,
March 2005. March 2005.
[61] Marshall, W., "Private Session Initiation Protocol (SIP) [61] Marshall, W., "Private Session Initiation Protocol (SIP)
Extensions for Media Authorization", RFC 3313, January 2003. Extensions for Media Authorization", RFC 3313, January 2003.
[62] Petrie, D., "A Framework for Session Initiation Protocol User [62] Petrie, D., "A Framework for Session Initiation Protocol User
Agent Profile Delivery", Agent Profile Delivery",
draft-ietf-sipping-config-framework-08 (work in progress), draft-ietf-sipping-config-framework-09 (work in progress),
March 2006. October 2006.
[63] Camarillo, G., "Compressing the Session Initiation Protocol [63] Petrie, D., "Extensions to the Session Initiation Protocol
(SIP) User Agent Profile Delivery Change Notification Event
Package for the Extensible Markup Language Language
Configuration Access Protocol (XCAP)",
draft-ietf-sip-xcap-config-00 (work in progress),
October 2006.
[64] Camarillo, G., "Compressing the Session Initiation Protocol
(SIP)", RFC 3486, February 2003. (SIP)", RFC 3486, February 2003.
[64] Foster, M., McGarry, T., and J. Yu, "Number Portability in the [65] Foster, M., McGarry, T., and J. Yu, "Number Portability in the
Global Switched Telephone Network (GSTN): An Overview", Global Switched Telephone Network (GSTN): An Overview",
RFC 3482, February 2003. RFC 3482, February 2003.
[65] Campbell, B. and R. Sparks, "Control of Service Context using [66] Campbell, B. and R. Sparks, "Control of Service Context using
SIP Request-URI", RFC 3087, April 2001. SIP Request-URI", RFC 3087, April 2001.
[66] Roach, A., Rosenberg, J., and B. Campbell, "A Session [67] 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", draft-ietf-simple-event-list-07 (work in Resource Lists", RFC 4662, August 2006.
progress), January 2005.
[67] Camarillo, G., "Subscriptions to Request-Contained Resource [68] Camarillo, G., "Subscriptions to Request-Contained Resource
Lists in the Session Initiation Protocol (SIP)", Lists in the Session Initiation Protocol (SIP)",
draft-ietf-sipping-uri-list-subscribe-05 (work in progress), draft-ietf-sip-uri-list-subscribe-00 (work in progress),
May 2006. September 2006.
[68] Garcia-Martin, M. and G. Camarillo, "Multiple-Recipient [69] Garcia-Martin, M. and G. Camarillo, "Multiple-Recipient
MESSAGE Requests in the Session Initiation Protocol (SIP)", MESSAGE Requests in the Session Initiation Protocol (SIP)",
draft-ietf-sipping-uri-list-message-07 (work in progress), draft-ietf-sip-uri-list-message-00 (work in progress),
February 2006. September 2006.
[69] Camarillo, G. and A. Johnston, "Conference Establishment Using [70] Camarillo, G. and A. Johnston, "Conference Establishment Using
Request-Contained Lists in the Session Initiation Protocol Request-Contained Lists in the Session Initiation Protocol
(SIP)", draft-ietf-sipping-uri-list-conferencing-05 (work in (SIP)", draft-ietf-sip-uri-list-conferencing-00 (work in
progress), February 2006. progress), September 2006.
[70] Peterson, J., "S/MIME Advanced Encryption Standard (AES) [71] 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.
[71] Arkko, J., Torvinen, V., Camarillo, G., Niemi, A., and T. [72] 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.
[72] Ono, K. and S. Tachimoto, "End-to-middle Security in the [73] Ono, K. and S. Tachimoto, "End-to-middle Security in the
Session Initiation Protocol (SIP)", draft-ietf-sip-e2m-sec-01 Session Initiation Protocol (SIP)", draft-ietf-sip-e2m-sec-03
(work in progress), October 2005. (work in progress), September 2006.
[73] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C., and [74] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C., and
D. Gurle, "Session Initiation Protocol (SIP) Extension for D. Gurle, "Session Initiation Protocol (SIP) Extension for
Instant Messaging", RFC 3428, December 2002. Instant Messaging", RFC 3428, December 2002.
[74] Polk, J., "Extending the Session Initiation Protocol (SIP) [75] Polk, J., "Extending the Session Initiation Protocol (SIP)
Reason Header for Preemption Events", RFC 4411, February 2006. Reason Header for Preemption Events", RFC 4411, February 2006.
[75] Schulzrinne, H. and J. Polk, "Communications Resource Priority [76] Schulzrinne, H. and J. Polk, "Communications Resource Priority
for the Session Initiation Protocol (SIP)", RFC 4412, for the Session Initiation Protocol (SIP)", RFC 4412,
February 2006. February 2006.
[76] Rosenberg, J., "A Framework for Application Interaction in the [77] Rosenberg, J., "A Framework for Application Interaction in the
Session Initiation Protocol (SIP)", Session Initiation Protocol (SIP)",
draft-ietf-sipping-app-interaction-framework-05 (work in draft-ietf-sipping-app-interaction-framework-05 (work in
progress), July 2005. progress), July 2005.
[77] Handley, M., "SDP: Session Description Protocol", [78] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
draft-ietf-mmusic-sdp-new-26 (work in progress), January 2006. Description Protocol", RFC 4566, July 2006.
[78] Camarillo, G., Eriksson, G., Holler, J., and H. Schulzrinne, [79] Camarillo, G., Eriksson, G., Holler, J., and H. Schulzrinne,
"Grouping of Media Lines in the Session Description Protocol "Grouping of Media Lines in the Session Description Protocol
(SDP)", RFC 3388, December 2002. (SDP)", RFC 3388, December 2002.
[79] Huitema, C., "Real Time Control Protocol (RTCP) attribute in [80] Huitema, C., "Real Time Control Protocol (RTCP) attribute in
Session Description Protocol (SDP)", RFC 3605, October 2003. Session Description Protocol (SDP)", RFC 3605, October 2003.
[80] Elwell, J., "Connected Identity in the Session Initiation [81] Elwell, J., "Connected Identity in the Session Initiation
Protocol (SIP)", draft-ietf-sip-connected-identity-00 (work in Protocol (SIP)", draft-ietf-sip-connected-identity-02 (work in
progress), April 2006. progress), October 2006.
[81] Sparks, R., "Addressing an Amplification Vulnerability in [82] Sparks, R., "Addressing an Amplification Vulnerability in
Forking Proxies", draft-ietf-sip-fork-loop-fix-01 (work in Session Initiation Protocol (SIP) Forking Proxies",
progress), April 2006. draft-ietf-sip-fork-loop-fix-03 (work in progress),
September 2006.
[82] Camarillo, G., "The Early Session Disposition Type for the [83] Camarillo, G., "The Early Session Disposition Type for the
Session Initiation Protocol (SIP)", RFC 3959, December 2004. Session Initiation Protocol (SIP)", RFC 3959, December 2004.
[83] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, F., [84] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, F.,
Watson, M., and M. Zonoun, "MIME media types for ISUP and QSIG Watson, M., and M. Zonoun, "MIME media types for ISUP and QSIG
Objects", RFC 3204, December 2001. Objects", RFC 3204, December 2001.
[84] Sparks, R., "Internet Media Type message/sipfrag", RFC 3420, [85] Sparks, R., "Internet Media Type message/sipfrag", RFC 3420,
November 2002. November 2002.
[85] Yon, D. and G. Camarillo, "TCP-Based Media Transport in the [86] Yon, D. and G. Camarillo, "TCP-Based Media Transport in the
Session Description Protocol (SDP)", RFC 4145, September 2005. Session Description Protocol (SDP)", RFC 4145, September 2005.
[86] Camarillo, G. and J. Rosenberg, "The Alternative Network [87] 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.
[87] Rosenberg, J., "TCP Candidates with Interactive Connectivity [88] Rosenberg, J., "TCP Candidates with Interactive Connectivity
Establishment (ICE)", draft-ietf-mmusic-ice-tcp-00 (work in Establishment (ICE)", draft-ietf-mmusic-ice-tcp-01 (work in
progress), March 2006. progress), June 2006.
[88] Burger, E., "A Mechanism for Content Indirection in Session [89] Burger, E., "A Mechanism for Content Indirection in Session
Initiation Protocol (SIP) Messages", RFC 4483, May 2006. Initiation Protocol (SIP) Messages", RFC 4483, May 2006.
[89] Westerlund, M., "A Transport Independent Bandwidth Modifier [90] Westerlund, M., "A Transport Independent Bandwidth Modifier
for the Session Description Protocol (SDP)", RFC 3890, for the Session Description Protocol (SDP)", RFC 3890,
September 2004. September 2004.
[90] Camarillo, G., "Session Description Protocol (SDP) Format for [91] Camarillo, G., "Session Description Protocol (SDP) Format for
Binary Floor Control Protocol (BFCP) Streams", Binary Floor Control Protocol (BFCP) Streams",
draft-ietf-mmusic-sdp-bfcp-03 (work in progress), draft-ietf-mmusic-sdp-bfcp-03 (work in progress),
December 2005. December 2005.
[91] Andreasen, F. and D. Wing, "Security Preconditions for Session [92] Andreasen, F. and D. Wing, "Security Preconditions for Session
Description Protocol Media Streams", Description Protocol (SDP) Media Streams",
draft-ietf-mmusic-securityprecondition-01 (work in progress), draft-ietf-mmusic-securityprecondition-02 (work in progress),
October 2005. June 2006.
[92] Andreasen, F., "Connectivity Preconditions for Session [93] Andreasen, F., "Connectivity Preconditions for Session
Description Protocol Media Streams", Description Protocol Media Streams",
draft-ietf-mmusic-connectivity-precon-02 (work in progress), draft-ietf-mmusic-connectivity-precon-02 (work in progress),
June 2006. June 2006.
[93] Hautakorpi, J. and G. Camarillo, "The SDP (Session Description [94] Hautakorpi, J. and G. Camarillo, "The SDP (Session Description
Protocol) Content Attribute", Protocol) Content Attribute",
draft-ietf-mmusic-sdp-media-content-03 (work in progress), draft-ietf-mmusic-sdp-media-content-06 (work in progress),
April 2006. September 2006.
[94] Levin, O. and G. Camarillo, "The SDP (Session Description [95] Levin, O. and G. Camarillo, "The Session Description Protocol
Protocol) Label Attribute", (SDP) Label Attribute", RFC 4574, August 2006.
draft-ietf-mmusic-sdp-media-label-01 (work in progress),
January 2005.
[95] Hilt, V. and G. Camarillo, "A Session Initiation Protocol [96] Hilt, V. and G. Camarillo, "A Session Initiation Protocol
(SIP) Event Package for Session-Specific Session Policies.", (SIP) Event Package for Session-Specific Session Policies",
draft-ietf-sipping-policy-package-00 (work in progress), draft-ietf-sipping-policy-package-01 (work in progress),
April 2006. June 2006.
[96] Camarillo, G. and A. Monrad, "Mapping of Media Streams to [97] Camarillo, G. and A. Monrad, "Mapping of Media Streams to
Resource Reservation Flows", RFC 3524, April 2003. Resource Reservation Flows", RFC 3524, April 2003.
[97] Lawrence, S., "Diagnostic Responses for SIP Hop Limit Errors", [98] Lawrence, S., "Diagnostic Responses for Session Initiation
draft-ietf-sip-hop-limit-diagnostics-02 (work in progress), Protocol Hop Limit Errors",
draft-ietf-sip-hop-limit-diagnostics-03 (work in progress),
June 2006. June 2006.
[98] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network Media [99] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network Media
Services with SIP", RFC 4240, December 2005. Services with SIP", RFC 4240, December 2005.
[99] Jennings, C., "Certificate Management Service for The Session [100] Jennings, C., "Certificate Management Service for The Session
Initiation Protocol (SIP)", draft-ietf-sip-certs-00 (work in Initiation Protocol (SIP)", draft-ietf-sip-certs-01 (work in
progress), May 2006. progress), June 2006.
[100] Lennox, J., "Connection-Oriented Media Transport over the [101] Rosenberg, J., "A Framework for Consent-Based Communications
in the Session Initiation Protocol (SIP)",
draft-ietf-sip-consent-framework-00 (work in progress),
September 2006.
[102] Tschofenig, H., "SIP SAML Profile and Binding",
draft-ietf-sip-saml-00 (work in progress), June 2006.
[103] Camarillo, G., "The Session Initiation Protocol (SIP) Pending
Additions Event Package",
draft-ietf-sipping-pending-additions-00 (work in progress),
September 2006.
[104] 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)", draft-ietf-mmusic-comedia-tls-06 Description Protocol (SDP)", RFC 4572, July 2006.
(work in progress), March 2006.
Author's Address Author's Address
Jonathan Rosenberg Jonathan Rosenberg
Cisco Systems Cisco Systems
600 Lanidex Plaza 600 Lanidex Plaza
Parsippany, NJ 07054 Parsippany, NJ 07054
US US
Phone: +1 973 952-5000 Phone: +1 973 952-5000
 End of changes. 110 change blocks. 
153 lines changed or deleted 205 lines changed or added

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