draft-ietf-sip-hitchhikers-guide-04.txt   draft-ietf-sip-hitchhikers-guide-05.txt 
SIP J. Rosenberg SIP J. Rosenberg
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Informational November 15, 2007 Intended status: Informational February 24, 2008
Expires: May 18, 2008 Expires: August 27, 2008
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-04 draft-ietf-sip-hitchhikers-guide-05
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 May 18, 2008. This Internet-Draft will expire on August 27, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). 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 the specifications under
the SIP umbrella, briefly summarizes each, and groups them into the SIP umbrella, briefly summarizes each, and groups them into
categories. categories.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Scope of this Document . . . . . . . . . . . . . . . . . . . . 4 2. Scope of this Document . . . . . . . . . . . . . . . . . . . . 4
3. Core SIP Specifications . . . . . . . . . . . . . . . . . . . 5 3. Core SIP Specifications . . . . . . . . . . . . . . . . . . . 5
4. Public Switched Telephone Network (PSTN) Interworking . . . . 9 4. Public Switched Telephone Network (PSTN) Interworking . . . . 9
5. General Purpose Infrastructure Extensions . . . . . . . . . . 10 5. General Purpose Infrastructure Extensions . . . . . . . . . . 11
6. NAT Traversal . . . . . . . . . . . . . . . . . . . . . . . . 13 6. NAT Traversal . . . . . . . . . . . . . . . . . . . . . . . . 13
7. Call Control Primitives . . . . . . . . . . . . . . . . . . . 13 7. Call Control Primitives . . . . . . . . . . . . . . . . . . . 14
8. Event Framework . . . . . . . . . . . . . . . . . . . . . . . 14 8. Event Framework . . . . . . . . . . . . . . . . . . . . . . . 15
9. Event Packages . . . . . . . . . . . . . . . . . . . . . . . . 15 9. Event Packages . . . . . . . . . . . . . . . . . . . . . . . . 16
10. Quality of Service . . . . . . . . . . . . . . . . . . . . . . 16 10. Quality of Service . . . . . . . . . . . . . . . . . . . . . . 17
11. Operations and Management . . . . . . . . . . . . . . . . . . 17 11. Operations and Management . . . . . . . . . . . . . . . . . . 18
12. SIP Compression . . . . . . . . . . . . . . . . . . . . . . . 17 12. SIP Compression . . . . . . . . . . . . . . . . . . . . . . . 19
13. SIP Service URIs . . . . . . . . . . . . . . . . . . . . . . . 18 13. SIP Service URIs . . . . . . . . . . . . . . . . . . . . . . . 19
14. Minor Extensions . . . . . . . . . . . . . . . . . . . . . . . 19 14. Minor Extensions . . . . . . . . . . . . . . . . . . . . . . . 20
15. Security Mechanisms . . . . . . . . . . . . . . . . . . . . . 20 15. Security Mechanisms . . . . . . . . . . . . . . . . . . . . . 22
16. Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 23 16. Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 25
17. Instant Messaging, Presence and Multimedia . . . . . . . . . . 24 17. Instant Messaging, Presence and Multimedia . . . . . . . . . . 26
18. Emergency Services . . . . . . . . . . . . . . . . . . . . . . 24 18. Emergency Services . . . . . . . . . . . . . . . . . . . . . . 27
19. Security Considerations . . . . . . . . . . . . . . . . . . . 25 19. Security Considerations . . . . . . . . . . . . . . . . . . . 27
20. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 20. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
21. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25 21. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27
22. Informative References . . . . . . . . . . . . . . . . . . . . 25 22. Informative References . . . . . . . . . . . . . . . . . . . . 28
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 36 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 41
Intellectual Property and Copyright Statements . . . . . . . . . . 37 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 lists
the specifications under the SIP umbrella. For each specification, a the 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 5, line 6 skipping to change at page 5, line 6
associated with SIP. associated with SIP.
2. Scope of this Document 2. Scope of this Document
It is very difficult to enumerate the set of SIP specifications. It is very difficult to enumerate the set of SIP specifications.
This is because there are many protocols that are intimately related This is because there are many protocols that are intimately related
to SIP and used by nearly all SIP implementations, but are not to SIP and used by nearly all SIP implementations, but are not
formally SIP extensions. As such, this document formally defines a formally SIP extensions. As such, this document formally defines a
"SIP specification" as: "SIP specification" as:
o Any specification that defines an extension to RFC 3261, where an o RFC 3261 and any specification that defines an extension to it,
extension is a mechanism that changes or updates in some way a where an extension is a mechanism that changes or updates in some
behavior specified there. way a behavior specified there.
o The basic SDP specification, RFC 4566 [RFC4566], and any o The basic SDP specification, RFC 4566 [RFC4566], and any
specification that defines an extension to SDP whose primary specification that defines an extension to SDP whose primary
purpose is to support SIP. purpose is to support SIP.
o Any specification that defines a MIME object whose primary purpose o Any specification that defines a MIME object whose primary purpose
is to support SIP is to support SIP
Excluded from this list are requirements, architectures, registry Excluded from this list are requirements, architectures, registry
definitions, non-normative frameworks, and processes. Best Current definitions, non-normative frameworks, and processes. Best Current
Practices are included when they normatively define mechanisms for Practices are included when they normatively define mechanisms for
accomplishing a task. accomplishing a task, or provide significant description of the usage
of the normative specifications, such as call flows.
The SIP change process [RFC3427] defines two types of extensions to The SIP change process [RFC3427] defines two types of extensions to
SIP. These are normal extensions and the so-called P-headers (where SIP. These are normal extensions and the so-called P-headers (where
P stands for "preliminary", "private", or "proprietary", and the "P-" P stands for "preliminary", "private", or "proprietary", and the "P-"
prefix is included in the header field name), which are meant to be prefix is included in the header field name), which are meant to be
used in areas of limited applicability. P-headers cannot be defined used in areas of limited applicability. P-headers cannot be defined
in the standards track. For the most part, P-headers are not in the standards track. For the most part, P-headers are not
included in the listing here, with the exception of those which have included in the listing here, with the exception of those which have
seen general usage despite their P-header status. seen general usage despite their P-header status.
skipping to change at page 6, line 50 skipping to change at page 7, line 4
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
package is used. package is used.
RFC 3325, Private Extensions to SIP for Asserted Identity within RFC 3325, Private Extensions to SIP for Asserted Identity within
Trusted Networks (I): Though its P-header status implies that it has Trusted Networks (I): Though its P-header status implies that it has
limited applicability, [RFC3325], which defines the P-Asserted- limited applicability, [RFC3325], which defines the P-Asserted-
Identity header field, has been widely deployed. It is used as Identity header field, has been widely deployed. It is used as
the basic mechanism for providing network asserted caller ID the basic mechanism for providing network asserted caller ID
services. services. Its update, [I-D.ietf-sipping-update-pai], clarifies
its usage for connected party identification as well.
RFC 3327, SIP Extension Header Field for Registering Non-Adjacent RFC 3327, SIP Extension Header Field for Registering Non-Adjacent
Contacts (S): [RFC3327] defines the Path header field. This field Contacts (S): [RFC3327] defines the Path header field. This field
is inserted by proxies between a client and their registrar. It is inserted by proxies between a client and their registrar. It
allows inbound requests towards that client to traverse these allows inbound requests towards that client to traverse these
proxies prior to being delivered to the user agent. It is proxies prior to being delivered to the user agent. It is
essential in any SIP deployment that has edge proxies, which are essential in any SIP deployment that has edge proxies, which are
proxies between the client and the home proxy or SIP registrar. proxies between the client and the home proxy or SIP registrar.
RFC 3581, An Extension to SIP for Symmetric Response Routing (S): RFC 3581, An Extension to SIP for Symmetric Response Routing (S):
skipping to change at page 9, line 14 skipping to change at page 9, line 17
particular, its usage with RFC 4916 means it will typically be particular, its usage with RFC 4916 means it will typically be
used as part of every session, to convey a secure connected used as part of every session, to convey a secure connected
identity. identity.
draft-ietf-sip-sips, The use of the SIPS URI Scheme in the Session draft-ietf-sip-sips, The use of the SIPS URI Scheme in the Session
Initiation Protocol (SIP) (S): [I-D.ietf-sip-sips] formally updated Initiation Protocol (SIP) (S): [I-D.ietf-sip-sips] formally updated
RFC 3261. It revises the processing of the SIPS URI, originally RFC 3261. It revises the processing of the SIPS URI, originally
defined in RFC 3261, to fix many errors and problems that have defined in RFC 3261, to fix many errors and problems that have
been encountered with that mechanism. been encountered with that mechanism.
RFC 3665, Session Initiation Protocol (SIP) Basic Call Flow Examples
(B): [RFC3665] contains best practice call flow examples for basic
SIP interactions - call establishment, termination, and
registration.
Essential Corrections to SIP: A collection of fixes to SIP that Essential Corrections to SIP: A collection of fixes to SIP that
address important bugs and vulnerabilities. These include a fix address important bugs and vulnerabilities. These include a fix
requiring loop detection in any proxy that forks requiring loop detection in any proxy that forks
[I-D.ietf-sip-fork-loop-fix] and a clarification on how record- [I-D.ietf-sip-fork-loop-fix], a clarification on how record-
routing works [I-D.ietf-sip-record-route-fix]. routing works [I-D.ietf-sip-record-route-fix], and a correction to
the IPv6 BNF [I-D.ietf-sip-ipv6-abnf-fix].
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): [RFC2848] is one of the RFC 2848, The PINT Service Protocol (S): [RFC2848] 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
skipping to change at page 10, line 10 skipping to change at page 10, line 19
the development of INFO [RFC2976]. SIP-T has seen widespread the development of INFO [RFC2976]. SIP-T has seen widespread
implementation for the limited deployment model that it addresses. implementation for the limited deployment model that it addresses.
As ISUP endpoints disappear from the network, the need for this As ISUP endpoints disappear from the network, the need for this
mechanism will decrease. mechanism will decrease.
RFC 3398, ISUP to SIP Mapping (S): [RFC3398] defines how to do RFC 3398, ISUP to SIP Mapping (S): [RFC3398] 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
SIP. It is widely used in SS7 to SIP gateways and is part of the SIP. It is widely used in SS7 to SIP gateways and is part of the
SIP-T framework. SIP-T framework.
RFC 4497, Interworking between the Session Initiation Protocol (SIP)
and QSIG (B): [RFC4497] defines how to do protocol mapping from
Q.SIG, used for PBX signaling, to SIP.
RFC 3578, Mapping of ISUP Overlap Signaling to SIP (S): [RFC3578] RFC 3578, Mapping of ISUP Overlap Signaling to SIP (S): [RFC3578]
defines a mechanism to map overlap dialing into SIP. This defines a mechanism to map overlap dialing into SIP. This
specification is widely regarded as the ugliest SIP specification, specification is widely regarded as the ugliest SIP specification,
as the introduction to the specification itself advises that it as the introduction to the specification itself advises that it
has many problems. Overlap signaling (the practice of sending has many problems. Overlap signaling (the practice of sending
digits into the network as dialed instead of waiting for complete digits into the network as dialed instead of waiting for complete
collection of the called party number) is largely incompatible collection of the called party number) is largely incompatible
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.
skipping to change at page 10, line 39 skipping to change at page 11, line 5
Protocol (SIP) (S): [RFC3959] defines a new session disposition type Protocol (SIP) (S): [RFC3959] defines a new session disposition type
for use with early media. It indicates that the SDP in the body for use with early media. It indicates that the SDP in the body
is for a special early media session. This has seen little usage. is for a special early media session. This has seen little usage.
RFC 3204, MIME Media Types for ISUP and QSIG Objects (S): [RFC3204] RFC 3204, MIME Media Types for ISUP and QSIG Objects (S): [RFC3204]
defines MIME objects for representing SS7 and QSIG signaling defines MIME objects for representing SS7 and QSIG signaling
messages. SS7 signaling messages are carried in the body of SIP messages. SS7 signaling messages are carried in the body of SIP
messages when SIP-T is used. QSIG signaling messages can be messages when SIP-T is used. QSIG signaling messages can be
carried in a similar way. carried in a similar way.
RFC3666, Session Initiation Protocol (SIP) Public Switched Telephone
Network (PSTN) Call Flows (B): [RFC3666] provides best practice call
flows around interworking with the PSTN.
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
widely used or as essential as the core specifications. used for every session or registration, as the core specifications
are.
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
provisional. Provisional responses are numbered from 100 to 199. provisional. Provisional responses are numbered from 100 to 199.
In SIP, these responses are not sent reliably. This choice was In SIP, these responses are not sent reliably. This choice was
made in RFC 2543 since the messages were meant to just be truly made in RFC 2543 since the messages were meant to just be truly
informational, and rendered to the user. However, subsequent work informational, and rendered to the user. However, subsequent work
on PSTN interworking demonstrated a need to map provisional on PSTN interworking demonstrated a need to map provisional
responses to PSTN messages that needed to be sent reliably. responses to PSTN messages that needed to be sent reliably.
[RFC3262] was developed to allow reliability of provisional [RFC3262] was developed to allow reliability of provisional
skipping to change at page 11, line 20 skipping to change at page 11, line 39
PRACK brings a great deal of complication for relatively small PRACK brings a great deal of complication for relatively small
benefit. As such, it has seen only moderate levels of deployment. benefit. As such, it has seen only moderate levels of deployment.
RFC 3323, A Privacy Mechanism for the Session Initiation Protocol RFC 3323, A Privacy Mechanism for the Session Initiation Protocol
(SIP) (S): [RFC3323] defines the Privacy header field, used by (SIP) (S): [RFC3323] defines the Privacy header field, used by
clients to request anonymity for their requests. Though it clients to request anonymity for their requests. Though it
defines several privacy services, the only one broadly used is the defines several privacy services, the only one broadly used is the
one that supports privacy of the P-Asserted-Identity header field one that supports privacy of the P-Asserted-Identity header field
[RFC3325]. [RFC3325].
draft-ietf-sip-ua-privacy, UA-Driven Privacy Mechanism for SIP (S):
[I-D.ietf-sip-ua-privacy] defines a mechanism for achieving
anonymous calls in SIP. It is an alternative to [RFC3323], and
instead places more intelligence in the endpoint to craft
anonymous messages by directly accessing network services.
RFC 2976, The INFO Method (S): [RFC2976] was defined as an extension RFC 2976, The INFO Method (S): [RFC2976] was defined as an extension
to RFC 2543. It defines a method, INFO, used to transport mid- to RFC 2543. It defines a method, INFO, used to transport mid-
dialog information that has no impact on SIP itself. Its driving dialog information that has no impact on SIP itself. Its driving
application was the transport of PSTN related information when application was the transport of PSTN related information when
using SIP between a pair of gateways. Though originally conceived using SIP between a pair of gateways. Though originally conceived
for broader use, it only found standardized usage with SIP-T for broader use, it only found standardized usage with SIP-T
[RFC3372]. It has been used to support numerous proprietary and [RFC3372]. It has been used to support numerous proprietary and
non-interoperable extensions due to its poorly defined scope. non-interoperable extensions due to its poorly defined scope.
RFC 3326, The Reason header field for SIP (S): [RFC3326] defines the RFC 3326, The Reason header field for SIP (S): [RFC3326] defines the
skipping to change at page 13, line 5 skipping to change at page 13, line 29
[RFC4091] defines a mechanism for including both IPv4 and IPv6 [RFC4091] defines a mechanism for including both IPv4 and IPv6
addresses for a media session as alternates. This mechanism has addresses for a media session as alternates. This mechanism has
been deprecated in favor of ICE [I-D.ietf-mmusic-ice]. been deprecated in favor of ICE [I-D.ietf-mmusic-ice].
draft-ietf-mmusic-sdp-media-capabilities, SDP Media Capabilities draft-ietf-mmusic-sdp-media-capabilities, SDP Media Capabilities
Negotiation (S): [I-D.ietf-mmusic-sdp-media-capabilities] defines an Negotiation (S): [I-D.ietf-mmusic-sdp-media-capabilities] defines an
extension to the SDP capability negotiation framework extension to the SDP capability negotiation framework
[I-D.ietf-mmusic-sdp-capability-negotiation] for negotiating [I-D.ietf-mmusic-sdp-capability-negotiation] for negotiating
codecs, codec parameters, and media streams. codecs, codec parameters, and media streams.
draft-ietf-sip-body-handling, Message Body Handling in the Session
Initiation Protocol (SIP): [I-D.ietf-sip-body-handling] clarifies
handling of bodies in SIP, focusing primarily on multi-part
behavior, which was underspecified in SIP.
6. NAT Traversal 6. NAT Traversal
These SIP extensions are primarily aimed at addressing NAT traversal These SIP extensions are primarily aimed at addressing NAT traversal
for SIP. for SIP.
draft-ietf-mmusic-ice, Interactive Connectivity Establishment (ICE) draft-ietf-mmusic-ice, Interactive Connectivity Establishment (ICE)
(S): [I-D.ietf-mmusic-ice] defines a technique for NAT traversal of (S): [I-D.ietf-mmusic-ice] defines a technique for NAT traversal of
media sessions for protocols that make use of the offer/answer media sessions for protocols that make use of the offer/answer
model. This specification is the IETF recommended mechanism for model. This specification is the IETF recommended mechanism for
NAT traversal for SIP media streams, and is meant to be used even NAT traversal for SIP media streams, and is meant to be used even
skipping to change at page 15, line 36 skipping to change at page 16, line 17
9. Event Packages 9. Event Packages
These are event packages defined to utilize the SIP events framework. These are event packages defined to utilize the SIP events framework.
Many of these are also listed elsewhere in their respective areas. Many of these are also listed elsewhere in their respective areas.
RFC 3680, A SIP Event Package for Registrations (S): [RFC3680] RFC 3680, A SIP Event Package for Registrations (S): [RFC3680]
defines an event package for finding out about changes in defines an event package for finding out about changes in
registration state. registration state.
draft-ietf-sipping-gruu-reg-event (S):
[I-D.ietf-sipping-gruu-reg-event] is an extension to the
registration event package [RFC3680] that allows user agents to
learn about their GRUUs. It is particularly useful in helping to
synchronize a client and its registrar with its currently valid
temporary GRUU.
RFC 3842, A Message Summary and Message Waiting Indication Event RFC 3842, A Message Summary and Message Waiting Indication Event
Package for SIP (S): [RFC3482] defines a way for a user agent to Package for SIP (S): [RFC3482] 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): [RFC3856] defines an RFC 3856, A Presence Event Package for SIP (S): [RFC3856] defines an
event package for indicating user presence through SIP. event package for indicating user presence through SIP.
RFC 3857, A Watcher Information Event Template Package for SIP (S): RFC 3857, A Watcher Information Event Template Package for SIP (S):
skipping to change at page 16, line 27 skipping to change at page 17, line 18
traditional telephone. It, along with RFC 2833 [RFC2833], are the traditional telephone. It, along with RFC 2833 [RFC2833], are the
two mechanisms defined for handling DTMF. RFC 4730 is a two mechanisms defined for handling DTMF. RFC 4730 is a
signaling-path solution, and RFC 2833 is a media-path solution. signaling-path solution, and RFC 2833 is a media-path solution.
draft-ietf-sipping-rtcp-summary, SIP Event Package for Voice Quality draft-ietf-sipping-rtcp-summary, SIP Event Package for Voice Quality
Reporting (S): [I-D.ietf-sipping-rtcp-summary] defines a SIP event Reporting (S): [I-D.ietf-sipping-rtcp-summary] defines a SIP event
package that enables the collection and reporting of metrics that package that enables the collection and reporting of metrics that
measure the quality for Voice over Internet Protocol (VoIP) measure the quality for Voice over Internet Protocol (VoIP)
sessions. sessions.
draft-ietf-sip-session-policy-framework, A Framework for Session
Initiation Protocol (SIP) Session Policies (S):
[I-D.ietf-sip-session-policy-framework] defines a framework for
session policies. In this framework, policy servers are used to
tell user agents about the media characteristics required for a
particular session. The session policy framework has not been
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 that [I-D.ietf-sipping-policy-package] defines a SIP event package used
allows a policy server to notify a user agent about its desire for in conjunction with the session policy framework
the UA to use certain codecs or generally obey certain media [I-D.ietf-sip-session-policy-framework].
session policies.
draft-ietf-sipping-pending-additions, The Session Initiation Protocol draft-ietf-sipping-pending-additions, The Session Initiation Protocol
(SIP) Pending Additions Event Package (S): (SIP) Pending Additions Event Package (S):
[I-D.ietf-sipping-pending-additions] defines a SIP event package [I-D.ietf-sipping-pending-additions] defines a SIP event package
that allows a UA to learn whether consent has been given for the 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 addition of an address to a SIP "mailing list". It is used in
conjunction with the SIP framework for consent conjunction with the SIP framework for consent
[I-D.ietf-sip-consent-framework]. [I-D.ietf-sip-consent-framework].
10. Quality of Service 10. Quality of Service
skipping to change at page 17, line 6 skipping to change at page 18, line 5
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
preconditions framework, which defines conditions that must be preconditions framework, which defines conditions that must be
true in order for a SIP session to proceed. true in order for a SIP session to proceed.
draft-ietf-mmusic-qos-identification, Quality of Service (QoS)
Mechanism Selection in the Session Description Protocol (SDP) (S):
[I-D.ietf-mmusic-qos-identification] defines a way for user agents
to negotiate what type of end-to-end QoS mechanism to use for a
session. At this time, there are two that can be used - RSVP and
NSIS. This negotiation is done through an SDP extension. Due to
limited deployment of RSVP and even more limited deployment of
NSIS, this extension has not been widely used.
RFC 3313, Private SIP Extensions for Media Authorization (I): RFC 3313, Private SIP Extensions for Media Authorization (I):
[RFC3313] defines a P-header that provides a mechanism for passing [RFC3313] 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.
skipping to change at page 18, line 30 skipping to change at page 19, line 37
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
Considerations for Session Initiation Protocol (SIP) Uniform Resource
Identifier (URI)-List Services (S): [I-D.ietf-sipping-uri-services]
defines the framework for list services in SIP. In this
framework, a UA can include an XML list object in the body of
various requests and the server provides list-oriented services as
a consequence. For example, a SUBSCRIBE with a list subscribes to
the URI in the list.
draft-ietf-sip-uri-list-subscribe, Subscriptions To Request-Contained draft-ietf-sip-uri-list-subscribe, Subscriptions To Request-Contained
Resource Lists in SIP (S): [I-D.ietf-sip-uri-list-subscribe] allows Resource Lists in SIP (S): [I-D.ietf-sip-uri-list-subscribe] uses
the URI list framework [I-D.ietf-sipping-uri-services] and allows
a 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 a series of subscriptions, and compile This server will generate subscriptions to the URI in the list,
the resulting information and send it back to the subscriber. For and compile the resulting information and send it back to the
this specification, the list of things to subscribe to is in the subscriber.
body of the SUBSCRIBE request.
draft-ietf-sip-uri-list-message, Multiple-Recipient MESSAGE Requests draft-ietf-sip-uri-list-message, Multiple-Recipient MESSAGE Requests
in SIP (S): [I-D.ietf-sip-uri-list-message] is similar to in SIP (S): [I-D.ietf-sip-uri-list-message] uses the URI list
[I-D.ietf-sip-uri-list-subscribe]. However, instead of framework [I-D.ietf-sipping-uri-services] and allows a client to
subscribing to the resource, a MESSAGE request is sent to the send a MESSAGE to a number of recipients.
resource, and it will send a copy to each recipient.
draft-ietf-sip-uri-list-conferencing, Conference Establishment Using draft-ietf-sip-uri-list-conferencing, Conference Establishment Using
Request-Contained Lists in SIP (S): Request-Contained Lists in SIP (S):
[I-D.ietf-sip-uri-list-conferencing] is similar to [I-D.ietf-sip-uri-list-conferencing] uses the URI list framework
[I-D.ietf-sip-uri-list-subscribe]. However, instead of [I-D.ietf-sipping-uri-services] and allows a client to ask the
subscribing to the resource, an INVITE request is sent to the server to act as a conference focus and send an invitation to each
resource, and it will act as a conference focus and generate an recipient in the list.
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 20, line 5 skipping to change at page 21, line 17
in REFER. It is useful for informing the target of the REFER in REFER. It is useful for informing the target of the REFER
about the characteristics of the intentended target of the about the characteristics of the intentended target of the
referred request. referred request.
draft-ietf-sip-answermode, Requesting Answer Modes for SIP (S): draft-ietf-sip-answermode, Requesting Answer Modes for SIP (S):
[I-D.ietf-sip-answermode] defines an extension for indicating to [I-D.ietf-sip-answermode] defines an extension for indicating to
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.
draft-ietf-sip-acr-code, Rejecting Anonymous Requests in SIP (S): RFC 5079, Rejecting Anonymous Requests in SIP (S): [RFC5079] defines
[I-D.ietf-sip-acr-code] defines a mechanism for a called party to a mechanism for a called party to indicate to the calling party
indicate to the calling party that a call was rejected since the that a call was rejected since the caller was anonymous. This is
caller was anonymous. This is needed for implementation of the needed for implementation of the Anonymous Call Rejection (ACR)
Anonymous Call Rejection (ACR) feature in SIP. feature in SIP.
draft-ietf-sip-multiple-refer, Referring to Multiple Resources in SIP draft-ietf-sip-multiple-refer, Referring to Multiple Resources in SIP
(S): [I-D.ietf-sip-multiple-refer] allows a UA sending a REFER to (S): [I-D.ietf-sip-multiple-refer] allows a UA sending a REFER to
ask the recipient of the REFER to generate multiple SIP requests, ask the recipient of the REFER to generate multiple SIP requests,
not just one. This is useful for conferencing, where a client not just one. This is useful for conferencing, where a client
would like to ask a conference server to eject multiple users. would like to ask a conference server 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
skipping to change at page 20, line 47 skipping to change at page 22, line 10
[I-D.ietf-mmusic-connectivity-precon] defines a usage of the [I-D.ietf-mmusic-connectivity-precon] defines a usage of the
precondition framework [RFC3312]. The connectivity precondition precondition framework [RFC3312]. The connectivity precondition
makes sure that the session doesn't get established until actual makes sure that the session doesn't get established until actual
packet connectivity is checked. packet connectivity is checked.
RFC 4796, The SDP (Session Description Protocol) Content Attribute RFC 4796, The SDP (Session Description Protocol) Content Attribute
(S): [RFC4796] defines an SDP attribute for describing the purpose (S): [RFC4796] defines an SDP attribute for describing the purpose
of a media stream. Examples include a slide view, the speaker, a of a media stream. Examples include a slide view, the speaker, a
sign language feed, and so on. sign language feed, and so on.
draft-ietf-sipping-v6-transition, IPv6 Transition in the Session
Initiation Protocol (SIP) (S): [I-D.ietf-sipping-v6-transition]
defines practices for interworking between IPv6 and IPv6 user
agents. This is done through multi-homed proxies which interwork
IPv4 and IPv6, along with ICE [I-D.ietf-mmusic-ice] for media
traversal. The specification includes some minor extensions and
clarifications to SDP in order to cover some additional cases.
draft-ietf-sip-connect-reuse, Connection Reuse in the Session
Initiation Protocol (SIP) (S): [I-D.ietf-sip-connect-reuse] defines
an extension to SIP that allows a TLS connection between servers
to be reused for requests in both directions. Normally two
connections are set up between a pair of servers, one for requests
in each direction.
15. Security Mechanisms 15. Security Mechanisms
Several extensions provide additional security features to SIP. Several extensions provide additional security features to SIP.
RFC 4474, Enhancements for Authenticated Identity Management in SIP RFC 4474, Enhancements for Authenticated Identity Management in SIP
(S): [RFC4474] defines a mechanism for providing a cryptographically (S): [RFC4474] defines a mechanism for providing a cryptographically
verifiable identity of the calling party in a SIP request. Known verifiable identity of the calling party in a SIP request. Known
as "SIP Identity", this mechanism provides an alternative to RFC as "SIP Identity", this mechanism provides an alternative to RFC
3325. It has seen little deployment so far, but its importance as 3325. It has seen little deployment so far, but its importance as
a key construct for anti-spam techniques and new security a key construct for anti-spam techniques and new security
mechanisms makes it a core part of the SIP specifications. mechanisms makes it a core part of the SIP specifications.
RFC 4916, Connected Identity in the Session Initiation Protocol (SIP)
(S): [RFC4916] formally updates RFC 3261. It defines an extension
to SIP that allows a calling user to determine the identity of the
final called user (connected party). Due to forwarding and
retargeting services, this may not be the same as the user that
the caller was originally trying to reach. The mechanism works in
tandem with the SIP identity specification [RFC4474] to provide
signatures over the connected party identity. It can also be used
if a party identity changes mid call due to third party call
control actions or PSTN behavior.
draft-ietf-sip-sips, The use of the SIPS URI Scheme in the Session
Initiation Protocol (SIP) (S): [I-D.ietf-sip-sips] formally updated
RFC 3261. It revises the processing of the SIPS URI, originally
defined in RFC 3261, to fix many errors and problems that have
been encountered with that mechanism.
draft-ietf-sip-domain-certs, Domain Certificates in the Session
Initiation Protocol (SIP) (B): [I-D.ietf-sip-domain-certs] clarifies
the usage of SIP over TLS with regards to certificate handling,
and defines additional procedures needed for interoperability.
RFC 3323, A Privacy Mechanism for the Session Initiation Protocol RFC 3323, A Privacy Mechanism for the Session Initiation Protocol
(SIP) (S): [RFC3323] defines the Privacy header field, used by (SIP) (S): [RFC3323] defines the Privacy header field, used by
clients to request anonymity for their requests. Though it clients to request anonymity for their requests. Though it
defines several privacy services, the only one broadly used is the defines several privacy services, the only one broadly used is the
one that supports privacy of the P-Asserted-Identity header field one that supports privacy of the P-Asserted-Identity header field
[RFC3325]. [RFC3325].
RFC 4567, Key Management Extensions for Session Description Protocol RFC 4567, Key Management Extensions for Session Description Protocol
(SDP) and Real Time Streaming Protocol (RTSP) (S): [RFC4567] defines (SDP) and Real Time Streaming Protocol (RTSP) (S): [RFC4567] defines
extensions to SDP that allow tunneling of an key management extensions to SDP that allow tunneling of an key management
skipping to change at page 21, line 48 skipping to change at page 23, line 46
draft-ietf-sip-dtls-srtp-framework, Framework for Establishing an draft-ietf-sip-dtls-srtp-framework, Framework for Establishing an
SRTP Security Context using DTLS (S): SRTP Security Context using DTLS (S):
[I-D.ietf-sip-dtls-srtp-framework] defines the overall framework [I-D.ietf-sip-dtls-srtp-framework] defines the overall framework
and SDP and SIP processing required to perform key management for and SDP and SIP processing required to perform key management for
RTP using Datagram TLS (DTLS) [RFC4347] directly between RTP using Datagram TLS (DTLS) [RFC4347] directly between
endpoints, over the media path. It is one of three SRTP keying endpoints, over the media path. It is one of three SRTP keying
techniques specified for SIP, with DTLS-SRTP techniques specified for SIP, with DTLS-SRTP
[I-D.ietf-sip-dtls-srtp-framework] having been selected as the [I-D.ietf-sip-dtls-srtp-framework] having been selected as the
final solution. final solution.
draft-ietf-mmusic-sdp-dtls, Session Description Protocol (SDP)
Indicators for Datagram Transport Layer Security (DTLS) (S):
[I-D.ietf-mmusic-sdp-dtls] defines the usage of SDP with DTLS-
SRTP.
RFC 3853, S/MIME AES Requirement for SIP (S): [RFC3853] formally RFC 3853, S/MIME AES Requirement for SIP (S): [RFC3853] formally
updates RFC 3261. It is a brief specification that updates the updates RFC 3261. It is a brief specification that updates the
cryptography mechanisms used in SIP S/MIME. However, SIP S/MIME cryptography mechanisms used in SIP S/MIME. However, SIP S/MIME
has seen very little deployment. has seen very little deployment.
draft-ietf-sip-certs, Certificate Management Service for The Session draft-ietf-sip-certs, Certificate Management Service for The Session
Initiation Protocol (SIP) (S): [I-D.ietf-sip-certs] defines a Initiation Protocol (SIP) (S): [I-D.ietf-sip-certs] defines a
certificate service for SIP whose purpose is to facilitate the certificate service for SIP whose purpose is to facilitate the
deployment of S/MIME. The certificate service allows clients to deployment of S/MIME. The certificate service allows clients to
store and retrieve their own certificates, in addition to store and retrieve their own certificates, in addition to
skipping to change at page 22, line 36 skipping to change at page 24, line 41
[I-D.ietf-sip-consent-framework] defines several extensions to [I-D.ietf-sip-consent-framework] defines several extensions to
SIP, including the Trigger-Consent and Permission-Missing header SIP, including the Trigger-Consent and Permission-Missing header
fields. These header fields, in addition to the other procedures fields. These header fields, in addition to the other procedures
defined in the document, define a way to manage membership on "SIP defined in the document, define a way to manage membership on "SIP
mailing lists" used for instant messaging or conferencing. In mailing lists" used for instant messaging or conferencing. In
particular, it helps avoid the problem of using such amplification particular, it helps avoid the problem of using such amplification
services for the purposes of an attack on the network, by making services for the purposes of an attack on the network, by making
sure a user authorizes the addition of their address onto such a sure a user authorizes the addition of their address onto such a
service. service.
draft-ietf-sipping-consent-format, A Document Format for Requesting
Consent (S): [I-D.ietf-sipping-consent-format] defines an XML object
used by the consent framework. Consent documents are sent from
SIP "mailing list servers" to users to allow them to manage their
membership on lists.
draft-ietf-sipping-pending-additions, The Session Initiation Protocol draft-ietf-sipping-pending-additions, The Session Initiation Protocol
(SIP) Pending Additions Event Package (S): (SIP) Pending Additions Event Package (S):
[I-D.ietf-sipping-pending-additions] defines a SIP event package [I-D.ietf-sipping-pending-additions] defines a SIP event package
that allows a UA to learn whether consent has been given for the 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 addition of an address to a SIP "mailing list". It is used in
conjunction with the SIP framework for consent conjunction with the SIP framework for consent
[I-D.ietf-sip-consent-framework]. [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
skipping to change at page 23, line 18 skipping to change at page 25, line 27
user agents to specific network intermediaries. user agents to specific network intermediaries.
RFC 4572, 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): [RFC4572] specifies a mechanism for signaling TLS-based (SDP) (S): [RFC4572] specifies a mechanism for signaling TLS-based
media streams between endpoints. It expands the TCP-based media media streams between endpoints. It expands the TCP-based media
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.
draft-ietf-mmusic-secruityprecondition, Security Preconditions for RFC 5027, Security Preconditions for Session Description Protocol
Session Description Protocol Media Streams (S): Media Streams (S): [RFC5027] defines a precondition for use with the
[I-D.ietf-mmusic-securityprecondition] defines a precondition for preconditions framework [RFC3312]. The security precondition
use with the preconditions framework [RFC3312]. The security prevents a session from being established until a security media
precondition prevents a session from being established until a stream is set up.
security media stream is set up.
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
skipping to change at page 24, line 13 skipping to change at page 26, line 23
would like to ask a conference server to eject multiple users. would like to ask a conference server to eject multiple users.
draft-ietf-sip-uri-list-conferencing, Conference Establishment Using draft-ietf-sip-uri-list-conferencing, Conference Establishment Using
Request-Contained Lists in SIP (S): Request-Contained Lists in SIP (S):
[I-D.ietf-sip-uri-list-conferencing] is similar to [I-D.ietf-sip-uri-list-conferencing] is similar to
[I-D.ietf-sip-uri-list-subscribe]. However, instead of [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 -
Conferencing for User Agents (B): [RFC4579] defines best practice
procedures and call flows for conferencing. This includes
conference creation, joining, and dial out, amongst other
capabilities.
RFC 4583, Session Description Protocol (SDP) Format for Binary Floor RFC 4583, Session Description Protocol (SDP) Format for Binary Floor
Control Protocol (BFCP) Streams (S): [RFC4583] defines a mechanism Control Protocol (BFCP) Streams (S): [RFC4583] defines a mechanism
in SDP to signal floor control streams that use BFCP. It is used in SDP to signal floor control streams that use BFCP. It is used
for Push-To-Talk and conference floor control. for Push-To-Talk and conference floor control.
17. Instant Messaging, Presence and Multimedia 17. Instant Messaging, Presence and Multimedia
SIP provides extensions for instant messaging, presence, and SIP provides extensions for instant messaging, presence, and
multimedia. multimedia.
skipping to change at page 24, line 43 skipping to change at page 27, line 12
event package. Its primary usage is with presence, but it can be event package. Its primary usage is with presence, but it can be
used with any event package. used with any event package.
draft-ietf-mmusic-file-transfer-mech, A Session Description Protocol draft-ietf-mmusic-file-transfer-mech, A Session Description Protocol
(SDP) Offer/Answer Mechanism to Enable File Transfer (S): (SDP) Offer/Answer Mechanism to Enable File Transfer (S):
[I-D.ietf-mmusic-file-transfer-mech] defines a mechanism for [I-D.ietf-mmusic-file-transfer-mech] defines a mechanism for
signaling a file transfer session with SIP. signaling a file transfer session with SIP.
18. Emergency Services 18. Emergency Services
Emergency services here covers pre-emption services, which allow Emergency services include pre-emption features, 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, along with traditional emergency calling.
RFC 4411, Extending the SIP Reason Header for Preemption Events (S): RFC 4411, Extending the SIP Reason Header for Preemption Events (S):
[RFC4411] defines an extension to the Reason header, allowing a UA [RFC4411] defines an extension to the Reason header, allowing a UA
to know that its dialog was torn down because a higher priority to know that its dialog was torn down because a higher priority
session came through. session came through.
RFC 4412, Communications Resource Priority for SIP (S): [RFC4412] RFC 4412, Communications Resource Priority for SIP (S): [RFC4412]
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.
draft-ietf-sip-location-conveyance, Location Conveyance for the
Session Initiation Protocol (S): [I-D.ietf-sip-location-conveyance]
defines a mechanism for carrying location objects in SIP messages.
This is used to convey location from a UA to an emergency call
taker.
19. Security Considerations 19. 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. Of does not introduce any security considerations on its own. Of
course, the world would be far more secure if everyone would follow course, the world would be far more secure if everyone would follow
one simple rule: "Don't Panic!" [HGTTG]. one simple rule: "Don't Panic!" [HGTTG].
20. IANA Considerations 20. IANA Considerations
None. None.
21. Acknowledgements 21. Acknowledgements
The author would like to thank Spencer Dawkins, Brian Stucker, John The author would like to thank Spencer Dawkins, Brian Stucker, Keith
Elwell and Avshalom Houri for their comments on this document. Drage, John Elwell and Avshalom Houri for their comments on this
document.
22. Informative References 22. Informative References
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
skipping to change at page 27, line 19 skipping to change at page 29, line 44
[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-10 (work in progress), July 2007. draft-ietf-sip-outbound-11 (work in progress),
November 2007.
[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 29, line 11 skipping to change at page 31, line 36
[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-06 (work in progress),
September 2007. 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.
[I-D.ietf-sip-acr-code] [RFC5079] Rosenberg, J., "Rejecting Anonymous Requests in the
Rosenberg, J., "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)", RFC 5079,
Session Initiation Protocol (SIP)", December 2007.
draft-ietf-sip-acr-code-05 (work in progress), July 2007.
[I-D.ietf-sip-multiple-refer] [I-D.ietf-sip-multiple-refer]
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)",
draft-ietf-sip-multiple-refer-02 (work in progress), draft-ietf-sip-multiple-refer-03 (work in progress),
November 2007. 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 30, line 45 skipping to change at page 33, line 20
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)
Extensions for Media Authorization", RFC 3313, Extensions for Media Authorization", RFC 3313,
January 2003. January 2003.
[I-D.ietf-sipping-config-framework] [I-D.ietf-sipping-config-framework]
Channabasappa, S., "A Framework for Session Initiation Channabasappa, S., "A Framework for Session Initiation
Protocol User Agent Profile Delivery", Protocol User Agent Profile Delivery",
draft-ietf-sipping-config-framework-13 (work in progress), draft-ietf-sipping-config-framework-15 (work in progress),
October 2007. February 2008.
[RFC3486] Camarillo, G., "Compressing the Session Initiation [RFC3486] Camarillo, G., "Compressing the Session Initiation
Protocol (SIP)", RFC 3486, February 2003. Protocol (SIP)", RFC 3486, February 2003.
[RFC3482] Foster, M., McGarry, T., and J. Yu, "Number Portability in [RFC3482] Foster, M., McGarry, T., and J. Yu, "Number Portability in
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.
skipping to change at page 31, line 22 skipping to change at page 33, line 46
[I-D.ietf-sip-uri-list-subscribe] [I-D.ietf-sip-uri-list-subscribe]
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)", draft-ietf-sip-uri-list-subscribe-02
(work in progress), November 2007. (work in progress), November 2007.
[I-D.ietf-sip-uri-list-message] [I-D.ietf-sip-uri-list-message]
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-02 (work in (SIP)", draft-ietf-sip-uri-list-message-03 (work in
progress), November 2007. progress), December 2007.
[I-D.ietf-sip-uri-list-conferencing] [I-D.ietf-sip-uri-list-conferencing]
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)", draft-ietf-sip-uri-list-conferencing-02
(work in progress), November 2007. (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.
skipping to change at page 32, line 30 skipping to change at page 35, line 4
Description Protocol (SDP)", RFC 3388, December 2002. Description Protocol (SDP)", RFC 3388, December 2002.
[RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute [RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute
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., "Addressing an Amplification Vulnerability in Sparks, R., Lawrence, S., Hawrylyshen, A., and B. Campen,
Session Initiation Protocol (SIP) Forking Proxies", "Addressing an Amplification Vulnerability in Session
draft-ietf-sip-fork-loop-fix-05 (work in progress), Initiation Protocol (SIP) Forking Proxies",
March 2007. draft-ietf-sip-fork-loop-fix-06 (work in progress),
November 2007.
[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 33, line 7 skipping to change at page 35, line 31
[RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in [RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
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-04 (work in progress), draft-ietf-mmusic-ice-tcp-05 (work in progress),
July 2007. November 2007.
[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
for Binary Floor Control Protocol (BFCP) Streams", for Binary Floor Control Protocol (BFCP) Streams",
RFC 4583, November 2006. RFC 4583, November 2006.
[I-D.ietf-mmusic-securityprecondition] [RFC5027] Andreasen, F. and D. Wing, "Security Preconditions for
Andreasen, F. and D. Wing, "Security Preconditions for
Session Description Protocol (SDP) Media Streams", Session Description Protocol (SDP) Media Streams",
draft-ietf-mmusic-securityprecondition-04 (work in RFC 5027, October 2007.
progress), July 2007.
[I-D.ietf-mmusic-connectivity-precon] [I-D.ietf-mmusic-connectivity-precon]
Andreasen, F., "Connectivity Preconditions for Session Andreasen, F., Camarillo, G., Oran, D., and D. Wing,
Description Protocol Media Streams", "Connectivity Preconditions for Session Description
draft-ietf-mmusic-connectivity-precon-02 (work in Protocol Media Streams",
progress), June 2006. draft-ietf-mmusic-connectivity-precon-04 (work in
progress), January 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
skipping to change at page 34, line 6 skipping to change at page 36, line 30
Policies", draft-ietf-sipping-policy-package-04 (work in Policies", draft-ietf-sipping-policy-package-04 (work in
progress), August 2007. progress), August 2007.
[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., "Certificate Management Service for The Jennings, C., Peterson, J., and J. Fischl, "Certificate
Session Initiation Protocol (SIP)", Management Service for The Session Initiation Protocol
draft-ietf-sip-certs-04 (work in progress), July 2007. (SIP)", draft-ietf-sip-certs-05 (work in progress),
February 2008.
[I-D.ietf-sip-consent-framework] [I-D.ietf-sip-consent-framework]
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)", draft-ietf-sip-consent-framework-03 (work Protocol (SIP)", draft-ietf-sip-consent-framework-04 (work
in progress), November 2007. in progress), January 2008.
[I-D.ietf-sip-saml] [I-D.ietf-sip-saml]
Tschofenig, H., "SIP SAML Profile and Binding", Tschofenig, H., Hodges, J., Peterson, J., Polk, J., and D.
draft-ietf-sip-saml-02 (work in progress), May 2007. Sicker, "SIP SAML Profile and Binding",
draft-ietf-sip-saml-03 (work in progress), November 2007.
[I-D.ietf-sipping-pending-additions] [I-D.ietf-sipping-pending-additions]
Camarillo, G., "The Session Initiation Protocol (SIP) Camarillo, G., "The Session Initiation Protocol (SIP)
Pending Additions Event Package", Pending Additions Event Package",
draft-ietf-sipping-pending-additions-03 (work in draft-ietf-sipping-pending-additions-03 (work in
progress), November 2007. 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-07 (work in draft-ietf-mmusic-sdp-capability-negotiation-08 (work in
progress), October 2007. progress), December 2007.
[I-D.ietf-mmusic-sdp-media-capabilities] [I-D.ietf-mmusic-sdp-media-capabilities]
Andreasen, F., "SDP media capabilities Negotiation", Gilman, R., Even, R., and F. Andreasen, "SDP media
draft-ietf-mmusic-sdp-media-capabilities-01 (work in capabilities Negotiation",
progress), February 2007. draft-ietf-mmusic-sdp-media-capabilities-02 (work in
progress), November 2007.
[I-D.ietf-mmusic-file-transfer-mech] [I-D.ietf-mmusic-file-transfer-mech]
Garcia-Martin, M., Isomaki, M., Camarillo, G., and S. Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S.,
Loreto, "A Session Description Protocol (SDP) Offer/Answer and P. Kyzivat, "A Session Description Protocol (SDP)
Mechanism to Enable File Transfer", Offer/Answer Mechanism to Enable File Transfer",
draft-ietf-mmusic-file-transfer-mech-04 (work in draft-ietf-mmusic-file-transfer-mech-06 (work in
progress), October 2007. progress), December 2007.
[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.20.0, September 2007. TS 24.229 5.21.0, December 2007.
[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. and C. Lebel, "Addressing Record-Route issues
in the Session Initiation Protocol (SIP)", in the Session Initiation Protocol (SIP)",
draft-ietf-sip-record-route-fix-01 (work in progress), draft-ietf-sip-record-route-fix-01 (work in progress),
November 2007. November 2007.
[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-01 (work in progress),
August 2007. August 2007.
[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-06 (work Initiation Protocol (SIP)", draft-ietf-sip-sips-07 (work
in progress), August 2007. in progress), November 2007.
[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] [I-D.ietf-rohc-sigcomp-sip]
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)",
draft-ietf-rohc-sigcomp-sip-08 (work in progress), draft-ietf-rohc-sigcomp-sip-08 (work in progress),
September 2007. 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-00 (work in progress), July 2007. draft-ietf-simple-simple-01 (work in progress),
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
skipping to change at page 36, line 18 skipping to change at page 38, line 47
[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-00 (work in progress),
November 2007. November 2007.
[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-03 (work in Multimedia", draft-ietf-ecrit-framework-04 (work in
progress), September 2007. progress), November 2007.
[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.
[RFC3830] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K. [RFC3830] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K.
Norrman, "MIKEY: Multimedia Internet KEYing", RFC 3830, Norrman, "MIKEY: Multimedia Internet KEYing", RFC 3830,
August 2004. August 2004.
[RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer [RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
Security", RFC 4347, April 2006. Security", RFC 4347, April 2006.
[I-D.ietf-sipping-v6-transition]
Camarillo, G., "IPv6 Transition in the Session Initiation
Protocol (SIP)", draft-ietf-sipping-v6-transition-07 (work
in progress), August 2007.
[I-D.ietf-sipping-update-pai]
Elwell, J., "Updates to Asserted Identity in the Session
Initiation Protocol (SIP)",
draft-ietf-sipping-update-pai-00 (work in progress),
February 2008.
[RFC3665] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and
K. Summers, "Session Initiation Protocol (SIP) Basic Call
Flow Examples", BCP 75, RFC 3665, December 2003.
[RFC3666] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and
K. Summers, "Session Initiation Protocol (SIP) Public
Switched Telephone Network (PSTN) Call Flows", BCP 76,
RFC 3666, December 2003.
[I-D.ietf-sip-ipv6-abnf-fix]
Gurbani, V., Carpenter, B., and B. Tate, "Essential
correction for IPv6 ABNF and URI comparison in RFC3261",
draft-ietf-sip-ipv6-abnf-fix-00 (work in progress),
February 2008.
[RFC4497] Elwell, J., Derks, F., Mourot, P., and O. Rousseau,
"Interworking between the Session Initiation Protocol
(SIP) and QSIG", BCP 117, RFC 4497, May 2006.
[I-D.ietf-sip-ua-privacy]
Munakata, M., Schubert, S., and T. Ohba, "UA-Driven
Privacy Mechanism for SIP", draft-ietf-sip-ua-privacy-00
(work in progress), November 2007.
[I-D.ietf-sip-body-handling]
Camarillo, G., "Message Body Handling in the Session
Initiation Protocol (SIP)",
draft-ietf-sip-body-handling-01 (work in progress),
January 2008.
[I-D.ietf-sip-domain-certs]
Gurbani, V., Lawrence, S., and B. Laboratories, "Domain
Certificates in the Session Initiation Protocol (SIP)",
draft-ietf-sip-domain-certs-00 (work in progress),
November 2007.
[I-D.ietf-sipping-gruu-reg-event]
Kyzivat, P., "Registration Event Package Extension for
Session Initiation Protocol (SIP) Globally Routable User
Agent URIs (GRUUs)", draft-ietf-sipping-gruu-reg-event-09
(work in progress), July 2007.
[I-D.ietf-sip-session-policy-framework]
Hilt, V., "A Framework for Session Initiation Protocol
(SIP) Session Policies",
draft-ietf-sip-session-policy-framework-02 (work in
progress), August 2007.
[I-D.ietf-mmusic-qos-identification]
Polk, J., Dhesikan, S., and G. Camarillo, "Quality of
Service (QoS) Mechanism Selection in the Session
Description Protocol (SDP)",
draft-ietf-mmusic-qos-identification-01 (work in
progress), January 2008.
[I-D.ietf-sipping-uri-services]
Camarillo, G. and A. Roach, "Framework and Security
Considerations for Session Initiation Protocol (SIP)
Uniform Resource Identifier (URI)-List Services",
draft-ietf-sipping-uri-services-07 (work in progress),
November 2007.
[I-D.ietf-sip-connect-reuse]
Mahy, R., Gurbani, V., and B. Tate, "Connection Reuse in
the Session Initiation Protocol (SIP)",
draft-ietf-sip-connect-reuse-09 (work in progress),
February 2008.
[I-D.ietf-mmusic-sdp-dtls]
Fischl, J. and H. Tschofenig, "Session Description
Protocol (SDP) Indicators for Datagram Transport Layer
Security (DTLS)", draft-ietf-mmusic-sdp-dtls-00 (work in
progress), January 2008.
[I-D.ietf-sipping-consent-format]
Camarillo, G., "A Document Format for Requesting Consent",
draft-ietf-sipping-consent-format-05 (work in progress),
November 2007.
[RFC4579] Johnston, A. and O. Levin, "Session Initiation Protocol
(SIP) Call Control - Conferencing for User Agents",
BCP 119, RFC 4579, August 2006.
[I-D.ietf-sip-location-conveyance]
Polk, J. and B. Rosen, "Location Conveyance for the
Session Initiation Protocol",
draft-ietf-sip-location-conveyance-09 (work in progress),
November 2007.
Author's Address Author's Address
Jonathan Rosenberg Jonathan Rosenberg
Cisco Cisco
Edison, NJ Edison, 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 (2007). 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
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 58 change blocks. 
116 lines changed or deleted 338 lines changed or added

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