draft-ietf-sip-hitchhikers-guide-02.txt   draft-ietf-sip-hitchhikers-guide-03.txt 
SIP J. Rosenberg SIP J. Rosenberg
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Informational March 5, 2007 Intended status: Informational July 5, 2007
Expires: September 6, 2007 Expires: January 6, 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-02 draft-ietf-sip-hitchhikers-guide-03
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 September 6, 2007. This Internet-Draft will expire on January 6, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
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 11 skipping to change at page 2, line 11
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 . . . . . . . . . . . . . . . . . . . . 3 2. Scope of this Document . . . . . . . . . . . . . . . . . . . . 3
3. Core SIP Specifications . . . . . . . . . . . . . . . . . . . 4 3. Core SIP Specifications . . . . . . . . . . . . . . . . . . . 4
4. Public Switched Telephone Network (PSTN) Interworking . . . . 7 4. Public Switched Telephone Network (PSTN) Interworking . . . . 7
5. General Purpose Infrastructure Extensions . . . . . . . . . . 8 5. General Purpose Infrastructure Extensions . . . . . . . . . . 9
6. NAT Traversal . . . . . . . . . . . . . . . . . . . . . . . . 11 6. NAT Traversal . . . . . . . . . . . . . . . . . . . . . . . . 11
7. Minor Extensions . . . . . . . . . . . . . . . . . . . . . . . 12 7. Minor Extensions . . . . . . . . . . . . . . . . . . . . . . . 12
8. Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 13
9. Call Control Primitives . . . . . . . . . . . . . . . . . . . 14 9. Call Control Primitives . . . . . . . . . . . . . . . . . . . 14
10. Event Framework and Packages . . . . . . . . . . . . . . . . . 14 10. Event Framework and Packages . . . . . . . . . . . . . . . . . 15
11. Quality of Service . . . . . . . . . . . . . . . . . . . . . . 16 11. Quality of Service . . . . . . . . . . . . . . . . . . . . . . 16
12. Operations and Management . . . . . . . . . . . . . . . . . . 17 12. Operations and Management . . . . . . . . . . . . . . . . . . 17
13. SIP Compression . . . . . . . . . . . . . . . . . . . . . . . 17 13. SIP Compression . . . . . . . . . . . . . . . . . . . . . . . 17
14. SIP Service URIs . . . . . . . . . . . . . . . . . . . . . . . 17 14. SIP Service URIs . . . . . . . . . . . . . . . . . . . . . . . 18
15. Security Mechanisms . . . . . . . . . . . . . . . . . . . . . 18 15. Security Mechanisms . . . . . . . . . . . . . . . . . . . . . 19
16. Instant Messaging, Presence and Multimedia . . . . . . . . . . 20 16. Instant Messaging, Presence and Multimedia . . . . . . . . . . 20
17. Emergency Services . . . . . . . . . . . . . . . . . . . . . . 20 17. Emergency Services . . . . . . . . . . . . . . . . . . . . . . 21
18. Security Considerations . . . . . . . . . . . . . . . . . . . 21 18. Security Considerations . . . . . . . . . . . . . . . . . . . 21
19. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 19. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
20. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 20. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21
21. Informative References . . . . . . . . . . . . . . . . . . . . 21 21. Informative References . . . . . . . . . . . . . . . . . . . . 21
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 30 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 30
Intellectual Property and Copyright Statements . . . . . . . . . . 31 Intellectual Property and Copyright Statements . . . . . . . . . . 32
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 7, line 21 skipping to change at page 7, line 21
media feature tag RFC XXXX [108] have been defined for use with media feature tag RFC XXXX [108] have been defined for use with
ICE. ICE.
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 [80] 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 4916, Connected Identity in the Session Initiation Protocol (SIP)
(S): RFC XXXX [81] defines an extension to SIP that allows a UAC to (S): RFC 4916 [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, The use of the SIPS URI Scheme in the Session Initiation
Proxies (S): RFC XXXX [82] makes a small normative change to RFC Protocol (SIP) (S): RFC XXXX [112] revises the processing of the
3261, requiring loop detection in any proxy that forks a request. SIPS URI, originally defined in RFC 3261, to fix many errors and
It addresses a vulnerability uncovered in RFC 3261. problems that have been encountered with that mechanism.
Essential Corrections to SIP: A collection of fixes to SIP that
address important bugs and vulnerabilities. These include a fix
requiring loop detection in any proxy that forks [82] and a
clarification on how record-routing works [110].
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
skipping to change at page 15, line 20 skipping to change at page 15, line 27
RFC 4662, A Session Initiation Protocol (SIP) Event Notification RFC 4662, A Session Initiation Protocol (SIP) Event Notification
Extension for Resource Lists (S): RFC 4662 [67] 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 XXXX, An Extension to Session Initiation Protocol (SIP) Events
for Conditional Event Notification (S): RFC XXXX [111] defines an
extension to RFC 3265 to optimize the performance of
notifications. When a client subscribes, it can indicate what
version of a document it has, so that the server can skip sending
a notification if the client is up to date. It is applicable to
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 [65] 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.
skipping to change at page 21, line 47 skipping to change at page 22, line 14
BCP 9, RFC 2026, October 1996. BCP 9, RFC 2026, October 1996.
[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 Protocol for Network Address Translator (NAT) Traversal for
for Offer/Answer Protocols", draft-ietf-mmusic-ice-13 (work in Offer/Answer Protocols", draft-ietf-mmusic-ice-16 (work in
progress), January 2007. progress), June 2007.
[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 23, line 11 skipping to change at page 23, line 23
[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 (SIP)", Identity Management in the Session Initiation Protocol (SIP)",
RFC 4474, August 2006. RFC 4474, August 2006.
[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-11 (work in progress), (SIP)", draft-ietf-sip-gruu-14 (work in progress), June 2007.
October 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-07 (work in progress), January 2007. draft-ietf-sip-outbound-09 (work in progress), June 2007.
[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
skipping to change at page 24, line 45 skipping to change at page 25, line 7
[39] Rosenberg, J., "Request Authorization through Dialog [39] Rosenberg, J., "Request Authorization through Dialog
Identification in the Session Initiation Protocol (SIP)", Identification in the Session Initiation Protocol (SIP)",
RFC 4538, June 2006. RFC 4538, June 2006.
[40] Levin, O. and A. Johnston, "Conveying Feature Tags with the [40] Levin, O. and A. Johnston, "Conveying Feature Tags with the
Session Initiation Protocol (SIP) REFER Method", RFC 4508, Session Initiation Protocol (SIP) REFER Method", RFC 4508,
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-04 (work in progress), June 2007.
[42] Adams, D., "The Hitchhiker's Guide to the Galaxy", [42] Adams, D., "The Hitchhiker's 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-04 (work Initiation Protocol (SIP)", draft-ietf-sip-acr-code-04 (work
in progress), March 2007. in progress), March 2007.
[44] Camarillo, G., "Referring to Multiple Resources in the Session [44] Camarillo, G., "Referring to Multiple Resources in the Session
Initiation Protocol (SIP)", draft-ietf-sip-multiple-refer-01 Initiation Protocol (SIP)", draft-ietf-sip-multiple-refer-01
skipping to change at page 26, line 8 skipping to change at page 26, line 19
[56] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session [56] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
Initiation Protocol (SIP) Event Package for Conference State", Initiation Protocol (SIP) Event Package for Conference State",
RFC 4575, August 2006. RFC 4575, August 2006.
[57] Burger, E. and M. Dolly, "A Session Initiation Protocol (SIP) [57] Burger, E. and M. Dolly, "A Session Initiation Protocol (SIP)
Event Package for Key Press Stimulus (KPML)", RFC 4730, Event Package for Key Press Stimulus (KPML)", RFC 4730,
November 2006. November 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-02
(work in progress), February 2006. (work in progress), May 2007.
[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. and S. Channabasappa, "A Framework for Session [62] Petrie, D. and S. Channabasappa, "A Framework for Session
Initiation Protocol User Agent Profile Delivery", Initiation Protocol User Agent Profile Delivery",
draft-ietf-sipping-config-framework-10 (work in progress), draft-ietf-sipping-config-framework-12 (work in progress),
January 2007. June 2007.
[63] Petrie, D., "Extensions to the Session Initiation Protocol [63] Petrie, D., "Extensions to the Session Initiation Protocol
(SIP) User Agent Profile Delivery Change Notification Event (SIP) User Agent Profile Delivery Change Notification Event
Package for the Extensible Markup Language Language Package for the Extensible Markup Language Language
Configuration Access Protocol (XCAP)", Configuration Access Protocol (XCAP)",
draft-ietf-sip-xcap-config-00 (work in progress), draft-ietf-sip-xcap-config-00 (work in progress),
October 2006. October 2006.
[64] Camarillo, G., "Compressing the Session Initiation Protocol [64] Camarillo, G., "Compressing the Session Initiation Protocol
(SIP)", RFC 3486, February 2003. (SIP)", RFC 3486, February 2003.
skipping to change at page 27, line 24 skipping to change at page 27, line 36
[71] 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.
[72] 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.
[73] 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-04 Session Initiation Protocol (SIP)", draft-ietf-sip-e2m-sec-05
(work in progress), December 2006. (work in progress), March 2007.
[74] 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.
[75] 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.
[76] 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,
skipping to change at page 28, line 6 skipping to change at page 28, line 17
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[79] 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.
[80] 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.
[81] Elwell, J., "Connected Identity in the Session Initiation [81] Elwell, J., "Connected Identity in the Session Initiation
Protocol (SIP)", draft-ietf-sip-connected-identity-05 (work in Protocol (SIP)", RFC 4916, June 2007.
progress), February 2007.
[82] Sparks, R., "Addressing an Amplification Vulnerability in [82] Sparks, R., "Addressing an Amplification Vulnerability in
Session Initiation Protocol (SIP) Forking Proxies", Session Initiation Protocol (SIP) Forking Proxies",
draft-ietf-sip-fork-loop-fix-04 (work in progress), draft-ietf-sip-fork-loop-fix-05 (work in progress),
October 2006. March 2007.
[83] 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.
[84] 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.
[85] Sparks, R., "Internet Media Type message/sipfrag", RFC 3420, [85] Sparks, R., "Internet Media Type message/sipfrag", RFC 3420,
November 2002. November 2002.
[86] 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.
[87] 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.
[88] Rosenberg, J., "TCP Candidates with Interactive Connectivity [88] Rosenberg, J., "TCP Candidates with Interactive Connectivity
Establishment (ICE)", draft-ietf-mmusic-ice-tcp-02 (work in Establishment (ICE", draft-ietf-mmusic-ice-tcp-03 (work in
progress), October 2006. progress), March 2007.
[89] 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.
[90] 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.
[91] Camarillo, G., "Session Description Protocol (SDP) Format for [91] Camarillo, G., "Session Description Protocol (SDP) Format for
Binary Floor Control Protocol (BFCP) Streams", RFC 4583, Binary Floor Control Protocol (BFCP) Streams", RFC 4583,
skipping to change at page 29, line 30 skipping to change at page 29, line 42
[98] Lawrence, S., "Diagnostic Responses for Session Initiation [98] Lawrence, S., "Diagnostic Responses for Session Initiation
Protocol Hop Limit Errors", Protocol Hop Limit Errors",
draft-ietf-sip-hop-limit-diagnostics-03 (work in progress), draft-ietf-sip-hop-limit-diagnostics-03 (work in progress),
June 2006. June 2006.
[99] 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.
[100] Jennings, C., "Certificate Management Service for The Session [100] Jennings, C., "Certificate Management Service for The Session
Initiation Protocol (SIP)", draft-ietf-sip-certs-02 (work in Initiation Protocol (SIP)", draft-ietf-sip-certs-03 (work in
progress), October 2006. progress), March 2007.
[101] Rosenberg, J., "A Framework for Consent-Based Communications [101] Rosenberg, J., "A Framework for Consent-Based Communications
in the Session Initiation Protocol (SIP)", in the Session Initiation Protocol (SIP)",
draft-ietf-sip-consent-framework-01 (work in progress), draft-ietf-sip-consent-framework-01 (work in progress),
November 2006. November 2006.
[102] Tschofenig, H., "SIP SAML Profile and Binding", [102] Tschofenig, H., "SIP SAML Profile and Binding",
draft-ietf-sip-saml-01 (work in progress), October 2006. draft-ietf-sip-saml-02 (work in progress), May 2007.
[103] Camarillo, G., "The Session Initiation Protocol (SIP) Pending [103] Camarillo, G., "The Session Initiation Protocol (SIP) Pending
Additions Event Package", Additions Event Package",
draft-ietf-sipping-pending-additions-01 (work in progress), draft-ietf-sipping-pending-additions-02 (work in progress),
November 2006. April 2007.
[104] Lennox, J., "Connection-Oriented Media Transport over the [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)", RFC 4572, July 2006. Description Protocol (SDP)", RFC 4572, July 2006.
[105] Andreasen, F., "SDP Capability Negotiation", [105] Andreasen, F., "SDP Capability Negotiation",
draft-ietf-mmusic-sdp-capability-negotiation-04 (work in draft-ietf-mmusic-sdp-capability-negotiation-05 (work in
progress), February 2007. progress), March 2007.
[106] Andreasen, F., "SDP media capabilities Negotiation", [106] Andreasen, F., "SDP media capabilities Negotiation",
draft-ietf-mmusic-sdp-media-capabilities-01 (work in draft-ietf-mmusic-sdp-media-capabilities-01 (work in
progress), February 2007. progress), February 2007.
[107] Garcia-Martin, M., "A Session Description Protocol (SDP) [107] Garcia-Martin, M., "A Session Description Protocol (SDP)
Offer/Answer Mechanism to Enable File Transfer", Offer/Answer Mechanism to Enable File Transfer",
draft-ietf-mmusic-file-transfer-mech-00 (work in progress), draft-ietf-mmusic-file-transfer-mech-03 (work in progress),
December 2006. June 2007.
[108] Rosenberg, J., "Indicating Support for Interactive [108] Rosenberg, J., "Indicating Support for Interactive
Connectivity Establishment (ICE) in the Session Initiation Connectivity Establishment (ICE) in the Session Initiation
Protocol (SIP)", draft-ietf-sip-ice-option-tag-00 (work in Protocol (SIP)", draft-ietf-sip-ice-option-tag-02 (work in
progress), January 2007. progress), June 2007.
[109] 3GPP, "Internet Protocol (IP) multimedia call control protocol [109] 3GPP, "Internet Protocol (IP) multimedia call control protocol
based on Session Initiation Protocol (SIP) and Session based on Session Initiation Protocol (SIP) and Session
Description Protocol (SDP); Stage 3", 3GPP TS 24.229 5.18.0, Description Protocol (SDP); Stage 3", 3GPP TS 24.229 5.19.0,
October 2006. June 2007.
[110] Froment, T. and C. Lebel, "Addressing Record-Route issues in
the Session Initiation Protocol (SIP)",
draft-ietf-sip-record-route-fix-00 (work in progress),
July 2007.
[111] Niemi, A., "An Extension to Session Initiation Protocol (SIP)
Events for Conditional Event Notification",
draft-ietf-sip-subnot-etags-00 (work in progress), May 2007.
[112] Audet, F., "The use of the SIPS URI Scheme in the Session
Initiation Protocol (SIP)", draft-ietf-sip-sips-05 (work in
progress), June 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
 End of changes. 28 change blocks. 
48 lines changed or deleted 72 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/